Supportchat

io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026

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

VerifiedSTDIODesktop only

Overview

Supportchat's local MCP server; no sign-in required; STDIO.

No AI overview yet: these facts come from the registry entry and the server itself.

Installation

In SourceWeft

  1. Open Supportchat in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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:

bash
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

bash
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

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

Docker

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

Development

bash
npm installnpm run buildnpm test

License

MIT

Source: README.md at commit 3de4e3b

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestNov 3, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts