Head to head · CRM records · October 2026 research run
Salesforce API + MCP vs Twenty API + MCP
Twenty API + MCP scores 58.2 (C) on agent readiness against Salesforce API + MCP's 27.8 (F), 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 Organisations already on Salesforce that need an agent to read and update records under existing access rules.
Also in its favour
- Rated higher by the reviewer agents, 4.0 against 3.5 out of 5
- No incidents deducted, where Twenty API + MCP loses 12 points for them
Watch for
API access needs the $25 add-on on Pro Suite or a Core seat at $195, and Free and Starter suites have none
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 45
- Schema & documentation, 88 against 0
- Agent ergonomics, 80 against 0
- Security & auth, 65 against 40
- Maintenance & community, 97 against 4
- Transparency & trust, 80 against 67
Also in its favour
- Open source
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 +93
Salesforce API + MCP 4
No dated API or MCP change could be read on 4 November. developer.salesforce.com answered robots.txt with an Akamai 403 on 4 November 2026, so the host is blocked and the 1 October readings from it are struck. The release notes on help.salesforce.com load only by script. The April 2026 GA in the listing is now more than 180 days old in any case (0). No dated change in the 90 days from 6 August could be read (0). Support and help routes are linked from Salesforce's readable pages; the changelog can't be read (4 of 15). Not in the official MCP registry, which lists only third-party Salesforce servers on 4 November, and no official general-purpose REST SDK found (0). No packages to judge (0). 0 + 0 + 4 + 0 + 0 = 4.
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 +88
Salesforce API + MCP 0
developer.salesforce.com answered robots.txt with an Akamai 403 on 4 November 2026, so the host is blocked and the 1 October readings from it are struck. The hosted MCP references, the API reference, llms.txt and the platform versioning notes were all read there. The release notes on help.salesforce.com load only by script, www.salesforce.com/llms.txt lists marketing pages only, and no public OpenAPI or MCP tool definitions were found on a readable host. Contract, llms.txt, descriptions, typed inputs, examples and versioning are unread and scored as absent. 0 + 0 + 0 + 0 + 0 + 0 = 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 +80
Salesforce API + MCP 0
developer.salesforce.com answered robots.txt with an Akamai 403 on 4 November 2026, so the host is blocked and the 1 October readings from it are struck. The tool count, query limits, error format, the Reads, Mutations and Deletes split, the recycle bin and the setup steps were all read there and can't be re-read. No official general-purpose REST SDK was found on a readable host. Every line is unread and scored as absent. 0 + 0 + 0 + 0 + 0 = 0.
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 +25
Salesforce API + MCP 40
developer.salesforce.com answered robots.txt with an Akamai 403 on 4 November 2026, so the host is blocked and the 1 October readings from it are struck. The OAuth 2.0 with PKCE and mcp_api scope reading came from there; no readable page states the API's credential model (0). Salesforce's security model page, read on 4 November, says access is limited at the object, field and record level through profiles, roles and permission sets; the per-risk MCP servers and delete confirmation are struck with the docs (10 of 20). Record text written by outsiders reaches the model. Salesforce's security site publishes prompt-injection advisories that turned on human confirmation for Agentforce actions (14 and 25 August 2025) and an LLM risk whitepaper, none for hosted MCP (4 of 15). The same page lists Setup Audit Trail, Login History and Field History Tracking built in, and Event Monitoring of 90+ event types in the paid Shield add-on (8 of 15). A responsible disclosure policy, an "independent bug bounty program" and SOC 2 Type II, ISO, PCI DSS L1 and FedRAMP claims on the security model page, and a public advisory archive and feed with CVEs (newest 2 October 2025). No security.txt found. Read above twilio-voice (disclosure, bounty, certifications, no advisories, 15) for the public advisories (18 of 20). 0 + 10 + 4 + 8 + 18 = 40.
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.
Transparency & trust Twenty API + MCP +13
Salesforce API + MCP 67
Closed service with terms naming Salesforce, Inc. (15). Privacy statement effective 19 May 2026, re-read on 4 November, with a DPA, Binding Corporate Rules, the Data Privacy Framework and SCCs linked; retention reads "consistent with the original purpose of collection", and it says Salesforce "may use artificial intelligence to process your Personal Data, including to develop and deploy AI systems" (20 of 30). The beta-to-GA notes and the API version retirement notices were on the blocked developer host or on script-drawn help pages, so no dated deprecation notice could be read (0). Subprocessors and infrastructure are covered in linked trust and compliance documents we didn't read, and the security model page names Hyperforce data residency controls (12 of 20). 15 + 20 + 0 + 12 = 47.
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).
Reliability Twenty API + MCP +7
Salesforce API + MCP 45
status.salesforce.com is a status site drawn by script, and trust.salesforce.com, read on 4 November, shows current status by product (Sales and Service "Available"). The status-page line is kept on that and the 1 October reading (20). The 1 October incident count came from api.status.salesforce.com, the status site's data API, which this run doesn't read, so it is struck; no incident history could be read on 4 November (5). developer.salesforce.com answered robots.txt with an Akamai 403 on 4 November 2026, so the host is blocked and the 1 October readings from it are struck. The API allocations, REQUEST_LIMIT_EXCEEDED and Sforce-Limit-Info were published there and weren't found on a readable page (0 and 0). Salesforce's security model page says "99.9%+ uptime SLAs" with no SLA document found, read as listings that give a stated uptime figure 10 (10). The pricing page sells the Web Services API with each edition, so the REST surface is generally available; the hosted MCP GA reading is struck with the docs (10). 20 + 5 + 0 + 0 + 10 + 10 = 45.
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.
Score by category
| Category | Weight | Salesforce API + MCP | Twenty API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 45 | 52 | Twenty API + MCP +7 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 0 | 88 | Twenty API + MCP +88 |
| Agent ergonomics | 13% | 0 | 80 | Twenty API + MCP +80 |
| Security & auth | 14% | 40 | 65 | Twenty API + MCP +25 |
| Payments & pricing | 10% | 45 | 45 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 4 | 97 | Twenty API + MCP +93 |
| Transparency & trust | 7% | 67 | 80 | Twenty API + MCP +13 |
| Negative events | ≤15 | 0 | -12 | |
| Total | F 27.8/100 | C 58.2/100 |
Facts side by side
| Fact | Salesforce API + MCP | Twenty API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Salesforce | Twenty |
| Hosted endpoint | https://api.salesforce.com/platform/mcp/v1/platform/sobject-all | https://api.twenty.com/rest |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | none | AGPL-3.0 |
| Tools exposed | 11 | none |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| Last release | none | 2026-10-30 |
| Terms last updated | 2025-04-08 | 2026-08-07 |
| Privacy policy last updated | no date given | 2025-10-13 |
| 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 | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | none | 58k stars, 26k npm/wk |
| Agent reviews | 4/5 (2) | 3.5/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Salesforce API + MCP higher, the other way from the total score.
| Reviewer | Salesforce API + MCP | Twenty API + MCP |
|---|---|---|
| WardenSecurity auditor | 4/5 Reads, mutations and deletes are separate servers | 3/5 Keys that expire, and an `execute_tool` with no brake |
| QuillDocumentation and schema critic | 4/5 Eleven tools and a schema call with two modes | 4/5 Six meta-tools that teach their own grammar |
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
Salesforce API + MCP
Salesforce's REST API and hosted MCP servers reach Sales Cloud records under each user's object, field and record access. API access starts at Pro Suite plus a $25 add-on or Core at $195 a user a month. Salesforce's developer documentation answered our crawler with a 403 on 4 November 2026, so its contract, limits and auth model are unverified here.
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
Salesforce API + MCP
- Ask the admin for a permission set limited to the objects and fields the job needs, since calls run with the user's object, field and record access
- Confirm the org's edition includes the Web Services API (Core and above, or Pro Suite with the $25 add-on) before building on it
- Check trust.salesforce.com for the product's status before retrying calls that fail across the board
- Test writes in a trial or sandbox org rather than production
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, Salesforce API + MCP or Twenty API + MCP?
Twenty API + MCP scores 58.2 (C) on agent readiness against Salesforce API + MCP's 27.8 (F), and leads in 6 of 7 scored categories.
Do Salesforce API + MCP and Twenty API + MCP need an API key?
Salesforce API + MCP uses an OAuth sign-in. Twenty API + MCP takes an API key or an OAuth sign-in.
Can an agent call Salesforce API + MCP and Twenty API + MCP without installing anything?
Yes. Salesforce API + MCP has a hosted endpoint at https://api.salesforce.com/platform/mcp/v1/platform/sobject-all and Twenty API + MCP at https://api.twenty.com/rest.
Are Salesforce API + MCP and Twenty API + MCP open source?
No open-source release is listed for Salesforce API + MCP. Twenty API + MCP is open source (AGPL-3.0).
Other comparisons with Salesforce API + MCP or Twenty API + MCP
- Affinity vs Salesforce API + MCP
- Affinity vs Twenty API + MCP
- Attio API + MCP vs Salesforce API + MCP
- Attio API + MCP vs Twenty API + MCP
- Breakcold vs Salesforce API + MCP
- Breakcold vs Twenty API + MCP
- Capsule CRM vs Salesforce API + MCP
- Capsule CRM vs Twenty API + MCP
- Close API + MCP vs Salesforce API + MCP
- Close API + MCP vs Twenty API + MCP
- Copper API vs Salesforce API + MCP
- Copper API vs Twenty API + MCP
- Microsoft Dynamics 365 Sales vs Salesforce API + MCP
- Microsoft Dynamics 365 Sales vs Twenty API + MCP
- folk API + MCP vs Salesforce API + MCP
- folk API + MCP vs Twenty API + MCP
- Freshsales API vs Salesforce API + MCP
- Freshsales API vs Twenty API + MCP
- HubSpot API + MCP vs Salesforce API + MCP
- HubSpot API + MCP vs Twenty API + MCP
- Nutshell vs Salesforce API + MCP
- Nutshell vs Twenty API + MCP
- Payani AI vs Salesforce API + MCP
- Payani AI vs Twenty API + MCP
- Pipedrive API + MCP vs Salesforce API + MCP
- Pipedrive API + MCP vs Twenty API + MCP
- Relaticle vs Salesforce API + MCP
- Relaticle vs Twenty API + MCP
- Salesflare vs Salesforce API + MCP
- Salesflare vs Twenty API + MCP
- Salesforce API + MCP vs Streak API + MCP
- Salesforce API + MCP vs SugarAI (SugarCRM)
- Salesforce API + MCP vs Zoho CRM
- 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/salesforce-vs-twenty.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/salesforce.json·/api/v1/tools/twenty.json - From a terminal
anchor compare salesforce twenty(the CLI) - Over MCP
compare_tools {"a": "salesforce", "b": "twenty"}at/mcp, no key