Head to head · CRM records · October 2026 research run
Freshsales API vs Twenty API + MCP
Twenty API + MCP scores 58.2 (C) on agent readiness against Freshsales API's 39.5 (E), and leads in 6 of 7 scored categories. Both do crm records.
Best CRM and customer-platform tools for AI agents · All 190 crm comparisons
Which one, for what
Best for Small teams already paying for Freshworks who want an agent to upsert contacts and log activities through REST.
Also in its favour
- Free to start without a card
- No incidents deducted, where Twenty API + MCP loses 12 points for them
Watch for
No MCP server for Freshsales
Best for Teams that want an open-source CRM they can self-host or extend with custom objects, and an MCP server that stays cheap in context.
Ahead on
- Reliability, 52 against 36
- Schema & documentation, 88 against 27
- Agent ergonomics, 80 against 48
- Security & auth, 65 against 44
- Maintenance & community, 97 against 5
- Transparency & trust, 80 against 73
Also in its favour
- A hosted endpoint, with nothing to install
- Open source
- Rated higher by the reviewer agents, 3.5 against 2.0 out of 5
Watch for
No status page found
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.
Maintenance & community Twenty API + MCP +92
Freshsales API 5
No public API changelog or release notes for the Freshsales API found; the reference page was last modified on 9 October 2024 per its server header, so no last change date (0). No dated entries in the last 90 days found (0). Freshworks runs community forums, but there's no API changelog to follow (5 of 15). No official Freshsales SDK. The FDK is for marketplace apps, not API calls (0). No packages to judge (0). Freshworks' MCP integration articles cover Freshdesk and Freshservice, not Freshsales (checked 10 November 2026). 0 + 0 + 5 + 0 + 0 = 5.
Twenty API + MCP 97
twenty/v2.54.0 tagged on 30 October 2026, with sdk/v2.54.3 the same day (30). 19 server tags between 2 and 30 October 2026, twenty/v2.45.0 to v2.54.0 (20). Responsiveness per the 1 October check, 60 open issues with priority labels on recent bug reports within days, not re-read on 1 November because GitHub's pages refuse us (22 of 25). Not in the official MCP registry (only a third-party io.usefulapi/twenty), but the official twenty-sdk is tagged with every release, sdk/v2.54.3 on 30 October (15). CI covers server, front end, SDK, end-to-end tests and breaking changes, with commits on main every day from 28 October to 1 November (10).
Schema & documentation Twenty API + MCP +61
Freshsales API 27
No OpenAPI or other machine-readable spec found (0). No llms.txt or Markdown docs (0). One long HTML reference page with short endpoint descriptions and no when-not-to-use guidance (8 of 20). Field tables and filter bodies, with free-form filter JSON for views and search (8 of 15). curl examples throughout, an error format of errors.code and errors.message and a list of status codes (11 of 15). No version scheme or API changelog found (0).
Twenty API + MCP 88
Each workspace serves its own OpenAPI files at /rest/open-api/core and /rest/open-api/metadata, generated from its schema, custom objects included (25). llms.txt and Markdown docs (10). The MCP server sends instructions that explain the tool-name grammar, when to use get_tool_catalog and that workflow and metadata tools need their skill loaded first (18 of 20). Inputs are typed from the workspace schema and learn_tools returns them on demand (13 of 15). Docs examples and JSON-RPC error codes. We didn't find a REST error reference (10 of 15). Release notes at twenty.com/releases and a breaking-changes CI check, but the API itself isn't versioned beyond the generated schema (12 of 15).
Agent ergonomics Twenty API + MCP +32
Freshsales API 48
No MCP server for Freshsales. include embeds related records on request and lists default to 25 per page. No field selection to trim responses (10 of 25). page pagination, filtered views, search and filter endpoints (14 of 20). Errors carry a code and a message, with status codes documented (12 of 20). /api/contacts/upsert and bulk_upsert (100 records a request) give idempotent creates for contacts, but nothing similar for deals. bulk_destroy deletes in bulk (8 of 20). Every account has its own host, so an agent needs the bundle alias as well as the key, and there's no official SDK (4 of 15).
Twenty API + MCP 80
By default the MCP server lists six meta-tools (execute_tool, learn_tools, load_skills, list_object_metadata_names, list_skills, get_tool_catalog) and loads schemas on demand. ?mode=direct lists every tool for clients that load lazily (25). REST and GraphQL take limits, filters and cursors, and the tool layer strips empty values and compacts output (20). learn_tools returns unknown names under notFound with the closest matches (15 of 20). Read-only tools carry readOnlyHint. execute_tool is deliberately not marked destructive although it runs deletes, with a code comment saying clients would prompt on every call. upsert_many_* exists for safe retries (10 of 20). Few required parameters. TypeScript SDKs only (twenty-sdk, twenty-client-sdk) (10 of 15).
Security & auth Twenty API + MCP +21
Freshsales API 44
One per-user API key in Authorization: Token token=<key>, limited by that user's role and visibility. No scopes, no OAuth for the CRM API, and we found no rotation docs (13 of 30). No read-only key. Access is whatever the user's role allows, and bulk delete endpoints exist (3 of 20). Records carry email, notes and chat text from outside parties, and we found no injection guidance (3 of 15). Audit logs listed on the Enterprise plan (8 of 15). HackerOne disclosure programme, a security.txt with contact and policy (no Expires field), and ISO, AICPA and Cyber Essentials Plus logos on the security page (17 of 20).
Twenty API + MCP 65
API keys are Bearer tokens with a required expiry date, a revoked flag and an optional role binding. OAuth with dynamic client registration for MCP and apps. Tokens stay out of URLs (30). A key bound to a read-only role gives least privilege, but MCP has no read-only switch of its own, writes and deletes (including deleting objects and fields through metadata tools) run without a confirmation step, and the destructive hint is off by design (10 of 20). Records include email synced over IMAP and Gmail, and we found no injection guidance (3 of 15). The pricing table lists audit logs on Organization and Enterprise with retention up to three years, record change logs on every plan, and 2 hours of log retention on Pro (10 of 15, up from 7 now the plans are stated). security.txt with two contacts and a policy link but no Expires field, a SECURITY.md promising a reply within one business day, and Twenty publishes GitHub security advisories with CVE numbers (nine of the ten CVEs in the last twelve months came through them). No SOC 2 or bug bounty found, and SECURITY.md says there is no formal bounty (12 of 20, between anythingllm's 10 with no security.txt and open-webui's 14 with a dated one). 30 + 10 + 3 + 10 + 12 = 65.
Reliability Twenty API + MCP +16
Freshsales API 36
Freshworks runs its own status page at status.freshworks.com across products and regions, but it renders only with JavaScript and its components were never read in a way this run uses (the 1 October incidents API answer is struck), so no Freshsales component counts (0; freshdesk, same page, 4 November). No readable incident history (5). 1,000 API requests an hour per account, published (15). 429 is documented ("exceeded the API limit set per hour per account"), with no Retry-After or backoff guidance. Contact upsert and bulk upsert make creates safe to retry (6 of 15, an earlier partial held). No SLA found on the pricing page (0). The REST API is GA (10). 0 + 5 + 15 + 6 + 0 + 10 = 36.
Twenty API + MCP 52
No status page found. status.twenty.com still serves the Twenty app shell on 1 November, and the website links only a trust centre (0). No readable incident history (5). Limits published with numbers, 100 requests a minute and 60 records per batch in the API docs, and 50 a minute on Cloud Pro and 100 on Organization in the pricing table (15). The data-import guide says to use exponential backoff and watch for 429 responses, the apps guide says to retry a 429 with backoff and a cap on attempts, and GraphQL batch upserts and the MCP upsert_many_* tools give a safe retry for creates, with no idempotency keys (12 of 15, as e2b). The Enterprise plan lists 'Dedicated support & SLA' on the pricing page (10). REST, GraphQL and MCP carry no beta label (10). 0 + 5 + 15 + 12 + 10 + 10 = 52.
Transparency & trust Twenty API + MCP +7
Freshsales API 73
Closed service with terms naming Freshworks Inc. (15). Privacy notice effective 1 March 2026 keeps service data up to six years from supply and other data up to three years from last contact, transfers under the Data Privacy Framework and SCCs, and links a subprocessor page and a data hosting page (24 of 30). No API deprecation policy or dated notices found (0). Subprocessors and hosting regions on their own pages (18 of 20).
Twenty API + MCP 80
AGPL-3.0 core with an application exception, some files under a commercial enterprise licence and the SDKs under MIT, all spelled out in LICENSE (25 of 30). Privacy policy effective 13 October 2025 says cloud data is hosted in Frankfurt and kept until deletion, with backups isolated until deleted. No retention periods in days (22 of 30). Release notes and an upgrade guide, but no API deprecation policy found (8 of 20). Subprocessors listed with locations in a DPA file synced weekly by CI (AWS in Germany, ClickHouse, Anthropic, OpenAI, Mistral, Sentry and others). Self-hosted telemetry is on by default (TELEMETRY_ENABLED = true) and sends the new user's email and name to twenty-telemetry.com on sign-up. The privacy policy discloses optional telemetry and the switch exists, but the self-hosting docs don't mention it (14 of 20).
Score by category
| Category | Weight | Freshsales API | Twenty API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 36 | 52 | Twenty API + MCP +16 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 27 | 88 | Twenty API + MCP +61 |
| Agent ergonomics | 13% | 48 | 80 | Twenty API + MCP +32 |
| Security & auth | 14% | 44 | 65 | Twenty API + MCP +21 |
| Payments & pricing | 10% | 45 | 45 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 5 | 97 | Twenty API + MCP +92 |
| Transparency & trust | 7% | 73 | 80 | Twenty API + MCP +7 |
| Negative events | ≤15 | 0 | -12 | |
| Total | E 39.5/100 | C 58.2/100 |
Facts side by side
| Fact | Freshsales API | Twenty API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Freshworks | Twenty |
| Hosted endpoint | no (local only) | https://api.twenty.com/rest |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | none | AGPL-3.0 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | none | 2026-10-30 |
| Terms last updated | 2026-04-01 | 2026-08-07 |
| Privacy policy last updated | no date given | 2025-10-13 |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | none | 58k stars, 26k npm/wk |
| Agent reviews | 2/5 (2) | 3.5/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Twenty API + MCP higher.
| Reviewer | Freshsales API | Twenty API + MCP |
|---|---|---|
| QuillDocumentation and schema critic | 2/5 One HTML page and no machine-readable spec | 4/5 Six meta-tools that teach their own grammar |
| WardenSecurity auditor | 2/5 One key per user, with bulk delete in reach | 3/5 Keys that expire, and an `execute_tool` with no brake |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Freshsales API
Contact upsert and bulk upsert of up to 100 records make creates safe to retry. No MCP server for Freshsales.
Twenty API + MCP
Six MCP meta-tools by default load schemas on demand, and every workspace generates its own OpenAPI files. Ten CVEs were published against the server in the last twelve months, four Critical and all fixed, and there is still no status page, so self-hosters need to keep up with releases.
Before you call either
Freshsales API
- Build the base URL from the bundle alias shown under the API key,
https://<alias>.myfreshworks.com/crm/sales/api/ - Use
/api/contacts/upsertrather than create, so a retry updates instead of duplicating - Budget calls, since 1,000 an hour covers the whole account and 429s carry no Retry-After
- Add
include=owner,sales_accountsto pull related records in one call - Expect to see only what the key owner's role can see
Twenty API + MCP
- Call
learn_toolswith every tool name you need in one call beforeexecute_tool - Build CRUD names from the grammar (
find_many_companies,upsert_many_people) instead of browsing the catalogue - Pass one category to
get_tool_catalog, since an unfiltered call returns hundreds of operations - Load the matching skill before any workflow or metadata tool, as the server instructions require
- Batch up to 60 records a call and back off on 429, since Cloud Pro allows only 50 requests a minute
Questions
Which is better for AI agents, Freshsales API or Twenty API + MCP?
Twenty API + MCP scores 58.2 (C) on agent readiness against Freshsales API's 39.5 (E), and leads in 6 of 7 scored categories.
Do Freshsales API and Twenty API + MCP need an API key?
Freshsales API needs an API key. Twenty API + MCP takes an API key or an OAuth sign-in.
Can an agent call Freshsales API and Twenty API + MCP without installing anything?
No hosted endpoint is listed for Freshsales API. Twenty API + MCP has a hosted endpoint at https://api.twenty.com/rest.
Are Freshsales API and Twenty API + MCP open source?
No open-source release is listed for Freshsales API. Twenty API + MCP is open source (AGPL-3.0).
Other comparisons with Freshsales API or Twenty API + MCP
- Affinity vs Freshsales API
- Affinity vs Twenty API + MCP
- Attio API + MCP vs Freshsales API
- Attio API + MCP vs Twenty API + MCP
- Breakcold vs Freshsales API
- Breakcold vs Twenty API + MCP
- Capsule CRM vs Freshsales API
- Capsule CRM vs Twenty API + MCP
- Close API + MCP vs Freshsales API
- Close API + MCP vs Twenty API + MCP
- Copper API vs Freshsales API
- Copper API vs Twenty API + MCP
- Microsoft Dynamics 365 Sales vs Freshsales API
- Microsoft Dynamics 365 Sales vs Twenty API + MCP
- folk API + MCP vs Freshsales API
- folk API + MCP vs Twenty API + MCP
- Freshsales API vs HubSpot API + MCP
- Freshsales API vs Nutshell
- Freshsales API vs Payani AI
- Freshsales API vs Pipedrive API + MCP
- Freshsales API vs Relaticle
- Freshsales API vs Salesflare
- Freshsales API vs Salesforce API + MCP
- Freshsales API vs Streak API + MCP
- Freshsales API vs SugarAI (SugarCRM)
- Freshsales API vs Zoho CRM
- HubSpot API + MCP vs Twenty API + MCP
- Nutshell vs Twenty API + MCP
- Payani AI vs Twenty API + MCP
- Pipedrive API + MCP vs Twenty API + MCP
- Relaticle vs Twenty API + MCP
- Salesflare vs Twenty API + MCP
- Salesforce API + MCP vs Twenty API + MCP
- Streak API + MCP vs Twenty API + MCP
- SugarAI (SugarCRM) vs Twenty API + MCP
- Twenty API + MCP vs Zoho CRM
Machine-readable
- This page as Markdown
/compare/freshsales-vs-twenty.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/freshsales.json·/api/v1/tools/twenty.json - From a terminal
anchor compare freshsales twenty(the CLI) - Over MCP
compare_tools {"a": "freshsales", "b": "twenty"}at/mcp, no key