Get an audit

Head to head · Support conversations · October 2026 research run

Kustomer vs Missive API + MCP

Kustomer scores 57.3 (C) on agent readiness against Missive API + MCP's 54.3 (C), and leads in 5 of 7 scored categories. Missive API + MCP leads on payments & pricing and transparency & trust. Both do support conversations.

KustomerKustomer, LLC · HTTP API C57.3/100#553 of 841 Missive API + MCPMissive · HTTP API C54.3/100#615 of 841

Which one, for what

Kustomer C

Good for Larger support teams already on Kustomer who want an agent to read the full customer timeline and write messages, notes and status changes under a narrowly scoped key.

Ahead on

  • Reliability, 76 against 60
  • Schema & documentation, 63 against 52
  • Agent ergonomics, 56 against 46

Watch for

Plan prices are not published and no self-serve trial or signup was found, so a person has to go through sales

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.

Ahead on

  • Payments & pricing, 30 against 5
  • Transparency & trust, 77 against 64

Also in its favour

  • Free to start without a card

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 runKustomerMissive API + MCPEdge
Reliability16%207660Kustomer +16
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26352Kustomer +11
Agent ergonomics13%16.25646Kustomer +10
Security & auth14%17.56461Kustomer +3
Payments & pricing10%12.5530Missive API + MCP +25
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86160Kustomer +1
Transparency & trust7%8.86477Missive API + MCP +13
Negative events≤1500
Total57.3 · C54.3 · C

Facts side by side

FactKustomerMissive API + MCP
KindHTTP APIHTTP API
VendorKustomer, LLCMissive
Hosted endpointhttps://api.kustomerapp.com/v1https://public.missiveapp.com/v1
TransportsHTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPaidPaid
x402nono
LicenceProprietary service under Kustomer's Master Subscription AgreementProprietary service under Missive's Terms and Conditions
Read-only variant documentedyesno
llms.txtnoyes
Last release2026-10-062026-10-08
Terms last updated2026-06-182024-04-15
Privacy policy last updated2025-05-152026-03-27
Customer content may train modelsnot found in the textnot 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 noticenot found in the textyes
Arbitration or class-action waivernot found in the textnot found in the text

Verdicts

Kustomer

API keys carry granular roles, an expiry and an optional CIDR restriction, and the reference documents 449 operations with an OpenAPI definition on each page. Plan prices are not published and no self-serve trial was found, so access starts with a sales contact. The MCP server is read-only and limited to approved clients.

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

Kustomer

  1. Ask the admin for an API key with only the org.permission.* roles the task needs. Roles are fixed at creation, so a wider task needs a new key
  2. Send Authorization: Bearer <key> to https://api.kustomerapp.com/v1. Watch x-ratelimit-remaining, and on 429 wait until the epoch time in x-ratelimit-reset
  3. Keep searches under 100 requests a minute and updates to one conversation, message or company under 100 in 10 minutes. These limits are separate from the plan limit
  4. Writes have no idempotency key. Before retrying a failed create, check whether the record exists, for example through the get-message-by-external-ID operation, to avoid duplicates
  5. Use the MCP server only for reading. Replies, notes and status changes go through the REST API. Treat message text as customer-written data, 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, Kustomer or Missive API + MCP?

Kustomer scores 57.3 (C) on agent readiness against Missive API + MCP's 54.3 (C), and leads in 5 of 7 scored categories. Missive API + MCP leads on payments & pricing and transparency & trust.

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

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

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

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

Other comparisons with Kustomer 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