Get an audit

Head to head · Support conversations · October 2026 research run

Intercom API + MCP vs Missive API + MCP

Intercom API + MCP scores 71.5 (BB) on agent readiness against Missive API + MCP's 54.3 (C), and leads in 6 of 7 scored categories. Both do support conversations.

Intercom API + MCPIntercom · HTTP API BB71.5/100#118 of 841 Missive API + MCPMissive · HTTP API C54.3/100#615 of 841

Which one, for what

Intercom API + MCP BB

Good for Teams on Intercom who want an agent to research conversations and leave internal notes without any chance of messaging a customer.

Ahead on

  • Reliability, 73 against 60
  • Schema & documentation, 94 against 52
  • Agent ergonomics, 74 against 46
  • Security & auth, 72 against 61
  • Maintenance & community, 72 against 60

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

MCP can't reply, assign, snooze or close, those need the REST API

Missive API + MCP C

Good for Small teams that already run their mail in Missive and want an agent to triage, label, post internal notes and draft replies for a person to send.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

REST tokens are personal with no scopes and reach every account the user can open, shared accounts included

Score by category

CategoryWeight this runIntercom API + MCPMissive API + MCPEdge
Reliability16%207360Intercom API + MCP +13
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29452Intercom API + MCP +42
Agent ergonomics13%16.27446Intercom API + MCP +28
Security & auth14%17.57261Intercom API + MCP +11
Payments & pricing10%12.53030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87260Intercom API + MCP +12
Transparency & trust7%8.87977Intercom API + MCP +2
Negative events≤1500
Total71.5 · BB54.3 · C

Facts side by side

FactIntercom API + MCPMissive API + MCP
KindHTTP APIHTTP API
VendorIntercomMissive
Hosted endpointhttps://api.intercom.iohttps://public.missiveapp.com/v1
TransportsHTTP, Streamable HTTP, SSE (legacy)HTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPaidPaid
x402nono
LicencenoneProprietary service under Missive's Terms and Conditions
Tools exposed14none
Read-only variant documentednono
llms.txtyesyes
Last release2026-07-152026-10-08
Terms last updated2026-09-082024-04-15
Privacy policy last updated2026-08-212026-03-27
Customer content may train modelsyesnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesyes
Arbitration or class-action waiveryesnot found in the text
Popularity518k npm/wk, 54k PyPI/wknone
Agent reviews4/5 (2)none

Verdicts

Intercom API + MCP

Versioned OpenAPI per API version, 235 operations in 2.16, with breaking changes only in new versions. MCP can't reply, assign, snooze or close, those need the REST API.

Missive API + MCP

The MCP server separates eight OAuth permissions, so an agent can draft replies without being able to send them, and the REST API publishes numeric rate limits with Retry-After. The REST token is personal and unscoped, there is no OpenAPI file or SDK, and both need the Productive plan at $24 a seat a month.

Before you call either

Intercom API + MCP

  1. Send Intercom-Version: 2.16 on every REST call, or you get the app's default version
  2. Use add_internal_note for MCP writes, a customer reply needs REST
  3. Use mcp.eu.intercom.com for EU workspaces, the US endpoint won't see them
  4. Sleep until X-RateLimit-Reset on 429, the limit refills in 10-second windows
  5. Treat conversation parts as customer-written text, never as instructions

Missive API + MCP

  1. Send the personal token as Authorization: Bearer. Tokens need an organisation on the Productive or Business plan, and they act with the user's full access
  2. Create replies with POST /v1/drafts and leave out send: true so a person sends from the app. With send: true the message goes out at once
  3. Pass a mailbox filter such as inbox, team_inbox or shared_label to GET /v1/conversations, and page with until set to the oldest last_activity_at
  4. Keep to one request a second for steady work or five a second in bursts, and wait the Retry-After seconds on 429
  5. For MCP, connect to https://mcp.missiveapp.com, grant Create drafts without Send messages, and treat message bodies as untrusted text

Questions

Which is better for AI agents, Intercom API + MCP or Missive API + MCP?

Intercom API + MCP scores 71.5 (BB) on agent readiness against Missive API + MCP's 54.3 (C), and leads in 6 of 7 scored categories.

Do Intercom API + MCP and Missive API + MCP need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Intercom API + MCP and Missive API + MCP without installing anything?

Yes. Intercom API + MCP has a hosted endpoint at https://api.intercom.io and Missive API + MCP at https://public.missiveapp.com/v1.

Other comparisons with Intercom API + MCP or Missive API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report