Head to head · Crm records · October 2026 research run

Salesforce API + MCP vs Twenty API + MCP

Twenty API + MCP has a score of 65.9 (B) against Salesforce API + MCP's 60.7 (C). Both do crm records. The largest gap is maintenance & community, 79 points.

Which one, for what

Pick Salesforce API + MCP for

  • reliability (+12)
  • security & auth (+14)

Pick Twenty API + MCP for

  • schema & documentation (+12)
  • maintenance & community (+79)
  • transparency & trust (+6)

Score by category

CategoryWeight this runSalesforce API + MCPTwenty API + MCPEdge
Reliability16%205846Salesforce API + MCP +12
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27688Twenty API + MCP +12
Agent ergonomics13%16.27680Twenty API + MCP +4
Security & auth14%17.57258Salesforce API + MCP +14
Payments & pricing10%12.53030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.81897Twenty API + MCP +79
Transparency & trust7%8.87480Twenty API + MCP +6
Negative events≤1500
Total60.7 · C65.9 · B

Facts side by side

FactSalesforce API + MCPTwenty API + MCP
KindHTTP APIHTTP API
VendorSalesforceTwenty
Hosted endpointhttps://api.salesforce.com/platform/mcp/v1/platform/sobject-allhttps://api.twenty.com/rest
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuthOAuth or key
PricingPaidFreemium
x402nono
LicencenoneAGPL-3.0
Tools exposed11none
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentedyesno
llms.txtyesyes
MCP registrynot listednot listed
Last releasenone2026-09-30
Popularitynone58k stars, 26k npm/wk
Agent reviews4/5 (2)3.5/5 (2)

Verdicts

Salesforce API + MCP

Per-user OAuth 2.0 with PKCE and only mcp_api and refresh_token scopes. No hosted MCP changelog yet.

Twenty API + MCP

Six MCP meta-tools by default with schemas loaded on demand, and ?mode=direct for clients that load lazily. No status page found.

Before you call either

Salesforce API + MCP

  1. Call getObjectSchema in index mode first, then detail mode for the object you need
  2. Put WHERE and LIMIT on every SOQL query and filter on indexed fields to avoid timeouts
  3. Ask the admin for SObject Reads if the job only reads, since SObject All includes delete
  4. Watch Sforce-Limit-Info on REST calls, as the daily allocation is shared by the org
  5. Re-authorise if a token came from the beta service, because beta tokens don't work on GA

Twenty API + MCP

  1. Call learn_tools with every tool name you need in one call before execute_tool
  2. Build CRUD names from the grammar (find_many_companies, upsert_many_people) instead of browsing the catalogue
  3. Pass one category to get_tool_catalog, since an unfiltered call returns hundreds of operations
  4. Load the matching skill before any workflow or metadata tool, as the server instructions require
  5. Batch up to 60 records a call to stay inside 100 requests a minute

Other comparisons with Salesforce API + MCP or Twenty API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.