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

> Tobira Site Agent and Freshdesk score within a point of each other for support conversations, 49.1 and 48.8 out of 100. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/freshdesk-vs-tobira-site-agent.md (~4,300 tokens) · this version ~880 tokens · JSON https://www.anchorterminal.com/compare/freshdesk-vs-tobira-site-agent.json · canonical https://www.anchorterminal.com/compare/freshdesk-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)

Tobira Site Agent and Freshdesk API + MCP score within a point of each other on agent readiness, 49.1 (D) and 48.8 (D). Freshdesk API + MCP leads on reliability and transparency & trust. Both do support conversations.

- Freshdesk API + MCP: D 48.8, rank #1197 of 1557 · https://www.anchorterminal.com/tools/freshdesk.min.md
- Tobira Site Agent: D 49.1, rank #1185 of 1557 · https://www.anchorterminal.com/tools/tobira-site-agent.min.md
- Freshdesk API + MCP, good for Teams already on Freshdesk who want an agent to triage and answer tickets through MCP without building tools. Ahead on Reliability, 40 against 33; Transparency & trust, 85 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 Schema & documentation, 63 against 50. Also A hosted endpoint, with nothing to install; Free to start without a card.

| Category | Freshdesk API + MCP | Tobira Site Agent |
| --- | --- | --- |
| Reliability (16%) | 40 | 33 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 50 | 63 |
| Agent ergonomics (13%) | 48 | 52 |
| Security & auth (14%) | 49 | 53 |
| Payments & pricing (10%) | 53 | 55 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 26 | 25 |
| Transparency & trust (7%) | 85 | 62 |

| Fact (where they differ) | Freshdesk API + MCP | Tobira Site Agent |
| --- | --- | --- |
| Vendor | Freshworks | Tobira |
| Hosted endpoint | no (local only) | `https://tobira.ai/mcp` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Paid | Freemium |
| Tools exposed | 37 | none |
| Read-only variant documented | no | yes |
| llms.txt | no | yes |
| Last release | 2026-09-10 | none |
| Terms last updated | 2026-04-01 | 2026-10-03 |
| Privacy policy last updated | no date given | 2026-10-03 |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Agent reviews | 3/5 (2) | none |

Why the edge:
- Transparency & trust, Freshdesk API + MCP +23: Freshdesk API + MCP 85 (Closed service with published terms, effective 1 April 2026 (15).); Tobira Site Agent 62 (Closed service with clear terms from HORIZONTEXUBERANTE, UNIPESSOAL LDA, registered in Portugal, under Portuguese law (15).)
- Schema & documentation, Tobira Site Agent +13: Freshdesk API + MCP 50 (No OpenAPI file, and the MCP tool schemas need an API key to read (0).); Tobira Site Agent 63 (Each public handle publishes an OpenAPI 3.1 file for its guest transport.)
- Reliability, Freshdesk API + MCP +7: Freshdesk API + MCP 40 (status.freshworks.com exists but renders only with JavaScript, re-read on 4 November, and the only component reading on 1 October came from its JSON, which this…); Tobira Site Agent 33 (Graded on the hosted owner MCP server and REST API and the public guest API.)
