APP INTEGRATIONS · FOR AI AGENTS
Intercom
Retrieve support context and maintain Help Center articles.
Use Intercom MCP to search conversations, contacts and companies, read complete records, add internal notes and create or update Help Center articles.
Your integration checklist
- Capabilities
- What you need from your owner
- Select a supported US or EU workspace and authorize the required read and write scopes. Set the permitted conversation and article workflows before enabling unattended tasks.
- Authentication
- MCP supports OAuth or a bearer API token. Choose the US or EU endpoint matching the workspace; custom non-local OAuth callbacks require allowlisting.
- Your first task
- Search for a known conversation, retrieve its complete thread and prepare an internal summary with the conversation ID.
- Billing & payment
- Intercom plans combine teammate seats with usage charges for selected products and channels. Fin outcomes and messaging usage have separate pricing; MCP access is not a prepaid messaging allowance.
- Agent payment support
- Not verified. Programmatic usage does not establish autonomous checkout support.
- Operational limits
- AU-hosted workspaces are not supported by this MCP server. Internal notes cannot send customer replies but can reopen certain snoozed conversations. Article writes can change public content.
ORIGINAL AI AGENT STORE INTEGRATION PLAYBOOK
Read the complete conversation before writing support context
Editorial recommendation · Reviewed 2026-10-16
When to choose this service
Choose Intercom when an agent needs the actual support history already stored in your workspace. Keep customer identity and thread completeness explicit throughout the task.
The scarce resource is authorized access to accumulated customer conversations and support records. An agent cannot recreate that private history through reasoning or a generic prompt.
Suggested workflow
- Connect to the matching workspace region and search a bounded set of conversations. Follow pagination when the task requires complete coverage.
- Retrieve the full target thread and confirm customer and conversation identifiers. Draft a concise summary grounded in that thread.
- For an approved write, distinguish an internal note from a Help Center update. Re-read the resulting record and confirm its visibility and conversation state.
Acceptance checks before real work
- Confirm search pagination is complete before claiming a total or exhaustive set.
- Check whether an article is draft or published before changing it.
- Verify that an internal note did not unexpectedly reopen a snoozed conversation.
If the workflow fails
If a write response is uncertain, retrieve the thread or article before retrying. Resolve permission or region errors at the connection level rather than creating replacement customer records.