Intercom MCP: workspace data and connection checks
Connect an approved AI client to Intercom MCP for the actual hosted region and permissions, then verify retrieved records and the boundary for changes.
- Published
- Last updated
Intercom MCP connects an approved AI client to your Intercom workspace through Model Context Protocol (MCP). Use the hosted server for US or EU workspaces, with the matching regional endpoint and reviewed permissions. Australian-hosted workspaces aren’t supported by that server. Test a permitted read and a denied action before giving the client routine support work.
Identify the server and workspace
Intercom’s hosted server lets an external AI client retrieve workspace records. Fin’s MCP connectors run in the opposite direction: Fin connects to another system. A connector template doesn’t establish that an external client can read your Intercom workspace.
Intercom’s connection instructions identify the hosted region from the workspace address. Use Streamable HTTP for a new connection. The older SSE transport is deprecated.
Regional connection choices
| Workspace hosting | Hosted MCP address | Decision |
|---|---|---|
| US, with app.intercom.com | https://mcp.intercom.com/mcp | Connect with the US endpoint |
| EU, with app.eu.intercom.com | https://mcp.eu.intercom.com/mcp | Connect with the EU endpoint |
| Australia | No supported hosted MCP endpoint | Use an approved regional API integration or the Intercom interface |
The hosted MCP guide documents the server. Intercom’s separate help guide confirms that AU hosting remains unsupported for MCP. Don’t substitute the US endpoint for an Australian workspace.
For an AU-hosted workspace, the Intercom REST API has the regional base https://api.au.intercom.io. An authorised developer can build a scoped integration against that API. That is a custom API path, not a successful connection to the hosted MCP server.
Changing hosting is a separate workspace decision. Intercom’s regional hosting guide says existing workspace data cannot migrate directly between regions. Don’t create another region’s workspace simply to make a connection test pass.
Connect with the intended permissions
Use OAuth for a browser-based authorisation flow unless your approved integration requires a Bearer token. Identify the teammate authorising access and the workspace before approving either method. Treat the client’s access as a separate decision from allowing staff to use Intercom in their browser.
- In your approved client, add a remote MCP connection with the regional address from the table and Streamable HTTP transport.
- Start OAuth from that client. Review the application name and Redirects to address on the Intercom MCP consent page. Cancel if the destination is unexpected.
- Review the requested access, then complete Intercom’s authorisation screen for the intended workspace. Return to the client and inspect the tools it exposes.
- Run a permitted read against an approved test conversation. Open the same conversation in Intercom and confirm the record identity.
- Attempt a request outside the approved permissions in a disposable test setup. Confirm that the server denies it and that the client doesn’t invent a result.
Intercom’s consent screen identifies the requesting application, while its following authorisation screen names the MCP server. The application supplies its own name. A familiar name alone doesn’t establish that the redirect address is correct.
Intercom’s OAuth permissions reference distinguishes conversation access from contact and company access. Record the granted scopes and signed-in teammate. Don’t assume that a limited-looking client screen narrows a broadly authorised connection.
For a Bearer-token integration, keep the token in the client’s secret storage. Avoid examples containing real credentials or customer messages. Use a dedicated, minimally scoped app so revoking it doesn’t unexpectedly disable another workflow.
Verify the retrieved support record
Verify an answer against its conversation and contact records before using it for a support decision. A search hit is a candidate record. The assistant’s summary is a further interpretation of that record.
Consider a fictional test workspace with contact contact_test_42 and two support conversations. One asks about a delayed parcel. The other asks about sizing. These are test labels, not IDs to send to a live workspace.
Use this acceptance sequence with your own approved test records:
- Search for the known test contact. Confirm its identifier against the fixture, then retrieve its full record.
- Search conversations for that contact’s expected delivery discussion. Fetch the returned conversation ID rather than choosing a similar-looking thread by its first sentence.
- Compare the source message and subsequent replies with the record in Intercom. Confirm the contact association and whether internal notes influenced the answer.
- If the response has a next-page cursor, repeat the same search with that cursor. Continue until the result set is complete for the question being answered.
- Ask the client to name the source conversation and separate recorded facts from its interpretation. Compare that answer with the known fixture.
The server’s universal search requires an object type, such as object_type:conversations. It supports starting_after for pagination. Pass returned IDs to fetch for detailed records. Keep the original filters when requesting subsequent pages.
In the fictional delivery conversation, the customer says their parcel hasn’t arrived. A teammate says they’ll investigate. Correct: the support record shows an unresolved delivery enquiry. Incorrect: the assistant reports that the order has shipped solely because the customer mentioned a tracking number.
Check fulfilment or payment claims against the authorised order system. A conversation can quote an old order state or contain a customer’s mistaken account. Keep the order identifier and the support conversation identifier separate.
Conversation detail can also have its own completeness limit. Intercom’s conversation retrieval reference describes pagination for long conversation histories. If the necessary earlier messages are absent, retrieve the required history through a supported path before answering from a partial thread.
Review changes and revoke access
Intercom MCP includes write operations, so discovery of a tool is not permission to run it. Its documented tools include create_article, update_article and add_internal_note. The note tool requires Write conversations permission. It can reopen a snoozed conversation assigned to another teammate, so an internal note can affect workflow state.
OAuth connections with the required workspace entitlement and teammate permission can also expose Fin Operator tools. Intercom’s Operator guide separates proposed changes from their application. Read each proposal with get_proposal_details and obtain approval for its exact effects before calling apply_proposals. Some changes cannot be undone.
An Operator response requiring human approval must stay pending until a person approves the named action. The client must not interpret a request to inspect a proposal as permission to apply it. Bearer-token connections don’t receive Operator tools.
Use a disposable setup to check these failure paths:
- For a refused write, use a token without the required write scope. Expect a permission error and confirm the target record remains unchanged.
- For an expired OAuth consent page, restart the connection from the client. Intercom documents a 15-minute consent window. An expired consent page doesn’t prove that an existing access token has expired.
- For the wrong region, remove the mistaken connection and reconnect with the workspace’s endpoint. Intercom documents a technical-difficulties message after Allow as a possible wrong-region symptom.
- For revocation, disable the intended grant, then attempt a fresh read through that connection. Expect authentication failure, with no newly retrieved workspace data.
For a dedicated private app, Intercom’s installation and revocation guide places token controls under Developer Hub, Test and Publish and the selected workspace. Regenerate token rotates it. Uninstall app revokes its access entirely. Review dependent workflows before uninstalling.
Remove the client’s saved connection as well. Revocation stops future access but doesn’t erase records the client already retained. Apply your retention rules to those copies. Restore access only after the correct workspace, permitted read and denied request all behave as intended.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.