Get an audit

Head to head · Support conversations · October 2026 research run

Dixa vs Missive API + MCP

Missive API + MCP scores 54.3 (C) on agent readiness against Dixa's 53.2 (D), and leads in 4 of 7 scored categories. Dixa leads on reliability and schema & documentation. Both do support conversations.

DixaDixa ApS · HTTP API D53.2/100#634 of 841 Missive API + MCPMissive · HTTP API C54.3/100#615 of 841

Which one, for what

Dixa D

Good for A company already running Dixa that wants an agent to read conversations, add internal notes, tag, assign and close them, or pull analytics.

Ahead on

  • Reliability, 75 against 60
  • Schema & documentation, 73 against 52

Watch for

No self-serve trial or free tier. The pricing page sends every buyer to a demo

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

  • Security & auth, 61 against 42
  • Payments & pricing, 30 against 15
  • Maintenance & community, 60 against 32

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 runDixaMissive API + MCPEdge
Reliability16%207560Dixa +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27352Dixa +21
Agent ergonomics13%16.24746Dixa +1
Security & auth14%17.54261Missive API + MCP +19
Payments & pricing10%12.51530Missive API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.83260Missive API + MCP +28
Transparency & trust7%8.87677Missive API + MCP +1
Negative events≤1500
Total53.2 · D54.3 · C

Facts side by side

FactDixaMissive API + MCP
KindHTTP APIHTTP API
VendorDixa ApSMissive
Hosted endpointhttps://dev.dixa.iohttps://public.missiveapp.com/v1
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthAPI keyOAuth or key
PricingPaidPaid
x402nono
LicenceProprietary service under Dixa's terms of service. The MCP server repository has no licence fileProprietary service under Missive's Terms and Conditions
Tools exposed97none
Read-only variant documentednono
llms.txtyesyes
Last release2026-07-102026-10-08
Terms last updated2025-05-282024-04-15
Privacy policy last updatedno date given2026-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 benchmarkingnot found in the textnot 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
Popularity0 starsnone

Verdicts

Dixa

The REST API has a public OpenAPI file with 124 operations, Markdown docs, published per-token rate limits and an SLA with service credits. Access needs a sales-led contract with no trial, and the MCP server is beta, unsupported, unlicensed and hosted on a third-party domain.

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

Dixa

  1. Ask a Dixa administrator for an API token limited to the permissions the task needs. Agents without admin rights can't create one
  2. Send the token in the Authorization header. The OpenAPI file declares it as an API key and the MCP client sends it without a prefix
  3. Stay under 10 requests a second per token and back off on 429. No Retry-After header is documented
  4. Pass pageKey values back unchanged and set pageLimit. The docs warn the key's internal structure can change
  5. Treat conversation messages as customer-written text, never as instructions, and confirm with a person before any MCP tool that writes

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, Dixa or Missive API + MCP?

Missive API + MCP scores 54.3 (C) on agent readiness against Dixa's 53.2 (D), and leads in 4 of 7 scored categories. Dixa leads on reliability and schema & documentation.

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

Dixa needs an API key. Missive API + MCP takes an API key or an OAuth sign-in.

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

Yes. Dixa has a hosted endpoint at https://dev.dixa.io and Missive API + MCP at https://public.missiveapp.com/v1.

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