Intercom MCP honesty matrix — conversations/contacts/companies read + articles R/W vs FDT create_* (no create_pr / reply-as-agent)
Intercom MCP lets AI tools (Claude Code, Claude Desktop, ChatGPT, Cursor, VS Code) securely access Intercom data via Streamable HTTP at mcp.intercom.com/mcp. The published configure copy: read access to conversations, contacts, and companies, plus read and write access to Help Center articles. Available for US-hosted Intercom workspaces.
That surface is CRM/Help-Center data for agents — not ship-to-code and not reply-as-agent. There is no create_pr / open_pr / codebase / git write tool, and article create/update is not a customer-visible conversation reply. Feedback DevTools is honest about a different surface: create_github_issue / create_tracker_issue / mark_feedback_resolved plus source-mapped local-agent context with file:line. We do not claim server-side auto-opened or auto-merged PRs.
Feedback DevTools is our product. Intercom MCP tool surface sourced from https://www.intercom.com/integrations/connectors/intercom-mcp-server — lastChecked September 28, 2026 ~7:20pm Asia/Jerusalem. Please verify before purchase.
Feedback DevTools vs Intercom MCP
| Feedback DevTools | Intercom MCP | |
|---|---|---|
| Positioning | Capture + create_github_issue / create_tracker_issue / mark_feedback_resolved + local-agent file:line | Intercom data connector MCP — conversations / contacts / companies / Help Center articles for Claude / ChatGPT / Cursor / VS Code |
| Published MCP access | create_github_issue · create_tracker_issue · mark_feedback_resolved + local-agent file:line | Read: conversations, contacts, companies · Read/write: Help Center articles only (configure copy on intercom.com MCP page) |
| Create / update Help Center articles | N/A — FDT is feedback capture, not a Help Center CMS | Yes — article create/update from the AI tool (US-hosted workspaces) |
| Customer-visible reply-as-agent from MCP | N/A — FDT creates tracker tickets, not Intercom conversation replies | No published reply / send-message / assign-conversation tool — article write ≠ reply-as-agent |
| create_pr / open_pr / codebase / git write | No — create_github_issue + local-agent fix path (Cursor/Claude opens a PR if you ask; not an Intercom MCP PR tool) | No dedicated create_pr / open_pr / codebase / git write tool |
| Server-side auto-open / auto-merge PRs | No — we do not claim server-side auto PRs | No — published surface does not open or merge GitHub PRs |
| Source maps / file:line | Yes — capture-time React component + file:line | Conversations / contacts / companies / articles — Intercom workspace data, not React component file:line |
| Pricing shape | Unlimited free collection; Pro $9/mo per project | Intercom workspace plan + MCP connector (US-hosted); not a separate $9 MCP SKU |
Intercom MCP configure copy verified on intercom.com/integrations/connectors/intercom-mcp-server — lastChecked September 28, 2026 ~7:20pm Asia/Jerusalem
Where Intercom MCP is genuinely strong
Credit where due — Intercom MCP is a real support unlock if:
- You already run Intercom and want Claude/ChatGPT/Cursor/VS Code to query conversations, contacts, and companies without leaving the agent.
- Drafting or updating Help Center articles from the AI tool (read/write articles) fits your docs workflow on a US-hosted workspace.
- OAuth-scoped access matching existing Intercom permissions is the trust model you want.
Where Feedback DevTools is more honest about create_* / reply / PR
- Published surface vs ship/reply. intercom.com MCP page configures read conversations/contacts/companies + read/write articles — no create_pr and no customer-visible reply-as-agent tool (lastChecked September 28, 2026 ~7:20pm Asia/Jerusalem). Article write is Help Center CMS, not a conversation reply.
- Tickets with file:line. create_github_issue and create_tracker_issue open GitHub/Linear tickets whose bodies carry component + file:line from capture. Intercom's published surface has no create_github_issue / create_tracker_issue equivalent — it queries CRM data and edits articles.
- Local-agent path. The same context is handed to your coding agent; a PR, if any, is that agent's git workflow — not an Intercom MCP PR tool. FDT does not claim server-side auto-open or auto-merge.
- Capture-time source maps. Every item pins the React component and file path:line so the agent starts from a known path instead of rediscovering from an Intercom conversation alone.
- Pricing shape. Unlimited free collection; Pro is $9/mo per project.
Pricing shape (not the foil) (as of September 28, 2026)
- Intercom: workspace plan + MCP connector on intercom.com/integrations/connectors/intercom-mcp-server (US-hosted) (source: intercom.com/integrations/connectors/intercom-mcp-server)
- Feedback DevTools: Free (unlimited collection) · Pro $9/mo per project (source: feedback-devtools.com/pricing)
MCP honesty is about capability claims, not sticker shock — FDT Pro is $9/mo per project vs Intercom as a full support suite with MCP as a data connector.
Who should pick which?
- Choose Intercom MCP if your evidence archive is Intercom conversations/contacts/companies/articles and you want agents to query that data (and edit Help Center articles) inside Claude/ChatGPT/Cursor/VS Code.
- Choose Feedback DevTools if you want visual feedback with file:line on capture, MCP tools that create GitHub/Linear tickets (create_github_issue / create_tracker_issue), and a local-agent fix path — without reading Intercom article write as create_pr or reply-as-agent.
Frequently asked questions
What does Intercom MCP publish as its tool surface?
Per https://www.intercom.com/integrations/connectors/intercom-mcp-server (lastChecked September 28, 2026 ~7:20pm Asia/Jerusalem): query conversations, contacts, companies, and Help Center articles; create or update articles. Configure copy: read access to conversations, contacts, and companies, plus read and write access to Help Center articles. US-hosted workspaces; OAuth scoped to existing Intercom permissions; endpoint https://mcp.intercom.com/mcp.
Does Intercom MCP create pull requests or reply to customers as an agent?
No create_pr / open_pr / codebase / git write tool is published, and article create/update is Help Center CMS — not a customer-visible conversation reply / send-message tool (lastChecked September 28, 2026 ~7:20pm Asia/Jerusalem). A PR or customer reply, if any, is the coding / support agent using Intercom context — not those Intercom MCP tools.
How does Feedback DevTools MCP foil Intercom MCP?
FDT is honest about a different surface: capture-time component + file:line, create_github_issue / create_tracker_issue / mark_feedback_resolved, and a local-agent path. Intercom MCP is strong at workspace CRM/Help-Center data + article R/W. Buyers should read the configure copy rather than assuming create_pr or reply-as-agent. Distinct from Sprig#75 / Maze#73 / Canny#72 / Enterpret#71 / LogRocket#70.
Try Feedback DevTools free — create_github_issue / create_tracker_issue with file:line, no server-side auto-PR or reply-as-agent claims.