Intercom MCP: support context without a customer-data dump

Intercom’s official MCP server lets compatible AI clients retrieve support context for summaries and draft answers. Fin’s MCP connectors let Intercom’s AI agent use external tools instead. Start with a selected, minimised case brief and require a human to review the reply.

What it can do

As of 30 Oct 2026, the official server guide documents conversation and contact retrieval, company information, and Help Center article tools. Treat those as building blocks for a specific support job, not a reason to load your whole customer history. Check the current documentation for the tool list and permissions before enabling writes.

A useful pilot is a handoff summary. Select a case about an account invitation, identify what the customer tried, and ask for the unresolved question and the next diagnostic action. Require the draft to distinguish customer statements from verified facts. An invitation that the customer says expired is different from an expiry confirmed in a system record.

Another practical task is preparing an answer from an approved help article and a redacted case brief. Keep the output in a review queue. The reviewer checks the policy, account details and proposed next step before sending anything. Drafting text does not itself authorise a customer message or a change to the workspace.

For other support systems, compare the Zendesk MCP guide. Browse the MCP servers for apps category for related connection patterns.

Minimise customer data before the task

Use this as a proposed workflow: an authorised operator or a separately reviewed retrieval service selects the relevant material, removes unnecessary fields, and passes the reduced brief to the drafting task. Merely asking an already connected assistant to redact its final answer is too late to keep raw tool responses out of that assistant’s context.

For example, a brief can say that the customer cannot accept an invitation after changing their login email, that resending did not help, and that account ownership still needs verification. The task can draft an explanation and a request for the approved verification step without receiving an email address or the rest of the customer’s history.

Keep the lookup between the local reference and the real case in the authorised support system. Redaction reduces exposure; it does not automatically make the remaining text anonymous. A distinctive incident can still identify someone. Use the MCP security checklist when designing the retrieval boundary.

How to connect it safely

1. Define the job and its owner. Start with a draft or summary of a selected case. Decide who may retrieve the source, who reviews the output, and where it may be stored. Use test material until these decisions are clear.

2. Review workspace permissions. Administrators can inspect teammate access under Settings → Workspace → Teammates in Intercom’s permissions guidance. As of 30 Oct 2026, MCP requests made on behalf of a teammate follow that teammate’s permissions and seat rules; conversation search requires full Inbox access. See the October permissions update. Review the requested integration access too. A narrow prompt is not a customer boundary: test access outside the intended case before using real data.

3. Check regional eligibility and routing. As of 30 Oct 2026, the Intercom MCP guide lists support only for US-hosted workspaces. The workspace addresses are app.intercom.com for US, app.eu.intercom.com for EU and app.au.intercom.com for Australia. Do not assume an EU or Australian workspace can use the hosted server. Intercom warns that information sent to external systems may leave its region. Review the client’s processing and retention separately. Regional Data Hosting, as of 30 Oct 2026.

4. Add the remote server in a compatible editor client. In VS Code, run MCP: Add Server from the Command Palette and choose HTTP. The official Intercom guide lists https://mcp.intercom.com/mcp; confirm that the current regional instructions apply to your workspace before entering an endpoint. Complete the browser authentication flow and inspect the requested access. Keep credentials out of chat and committed configuration. Follow the VS Code connection instructions, as of 30 Oct 2026, for the configuration destination appropriate to your client.

5. Inspect the tools and test the boundary. Enable only the tools needed for the pilot where the client supports selection. Keep mutations behind explicit review. With test records, try the intended case and a case outside the allowed scope. A tool selector limits actions; your retrieval service must still enforce which customers those actions can reach. If that restriction cannot be demonstrated, use an operator-prepared brief instead of direct task access.

6. Verify the result and close access deliberately. Inspect the actual tool response, compare the summary with the source, and check for leaked identifiers. Record the case reference, source time, reviewer and decision without duplicating raw conversations in logs. Remove the connection when the pilot ends and review the client’s retained transcripts.

When this does not work

Direct access conflicts with pre-task redaction. If the drafting assistant receives the full conversation first, redaction in its answer cannot undo that disclosure. Put selection and filtering upstream, or prepare the brief manually.

Authentication succeeds but the job fails. Missing permissions, invalid search parameters and API throttling are documented failure modes. Check the current documentation and the returned error before changing access or retrying. An empty result should not become a claim that no relevant case exists. Intercom MCP guide.

The request crosses an authority boundary. Customer text is evidence to analyse, not permission to export records or call another tool. A message asking the assistant to inspect another customer’s account must not expand the authorised task.

You enable more than retrieval. Fin Operator MCP tools can propose and apply workspace changes. Their availability depends on workspace, teammate and OAuth permissions; some applied changes cannot be undone. Keep this outside a draft-only pilot. Fin Operator documentation, as of 30 Oct 2026.

For Fin calling an external server, Intercom explicitly cautions that returned tool data may be shared with the customer. Filter the response at the source before enabling that path. Fin connector configuration.

Where Tvijo fits

As of 30 Oct 2026, the DSHREM VS Code extension provides an editor entry point for a question and selected context. A suitable support workflow is to attach the approved, minimised brief and request a draft answer. The operator or an explicitly scoped connector must perform customer-data selection and redaction before that submission; do not assume an automatic Intercom redaction feature.

TvijoCode is a test build with the Tvijo extension embedded. Tvijo MCP makes Tvijo callable from a compatible MCP client for consultation; its prepared diff-review functionality awaits publication in the dated release record, and editor delegation remains planned. None of these descriptions establishes a ready Intercom integration. A direct connection needs separate implementation and acceptance checks.

The Tvijo workspace, as of 30 Oct 2026, shows Try at $0: up to 5 tasks, 50,000 tokens or $0.05 of sponsored usage, whichever is reached first, from a shared $1 daily pool funded by TVIJO. Service credit is shown at $10 for requested prepaid credit, with metered provider usage plus an 8% service markup. Payment collection is not activated; an order is not a charge.

Review permissions and data flow before submitting a customer brief. A task limit controls usage, while the data decision determines what the task receives.

FAQ

Is Intercom MCP the same as Fin’s MCP connectors?

They serve different directions: the hosted server exposes Intercom capabilities to an external client; Fin’s connectors let Fin use external tools. Choose the direction before configuring access.

Does MCP automatically hide unrelated customers?

Do not assume it does. Verify the effective authorisation boundary with test records. Use a filtered retrieval service or an operator-prepared brief when a task must see only selected customer data.

Can I use it only to draft answers?

Design the pilot that way: minimise the input, restrict available actions, and have a support reviewer approve the text. Check the current documentation for tool availability; do not treat a draft request as permission to send or publish.

Intercom is a trademark of its owner. Tvijo is not affiliated with or endorsed by it.