Claude reads last week's Intercom conversations through Intercom's MCP server, groups repeated product problems and drafts Linear issues. A person reviews them before anything is filed.
Independent review. Unpaid; no partnership with the tools on this page. Based on public documentation and research. Trademarks identify their owners’ products. Disclosure.
Editorial shortlist
Compare your options.
For turning repeated problems into proposed issues.
Keep supporting cases and severity uncertainty; approve Linear writes separately. Choose one for drafting from approved material; switching may need setup changes.
Editorial judgment, not a personal-use endorsement or performance score. These are alternatives for the named role, not three required stack components. Vendors did not pay for, request or approve these positions.
Source reconciliation comes before extra automation. A lower-ranked option may fit your constraints better; compare the conditions stated on each card before choosing.
Setup and portability: Keep the approved source pack and accepted output outside chat. Upload access is not publication permission.
Reviewed 2026-10-21. This page applies a shared comparison for “drafting from approved material” to the stated task and constraints. It is documentation-based editorial guidance, not three new hands-on tests. We weigh value for the job, distinct capabilities, replacement limits, technical effort and interoperability. Check current plan terms before adopting or switching.
Confirmed = vendor-documented, not Ion-tested. Human and AI-platform steps are proposed roles.
Human approval
Nothing is filed in Linear until you approve each draft.
Watch out for
Conversation text can include personal data, so keep it out of issue descriptions and link to the conversation instead. Grouping by theme is a judgment call, so check that each draft really matches its conversations. To browse before you approve, connect Linear's read-only endpoint, and switch to the full endpoint only when you file.
Starter prompt
Using the Intercom MCP server, find conversations closed in the last 7 days. Group them by product problem and only keep themes that show up in at least 3 conversations. For each theme, draft a Linear issue with a one-line title, a short description in plain words, the conversation count and links to the conversations. Leave out customer names, email addresses and any other personal details. Show me the drafts and wait for my approval before creating anything in Linear.
Written for this workflow. Paste it into your AI platform and adjust it to your situation.
Intercom: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; Linear: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it
Intercom: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; Linear: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it
Intercom: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; Linear: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it
Intercom: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; Linear: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it
Gemini
To verify
Intercom: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; Linear: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it
Intercom: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; Linear: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it
What the platform statuses mean
Confirmed: documented access meets the recorded requirements. Inferred: a reviewed note describes a plausible, untested pairing. To verify: a connection or step is unresolved. MCP and API pairings need route-specific evidence; a plugin, CLI or API alone does not prove compatible access, credentials or permissions. These are documentation assessments, not IonBin runtime tests.
What we checked (2026-10-18)
Intercom MCP server.Intercom documents a remote server for US-hosted workspaces at https://mcp.intercom.com/mcp and for EU-hosted ones at https://mcp.eu.intercom.com/mcp. It offers 14 tools, including a universal search for conversations and contacts and a search_conversations tool with filters for state, assignee and timing. Requests to the EU endpoint are processed in the EU.
Linear MCP server. Linear hosts its server at https://mcp.linear.app/mcp, with OAuth 2.1 or an API key. A read-only endpoint at /mcp/readonly is available for lookups.
Set it up
Use the Intercom endpoint for your region. The workspace URL tells you which one: app.intercom.com is US and app.eu.intercom.com is EU.
Connect Linear. Use the read-only endpoint while you review, and the full endpoint only to file approved issues.
Once a week, run the prompt above and read every draft against its linked conversations.
Strip personal details, merge duplicates of existing Linear issues, then approve the drafts you want filed.
This is a proposed sequence based on documented tools, not a tested account integration.
Related agent skill
OpenAI’s Linear skill has the same read-first habit: it reads issues before changing them and explains bulk changes before applying them. IonBin reviewed it from source only.