How to connect Intercom MCP to OpenClaw
Connect Intercom MCP to OpenClaw with ClawLink: paste your Intercom MCP key once and 14 tools work from chat. No MCP server to run, nothing stored on your machine.
Intercom MCPAPI KEYMCPAccess Intercom conversations, contacts, companies, Help Center articles, tickets, and workspace data through Intercom's hosted MCP server.. Once connected, OpenClaw can read and act on Intercom MCP from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Intercom MCP access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Intercom MCP setup: install one ClawHub skill, connect Intercom MCP in the browser, and OpenClaw can call real Intercom MCP actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to Intercom MCP.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Intercom MCP
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Intercom MCP?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Intercom MCP in the ClawLink dashboard — paste your Intercom MCP API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Intercom MCP, summarize it in plain English, and point out anything that needs attention.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Intercom MCP is connected in the dashboard, that agent calls the same 14 Intercom MCP tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Intercom MCP MCP for OpenClaw
Looking for a Intercom MCP MCP server for OpenClaw? ClawLink connects Intercom MCP to OpenClaw and exposes 14 Intercom MCP tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Intercom MCP integration works the same way.
What the OpenClaw Intercom MCP integration can do
14 Intercom MCP tools are ready for OpenClaw once the account is connected.
All 14 Intercom MCP tools for OpenClaw
| Tool | What it does |
|---|---|
Get article intercom_mcp_get_article | Retrieve complete details for a specific Intercom Help Center article |
Get company intercom_mcp_get_company | Retrieve complete details for a specific Intercom company |
Get contact intercom_mcp_get_contact | Retrieve complete details for a specific Intercom contact |
Get conversation intercom_mcp_get_conversation | Retrieve complete details for a specific Intercom conversation |
List articles intercom_mcp_list_articles | List all articles in the Intercom Help Center |
List companies intercom_mcp_list_companies | List Intercom companies with optional filters |
Search intercom_mcp_search | Purpose: 1 |
Search articles intercom_mcp_search_articles | Search for articles in the Intercom Help Center |
Search contacts intercom_mcp_search_contacts | Search for Intercom contacts using multiple filter criteria |
Search conversations intercom_mcp_search_conversations | Search for Intercom conversations using multiple filter criteria |
Create article intercom_mcp_create_article | Create a new article in the Intercom Help Center |
Fetch intercom_mcp_fetch | Retrieve detailed content for a specific Intercom resource by ID or URL |
Submit mcp feedback intercom_mcp_submit_mcp_feedback | Submit feedback about this Intercom MCP server to the Intercom team that builds it |
Update article intercom_mcp_update_article | Update an existing article in the Intercom Help Center |
Try it: find the Intercom MCP tool you need
Browse the 14 Intercom MCP tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Intercom MCP, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Intercom MCP, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Intercom MCP, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Intercom MCP, summarize it in plain English, and point out anything that needs attention.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Intercom MCP working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Intercom MCP API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Intercom MCP account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Intercom MCP. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Intercom MCP actions to the runtime in a format your agent can reliably use. | 14 tools for Intercom MCP are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Intercom MCP to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Intercom MCP in the browser, and the 14 tools above work from chat. There is no SDK and no config file, and the Intercom MCP key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Intercom MCP skill but can't call the tools
The ClawHub skill teaches OpenClaw about Intercom MCP, but the calls run through the ClawLink plugin and your connected account. Make sure Intercom MCP is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Intercom MCP from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Intercom MCP tools
Intercom MCP tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Intercom MCP call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Intercom MCP returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for Intercom MCP has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Intercom MCP integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Intercom MCP: link your Intercom MCP account once in the browser and OpenClaw can call the Intercom MCP API through 14 ready-made tools — no custom code or token handling.
How do I add Intercom MCP to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Intercom MCP skill from ClawHub, then you click Connect in the dashboard to authorize Intercom MCP. OpenClaw calls the tools from the next message — no config files, and the Intercom MCP key you paste is stored server-side instead of in your environment.
How long does it take to connect Intercom MCP to OpenClaw?
About two minutes. Sign in, click Connect next to Intercom MCP in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Intercom MCP up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Intercom MCP working from chat.
OpenClaw installed the Intercom MCP skill but can't call the tools
The ClawHub skill teaches OpenClaw about Intercom MCP, but the calls run through the ClawLink plugin and your connected account. Make sure Intercom MCP is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
