Read and send Slack messages, manage channels and threads.
slack, messaging, communication, automation
Intercom
Search conversations, contacts, companies, and help articles in Intercom from an AI agent — official MCP.
Quick answer
What it does
Exposes Intercom data as MCP tools: search + fetch, conversations, contacts, companies, and Help Center articles (list, search, get, create, update), served from Intercom's hosted remote MCP.
Best for
- Searching conversations and contacts
- Reading customer + company records
- Managing Help Center articles
- Grounded support automation
Not for
- Non-US-hosted Intercom workspaces
- Bulk write operations beyond articles
Setup recipe
- 1
Install
No install snippet available yet — see the project’s README for setup instructions.
- 2
Set required secrets
No credentials required — this MCP runs over stdio without authentication.
- 3
Try a minimum working prompt
Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.
Tools & permissions
Tools list pending verification. The server exposes tools over MCP; we haven’t yet parsed its capability manifest into this page. Check the GitHub repo for the authoritative list.
Agent prompt pack
— copy into Claude, Cursor, or ChatGPT.Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.
Recommend the best MCP servers for [task: e.g. communication work] in [client: Claude]. Constraints: - Prefer tools that are [official | open-source | read-only] — pick what matters for my use case. - Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport]. - Return at most 3 picks, ranked. For each pick include: 1. One-sentence rationale. 2. The ready-to-paste install snippet for my client. 3. Any required secrets I need to create before installing. Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-communication
Compare Intercom against a real alternative. Swap the second MCP in [brackets] if you want a different match.
Compare Intercom MCP vs [Slack MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"]. Judge them on: - Setup time and complexity (what a new user hits first). - Auth model (none / API key / OAuth 2.1) and credential risk. - Transport (stdio / Streamable HTTP / SSE) and where the server runs. - Required secrets and the blast radius if they leak. - Operational risk in an unattended agent loop. - Which one is "good enough" for a weekend prototype vs. production. End with one sentence: which should I pick for my scenario, which is: [my scenario]. References: - https://top-mcps.com/mcp/intercom - top-mcps.com listing for Slack
Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.
Install the Intercom MCP server for my [client: Claude] at the default config path for that client. Use the exact install snippet published at https://top-mcps.com/mcp/intercom (fetch https://top-mcps.com/mcp/intercom.json for the canonical server.json if you can read URLs). Before finishing: 1. Create the required secrets (no secrets) and put them in the appropriate env block — do not hard-code them. 2. Restart or reload the client so it picks up the new server. 3. Verify the server is connected (green / running state) and at least one tool is listed. 4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry. Confirm when done and list the tools the server now exposes.
Frequently asked questions
What changed
— 2 updates tracked.Refreshed install snippets and fact sheet; verified for 2026.
Initial directory listing.
More Communication MCPs
Other tools in the same category worth evaluating.
Compared with Intercom
Side-by-side breakdowns for the choices people most often weigh against this MCP.
Exploring Top MCPs for Communication? See all Communication MCPs →