mcpField
S
supportchat

supportchat

Local
github.com/CloudCorpRecordsCommunication0Updated 2w ago
Repository

About supportchat

supportchat wraps a core set of Intercom REST API operations for conversations, contacts, tags, and articles, for developers and agents working with Intercom support. It uses an access token for API requests and does not reproduce hosted OAuth.

Key features

  1. 01List, search, and retrieve conversations
  2. 02Reply to or close conversations
  3. 03List, create, and update contacts
  4. 04List tags and tag contacts
  5. 05List articles

Use cases

  1. 01Find open support conversations
  2. 02Reply to or close a customer conversation
  3. 03Maintain contact details and tags
  4. 04Browse Intercom articles

MCP support

It runs as a stdio MCP server and exposes 12 Intercom REST API tools to MCP clients. Calls require INTERCOM_ACCESS_TOKEN.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "cloudcorprecords-supportchat": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/supportchat"
      ]
    }
  }
}
Run commandnpx -y @reneturcios/supportchat

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@reneturcios/supportchat0.1.0
ocighcr.io/cloudcorprecords/supportchat:0.1.0

Tools

12

Saved tool list · updated 1w ago

ParameterTypeRequiredDescription
statestringNoOptional conversation state to filter by, passed as the state query parameter.
per_pagenumberNoOptional maximum number of conversations to return per page.

Details

From the project README

supportchat

Intercom support conversations as MCP tools, talking to the Intercom REST API. supportchat is a clean-room rebuild of the core surface of the Intercom MCP server, under a new name: fresh code, no copied branding. The original is Intercom's hosted remote MCP (OAuth); hosted OAuth is NOT reproduced — this rebuild is a token REST client for the same API.

Tools (core subset, 12)

list_conversations, get_conversation, reply_to_conversation, close_conversation, search_conversations, list_contacts, get_contact, create_contact, update_contact, list_tags, tag_contact, list_articles.

Not in this subset: article detail (get_article, dropped to keep exactly 12), companies, teams and teammates admin, events and data attributes, notes, tickets, workflows, visitor conversion tools, and counts and reporting exports.

Setup

Create an access token for your Intercom workspace and set it:

export INTERCOM_ACCESS_TOKEN=dG9r...

Optionally override the API base with INTERCOM_API_BASE_URL (default https://api.intercom.io). Every request carries the Intercom-Version: 2.11 header. Without the token, every tool call fails with an error naming the missing variable. Replying and closing conversations require the acting admin's admin_id.

CLI

npx @reneturcios/supportchat list_conversations '{"state":"open"}'
npx @reneturcios/supportchat mcp        # stdio MCP server

Each tool name is a subcommand taking one JSON object argument.

MCP client config

{
  "mcpServers": {
    "supportchat": {
      "command": "npx",
      "args": ["-y", "@reneturcios/supportchat", "mcp"],
      "env": { "INTERCOM_ACCESS_TOKEN": "dG9r..." }
    }
  }
}

Docker

docker run -i -e INTERCOM_ACCESS_TOKEN ghcr.io/cloudcorprecords/supportchat

Development

npm install
npm run build
npm test

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.