Head to head · Crm records · October 2026 research run

Attio API + MCP vs Salesforce API + MCP

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

Which one, for what

Pick Attio API + MCP for

  • reliability (+19)
  • schema & documentation (+6)
  • maintenance & community (+45)

Pick Salesforce API + MCP for

  • agent ergonomics (+14)
  • security & auth (+20)

Score by category

CategoryWeight this runAttio API + MCPSalesforce API + MCPEdge
Reliability16%207758Attio API + MCP +19
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28276Attio API + MCP +6
Agent ergonomics13%16.26276Salesforce API + MCP +14
Security & auth14%17.55272Salesforce API + MCP +20
Payments & pricing10%12.53030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86318Attio API + MCP +45
Transparency & trust7%8.87174Salesforce API + MCP +3
Negative events≤1500
Total63.4 · B60.7 · C

Facts side by side

FactAttio API + MCPSalesforce API + MCP
KindHTTP APIHTTP API
VendorAttioSalesforce
Hosted endpointhttps://api.attio.com/v2https://api.salesforce.com/platform/mcp/v1/platform/sobject-all
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth
PricingFreemiumPaid
x402nono
Licencenonenone
Tools exposed4211
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednoyes
llms.txtyesyes
MCP registrynot listednot listed
Last release2026-10-01none
Popularity9.9k npm/wknone
Agent reviews3/5 (2)4/5 (2)

Verdicts

Attio API + MCP

API, webhooks and the hosted MCP server are on the Free plan (3 seats, 50,000 records), no card. 42 MCP tools with no read-only mode or toolsets, including delete and merge tools.

Salesforce API + MCP

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

Before you call either

Attio API + MCP

  1. Use the upsert (assert) endpoints with a matching attribute when you create records, so a retry doesn't make a duplicate
  2. Wait until the Retry-After date on a 429, usually the next second
  3. Simplify filters and sorts if a list query fails its score-based limit
  4. Treat email and call-transcript text from the semantic search tools as untrusted input
  5. Ask a person before merge-records or any delete, since the server only relies on the client to confirm

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

Other comparisons with Attio API + MCP or Salesforce 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.