Back to Browse

Supportchat MCP Server

Developer ToolsModerate5.4MCP RegistryLocal
Free

Server data from the Official MCP Registry

Intercom conversations, contacts, tags and articles as MCP tools.

About

Intercom conversations, contacts, tags and articles as MCP tools.

Security Report

5.4
Moderate5.4Moderate Risk

supportchat is a straightforward Intercom REST client: the access token is read from INTERCOM_ACCESS_TOKEN, sent only as a Bearer header to the Intercom API, and no data is sent to third-party hosts. The main concerns are write actions (reply, close, tag, create/update contact) that the model can trigger with a caller-supplied admin_id, and the overridable API base URL, which could redirect the token if the environment is tampered with. Both are reasonable for this category and should be documented for users. Supply chain analysis found 4 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.

8 files analyzed · 11 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

INTERCOM_ACCESS_TOKENRequired

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-cloudcorprecords-supportchat": {
      "env": {
        "INTERCOM_ACCESS_TOKEN": "your-intercom-access-token-here"
      },
      "args": [
        "-y",
        "@reneturcios/supportchat"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub 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

Reviews

No reviews yet

Be the first to review this server!