Head to head · Support conversations · October 2026 research run
Missive API + MCP vs Tobira Site Agent
Missive API + MCP scores 55.3 (C) on agent readiness against Tobira Site Agent's 49.1 (D), and leads in 4 of 7 scored categories. Tobira Site Agent leads on schema & documentation, agent ergonomics and payments & pricing. Both do support conversations.
Best customer support and helpdesk APIs for AI agents · All 232 support comparisons
Which one, for what
Best 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
- Reliability, 60 against 33
- Security & auth, 61 against 53
- Maintenance & community, 50 against 25
- Transparency & trust, 77 against 62
Watch for
REST tokens are personal with no scopes and reach every account the user can open, shared accounts included
Best for Businesses that want one chat agent on their site to answer people and visiting AI assistants and book meetings.
Ahead on
- Schema & documentation, 63 against 52
- Agent ergonomics, 52 against 46
- Payments & pricing, 55 against 45
Watch for
No status page, changelog or SLA, and the terms promise no particular uptime
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Reliability Missive API + MCP +27
Missive API + MCP 60
Graded as a hosted service. status.missiveapp.com is a PagerDuty status page with eight components, one of them REST API, per the 8 October check, not re-read on 4 November because its robots.txt request answers with the status app's HTML page (20). The incident history was not read on either date (5). REST limits are 5 concurrent requests, 300 a minute and 900 per 15 minutes, and MCP limits are 60 a minute and 600 an hour per user (15). A 429 carries Retry-After and three X-RateLimit headers and the docs give pacing guidance, but no idempotency key or safe-retry guidance for draft and message writes was found (10). No SLA is published. The security FAQ lists uptime figures for 2020 to 2023 only, per the 8 October check (0). The REST API is generally available and the MCP server left beta on 28 August 2026 (10).
Tobira Site Agent 33
Graded on the hosted owner MCP server and REST API and the public guest API. No status page was found on tobira.ai, llms.txt or the API guide (0). No readable incident history (5). Numbers are published only for some limits: site-draft bootstrap at 20 new drafts a day per IP, Cloudflare traffic reports at ten an agent a minute, and the plan's monthly conversation allowances. No per-key request limit is given for the owner API or the guest API (8 of 15). The guide says to honour Retry-After or retry_after on 429, not to repeat account, session, booking or key creation on retries, and to reuse booking idempotency keys (15). The terms say 'we do not promise a particular uptime' and no SLA was found (0). The network is early access and several routes are rollout gated, though Site Agent plans are on sale (5 of 10). 0+5+8+15+0+5 = 33.
Maintenance & community Missive API + MCP +25
Missive API + MCP 50
Graded on the REST API and MCP server, so changelog entries about app functions the API doesn't serve are not counted. The newest entry naming the API or the MCP server is version 11.36.0 on 24 September 2026, which made the MCP server available on trial, 41 days before this check. Versions 11.37.0 (8 October), 11.37.1 (20 October) and 11.38.0 (23 October) cover app functions only (20). Four dated entries since 6 August name API or MCP server changes, on 14 August (add_default_signature on drafts), 28 August (MCP server out of beta), 10 September (signature variables in drafts made through the API and MCP server) and 24 September (20). Support is by email, there is a public feedback board and the changelog names API fixes, with no public issue tracker (10). No official SDK was found (0). There is no package to assess (0).
Tobira Site Agent 25
No release notes or dated changes were found. The newest dated first-hand pages are the terms, privacy policy and DPA, all of 3 October 2026, 46 days before this check (20). No changelog, so no dated entries can be counted (0). Closed service with no public changelog. Support by email and 'Human support, reply within 2 business days' on the Lite plan. We didn't test support (5 of 15). Not in the official MCP registry (searched for tobira on 18 November 2026) and no official SDK (0). No public packages or repositories found (0). 20+0+5+0+0 = 25.
Transparency & trust Missive API + MCP +15
Missive API + MCP 77
Closed service under Terms and Conditions last updated 15 April 2024, which name Heliom inc. and Quebec law (15). The privacy policy of 27 March 2026 says staff do not read user data without consent or a security need (per the 8 October check), the terms keep data retrievable for 30 days after termination, and a DPA is available on request. No general retention periods are given. The security page now names AWS and Crunchy Bridge, in line with the sub-processor list, where on 8 October it named Heroku. The line keeps its earlier partial value (20). No deprecation policy was found, and the terms let Missive modify or terminate API access with or without notice (4). The GDPR page, last updated 15 July 2025, lists 13 sub-processors with locations and an RSS feed, and the security FAQ says all servers run in AWS us-east-1, per the 8 October check (18).
Tobira Site Agent 62
Closed service with clear terms from HORIZONTEXUBERANTE, UNIPESSOAL LDA, registered in Portugal, under Portuguese law (15). The privacy policy and DPA (both 3 October 2026) agree with the terms. Retention is mostly by criteria, with some periods (guest sessions seven days, guest files 24 hours to seven days, attribution 30 days, a 30-day restoration window after agent deletion). Tobira says it doesn't train foundation models on conversations, and gives no guarantee for providers (22 of 30). The terms give 30 days' notice of material contractual changes, with no API deprecation policy (5 of 20). Providers are named with what they receive and where (mostly the United States) (16 of 20). 15+22+5+16 = 58.
Schema & documentation Tobira Site Agent +11
Missive API + MCP 52
No OpenAPI or other machine-readable contract was found in the developer docs, and the MCP tool definitions were not read because mcp.missiveapp.com disallows every path in robots.txt (0). The docs publish llms.txt and a Markdown twin of every page (10). The endpoints reference covers 44 method and path forms and says when to use posts, drafts or the silent conversation update (14). Parameters are in tables with types, defaults, maximums and required marks, not in a schema (8). Request and response examples are plentiful, but errors are limited to a few 400 and 404 cases with no error format (8). The path is versioned /v1 and the dated changelog names API changes, though the WhatsApp identifier change marked breaking in the docs has no changelog entry we found (12).
Tobira Site Agent 63
Each public handle publishes an OpenAPI 3.1 file for its guest transport. @tobira-ai's has five operations (ask, guest session, message, messages poll and action) with typed parameters such as q at 1 to 2,000 characters. The owner REST API has no published OpenAPI found, and the owner MCP server's schemas are only in tools/list, which answered 401 without a token (15 of 25). llms.txt, AGENTS.md, for-ai pages and a Markdown API and MCP guide (10). The guide says which credential fits which job and when not to use a surface (the read-only ask cannot book or take contact details), and lists tools by area, but no tool descriptions were readable (14 of 20). Action inputs are listed with ranges (days 1 to 31, default 7) and required fields, and guest OpenAPI parameters carry length limits (10 of 15). Request examples throughout and error classes 400, 401, 403, 404, 409, 422 and 429 with named codes such as stale_revision, csrf_failed and bootstrap_ip_limit (11 of 15). The guest OpenAPI carries a dated version (2026-05-27.stage1) but no public changelog was found (3 of 15). 15+10+14+10+11+3 = 63.
Payments & pricing Tobira Site Agent +10
Missive API + MCP 45
No x402, MPP or L402 (0). Plan prices are public at $14, $24 and $36 a user a month billed yearly, or $18, $30 and $45 monthly, with nothing priced per call (10). A 30-day trial of the Productive plan needs no card, and the changelog of 24 September 2026 says the MCP server can be enabled on a trial (20). A person signs up in a browser, and the MCP authorisation flow cannot create an account (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Tobira Site Agent 55
No x402, MPP or L402. Payments go through Stripe or the business's Cal.com checkout, completed by a human (0). Plan prices are public (Free $0, Lite $49, Start $169, Business $399, Premium $799 a month, with six-month and yearly discounts and setup fees), with no per-call price (15 of 30). The Free plan uses the owner's own AI key, allows up to 1,000 conversations a month and is 'Free to start, no card' on the official agent's page (30). The guest API needs no account, so a visiting agent can call a business's site agent keyless, but creating or managing a Site Agent needs an owner's browser sign-in, so partial (10 of 30). 0+15+30+10 = 55.
Security & auth Missive API + MCP +8
Missive API + MCP 61
The REST API takes a personal access token with no scopes that reaches every account the user can open, sent only in the Authorization header. The MCP server uses OAuth with PKCE, automatic client registration, the resource parameter, eight permissions and 30-day access that the user can revoke. Scored between the two (22). MCP read permissions are separate from write ones and drafting from sending, but the docs say MCP writes run immediately with no server-side confirmation, and admins cannot restrict apps or permissions (12). The MCP docs tell users to make the client ask before running tools and to check the redirect URL. No prompt-injection guidance was found for message content (4). A connected-apps list shows scopes, last IP and last use, API posts leave a visible trace, and the feature list claims an audit trail of every action. No per-call API log was found (7). security.txt is valid until 13 July 2027, there is a disclosure programme with discretionary rewards, and Missive states SOC 2 Type II with the report on request. No public advisories page was found (16).
Tobira Site Agent 53
The owner MCP server takes OAuth through discovered metadata or an agent-scoped API key, with tobira_rotate_api_key. Collaborator tokens are scoped, and visitor MCP tokens are scoped to one company and revocable. An OAuth grant covers every agent in the account, and the guide documents the guest token in the GET /api/v1/guest/messages?token= query string, so less 10 (16 of 30). Guests, visitors and collaborators can't edit an agent or read owner context, owner-only knowledge stays out of public answers, and bookings and contact submissions need the user's authorisation, with payment left to the human (15 of 20). Visiting agents are treated as untrusted guests and owner-private notes are kept out of their context, but no guidance was found for owners' agents reading guest messages through tobira_check_inbox (8 of 15). Conversations are tagged by source, and activity metrics and lead and booking lists are readable, with no audit log (6 of 15). A valid security.txt (security@tobira.ai, expires 5 November 2027) and a DPA on paid plans, with no disclosure policy, bounty or certification found (8 of 20). 16+15+8+6+8 = 53.
Score by category
| Category | Weight | Missive API + MCP | Tobira Site Agent | Edge |
|---|---|---|---|---|
| Reliability | 16% | 60 | 33 | Missive API + MCP +27 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 52 | 63 | Tobira Site Agent +11 |
| Agent ergonomics | 13% | 46 | 52 | Tobira Site Agent +6 |
| Security & auth | 14% | 61 | 53 | Missive API + MCP +8 |
| Payments & pricing | 10% | 45 | 55 | Tobira Site Agent +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 50 | 25 | Missive API + MCP +25 |
| Transparency & trust | 7% | 77 | 62 | Missive API + MCP +15 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 55.3/100 | D 49.1/100 |
Facts side by side
| Fact | Missive API + MCP | Tobira Site Agent |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Missive | Tobira |
| Hosted endpoint | https://public.missiveapp.com/v1 | https://tobira.ai/mcp |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | Proprietary service under Missive's Terms and Conditions | none |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| Last release | 2026-09-24 | none |
| Terms last updated | 2024-04-15 | 2026-10-03 |
| Privacy policy last updated | 2026-03-27 | 2026-10-03 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
How the scores have moved
Tobira Site Agent
No score change since it was listed.
Verdicts
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.
Tobira Site Agent
Visiting agents get a keyless guest API with a per-business OpenAPI file and booking actions that need the user's consent, and owners get an MCP server and REST API. The owner tool list is long and unpublished as schemas, there is no status page or changelog, and owner setup needs a browser sign-in.
Before you call either
Missive API + MCP
- 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 - Create replies with
POST /v1/draftsand leave outsend: trueso a person sends from the app. Withsend: truethe message goes out at once - Pass a mailbox filter such as
inbox,team_inboxorshared_labeltoGET /v1/conversations, and page withuntilset to the oldestlast_activity_at - Keep to one request a second for steady work or five a second in bursts, and wait the
Retry-Afterseconds on 429 - For MCP, connect to
https://mcp.missiveapp.com, grant Create drafts without Send messages, and treat message bodies as untrusted text
Tobira Site Agent
- Read the business's
https://tobira.ai/@{handle}/for-aipage orguest-agent.jsonfirst, and use only the actions its manifest advertises - Create one guest session and keep its token for follow-up questions. Don't open a new session per turn
- Get the user's explicit consent before
prepare_bookingorsubmit_authorized_contact, and reuse the sameidempotency_keyon retries - Hand any
checkout_urlto the human to pay, and treat onlybooking_confirmedas a confirmed booking - Don't put private details in the read-only
ask?q=URL, which can appear in proxy and browser logs
Questions
Which is better for AI agents, Missive API + MCP or Tobira Site Agent?
Missive API + MCP scores 55.3 (C) on agent readiness against Tobira Site Agent's 49.1 (D), and leads in 4 of 7 scored categories. Tobira Site Agent leads on schema & documentation, agent ergonomics and payments & pricing.
Do Missive API + MCP and Tobira Site Agent need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Missive API + MCP and Tobira Site Agent without installing anything?
Yes. Missive API + MCP has a hosted endpoint at https://public.missiveapp.com/v1 and Tobira Site Agent at https://tobira.ai/mcp.
Other comparisons with Missive API + MCP or Tobira Site Agent
- Chatway MCP vs Missive API + MCP
- Chatway MCP vs Tobira Site Agent
- Chatwoot API vs Missive API + MCP
- Chatwoot API vs Tobira Site Agent
- Crisp API + MCP vs Missive API + MCP
- Crisp API + MCP vs Tobira Site Agent
- Dixa vs Missive API + MCP
- Dixa vs Tobira Site Agent
- Drag vs Missive API + MCP
- Drag vs Tobira Site Agent
- FreeScout vs Missive API + MCP
- FreeScout vs Tobira Site Agent
- Freshdesk API + MCP vs Missive API + MCP
- Freshdesk API + MCP vs Tobira Site Agent
- Front API + MCP vs Missive API + MCP
- Front API + MCP vs Tobira Site Agent
- Gladly vs Missive API + MCP
- Gladly vs Tobira Site Agent
- Gorgias API + MCP vs Missive API + MCP
- Gorgias API + MCP vs Tobira Site Agent
- Help Scout API + MCP vs Missive API + MCP
- Help Scout API + MCP vs Tobira Site Agent
- Intercom API + MCP vs Missive API + MCP
- Intercom API + MCP vs Tobira Site Agent
- Kustomer vs Missive API + MCP
- Kustomer vs Tobira Site Agent
- LiveAgent vs Missive API + MCP
- LiveAgent vs Tobira Site Agent
- Missive API + MCP vs Plain API + MCP
- Missive API + MCP vs Pylon API + MCP
- Missive API + MCP vs Zammad
- Missive API + MCP vs Zendesk Support API
- Missive API + MCP vs Zoho Desk
- Plain API + MCP vs Tobira Site Agent
- Pylon API + MCP vs Tobira Site Agent
- Tobira Site Agent vs Zammad
- Tobira Site Agent vs Zendesk Support API
- Tobira Site Agent vs Zoho Desk
- HelpDesk vs Missive API + MCP
- HelpDesk vs Tobira Site Agent
Machine-readable
- This page as Markdown
/compare/missive-vs-tobira-site-agent.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/missive.json·/api/v1/tools/tobira-site-agent.json - From a terminal
anchor compare missive tobira-site-agent(the CLI) - Over MCP
compare_tools {"a": "missive", "b": "tobira-site-agent"}at/mcp, no key