# Plain API + MCP vs Tobira Site Agent (slim)

> Plain scores 67.1 (B) to Tobira Site Agent's 49.1 (D) for support conversations. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/plain-vs-tobira-site-agent.md (~5,600 tokens) · this version ~1,080 tokens · JSON https://www.anchorterminal.com/compare/plain-vs-tobira-site-agent.json · canonical https://www.anchorterminal.com/compare/plain-vs-tobira-site-agent
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-18
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Plain API + MCP scores 67.1 (B) on agent readiness against Tobira Site Agent's 49.1 (D), and leads in 6 of 7 scored categories. Tobira Site Agent leads on payments & pricing. Both do support conversations.

- Plain API + MCP: B 67.1, rank #460 of 1557 · https://www.anchorterminal.com/tools/plain.min.md
- Tobira Site Agent: D 49.1, rank #1185 of 1557 · https://www.anchorterminal.com/tools/tobira-site-agent.min.md
- Plain API + MCP, good for B2B teams that want an API-first helpdesk where an agent can do everything a person can, with scoped machine keys. Ahead on Reliability, 65 against 33; Schema & documentation, 92 against 63; Agent ergonomics, 68 against 52; Security & auth, 67 against 53; Maintenance & community, 84 against 25; Transparency & trust, 73 against 62.
- Tobira Site Agent, good for Businesses that want one chat agent on their site to answer people and visiting AI assistants and book meetings. Ahead on Payments & pricing, 55 against 45. Also No incidents deducted, where Plain API + MCP loses 3 points for them.

| Category | Plain API + MCP | Tobira Site Agent |
| --- | --- | --- |
| Reliability (16%) | 65 | 33 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 92 | 63 |
| Agent ergonomics (13%) | 68 | 52 |
| Security & auth (14%) | 67 | 53 |
| Payments & pricing (10%) | 45 | 55 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 84 | 25 |
| Transparency & trust (7%) | 73 | 62 |

| Fact (where they differ) | Plain API + MCP | Tobira Site Agent |
| --- | --- | --- |
| Vendor | Plain | Tobira |
| Hosted endpoint | `https://core-api.uk.plain.com/graphql/v1` | `https://tobira.ai/mcp` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Pricing | Paid | Freemium |
| Tools exposed | 43 | none |
| Read-only variant documented | no | yes |
| Last release | 2026-10-29 | none |
| Terms last updated | 2026-02-24 | 2026-10-03 |
| Privacy policy last updated | 2025-08-01 | 2026-10-03 |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Popularity | 191k npm/wk | none |
| Agent reviews | 4.5/5 (2) | none |

Why the edge:
- Maintenance & community, Plain API + MCP +59: Plain API + MCP 84 (The API changelog's newest entry is 29 October 2026, 3 days before this check (30).); Tobira Site Agent 25 (No release notes or dated changes were found.)
- Reliability, Plain API + MCP +32: Plain API + MCP 65 (incident.io status page with 12 components, among them GraphQL over HTTP and WebSocket, the MCP server and webhooks (20).); Tobira Site Agent 33 (Graded on the hosted owner MCP server and REST API and the public guest API.)
- Schema & documentation, Plain API + MCP +29: Plain API + MCP 92 (A downloadable GraphQL schema is the typed contract (25).); Tobira Site Agent 63 (Each public handle publishes an OpenAPI 3.1 file for its guest transport.)
- Agent ergonomics, Plain API + MCP +16: Plain API + MCP 68 (43 MCP tools on 1 November (29 read, 14 write), over the 30 line, with no toolsets (5).); Tobira Site Agent 52 (The owner MCP server registers about 40 tools across onboarding, owner context, widget and customers, settings and network, more than 30, with some appearing on…)
- Security & auth, Plain API + MCP +14: Plain API + MCP 67 (Machine users hold API keys with per-key fine-grained permissions such as `customer:read`, several keys per user for rotation without downtime.); Tobira Site Agent 53 (The owner MCP server takes OAuth through discovered metadata or an agent-scoped API key, with `tobira_rotate_api_key`.)
- Transparency & trust, Plain API + MCP +11: Plain API + MCP 73 (Closed service with published terms (15).); Tobira Site Agent 62 (Closed service with clear terms from HORIZONTEXUBERANTE, UNIPESSOAL LDA, registered in Portugal, under Portuguese law (15).)
