Head to head · CRM records · October 2026 research run

Attio API + MCP vs Salesforce API + MCP

Attio API + MCP scores 62.8 (B) 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

Attio API + MCP B

Best for Small teams and startups that want an agent to search across records, notes, emails and calls and then update the CRM, starting free.

Ahead on

  • Reliability, 77 against 45
  • Schema & documentation, 82 against 0
  • Agent ergonomics, 62 against 0
  • Security & auth, 56 against 40
  • Maintenance & community, 63 against 4

Also in its favour

  • Free to start without a card

Watch for

48 MCP tools with no read-only mode or toolsets, including delete and merge tools

Salesforce API + MCP F

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.0 out of 5
  • No incidents deducted, where Attio API + MCP loses 3 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

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.

Schema & documentation Attio API + MCP +82

Attio API + MCP 82

Three public OpenAPI files (API, standard objects, webhooks) at api.attio.com/openapi, per the 1 October check (25). llms.txt now lists 399 links, with Markdown copies of every page (10). Each MCP tool gets a one-line purpose and example prompts in the docs. We couldn't read the hosted server's own tool definitions, so when-not-to-use guidance is unchecked (12 of 20). Typed parameters in the OpenAPI, but filters are a nested JSON object the agent has to build (11 of 15). Examples on reference pages and a documented error body with status_code, type, code and message (12 of 15). Dated public changelogs for the REST API, the MCP server and the App SDK, but no versioning or deprecation policy beyond the v2 path (12 of 15). 25 + 10 + 12 + 11 + 12 + 12 = 82.

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.

Agent ergonomics Attio API + MCP +62

Attio API + MCP 62

The MCP server now lists 48 tools, after delete-task on 1 October and six activity tools on 14 October 2026, with no toolsets, no read-only subset and no dynamic loading (5). Semantic search tools over notes, emails and call recordings save a few listing calls (3 more, 8 of 25). REST lists take limit, offset, filters and sorts, and comment threads paginate at 80 replies and 250 comments a page (20). Errors carry a machine code and a message, and 429s say when to retry (15 of 20). The docs say the server uses MCP safety annotations, with reads auto-approved and writes asking the user to confirm in the client, and REST has upsert endpoints. We didn't read the annotations on the tools themselves (12 of 20). No official REST SDK in any language. The npm package attio is the App SDK CLI, not an API client (7 of 15). 8 + 20 + 15 + 12 + 7 = 62.

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.

Maintenance & community Attio API + MCP +59

Attio API + MCP 63

REST changelog entries on 28 October (writable avatar_url and logo_url), 27 October, 15 October and 14 October 2026, and MCP entries on 14 October and 1 October (30). Seventeen dated entries (13 REST, 4 MCP) across the REST and MCP changelogs since 4 August 2026 (20). Closed service with public changelogs and a support address. We didn't test support (10 of 15). Not in the official MCP registry. A search for attio on 2 November returns only third-party servers (kesslerio, kaszek, Smithery). No official REST SDK (0). The only npm package is the App SDK CLI, version not re-read (3 of 10). 30 + 20 + 10 + 0 + 3 = 63.

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.

Reliability Attio API + MCP +32

Attio API + MCP 77

status.attio.com moved to incident.io, with five components and data back to August 2020 (20). Its feed and 90-day bars show four incidents from 4 August to 2 November 2026, all partial. On 8 September, "Platform avaliblity issues", intermittent availability problems on Attio Cloud and the web client from 17:05 to monitoring at 17:24 UTC. On 28 September workflow execution and webhook delivery ran late for about 4 hours. On 6 October formula updates and on 12 October bulk record deletions were delayed on Background Tasks. Minor incidents only (20). Rate limits published, 100 reads and 25 writes a second, plus score-based limits on list queries in a 10-second window (15). 429s carry a Retry-After date and a JSON body, and the docs say rate-limited requests weren't processed and can be retried. Upsert (assert) endpoints give a safe retry for creates, but there's no idempotency key (12 of 15). No SLA found on the pricing page (0). REST v2 and the MCP server carry no beta label, though several newer endpoints do (10). 20 + 20 + 15 + 12 + 0 + 10 = 77.

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.

Security & auth Attio API + MCP +16

Attio API + MCP 56

Workspace API keys and OAuth tokens share one set of per-endpoint scopes, a token revocation endpoint shipped on 11 September 2026, and since 15 October OAuth tokens can be user-level, limited to one member's data and permissions. The MCP server is OAuth only and works as the signed-in user. HTTP Basic is supported but discouraged, and we found no query-string token option (27 of 30). A read-scoped key gives least privilege on REST. The MCP server has no read-only mode, its writes rely on client confirmation, and it can delete comments and tasks and merge records. A REST endpoint added on 4 September 2026 deletes a whole custom object, which the changelog calls destructive and irreversible (13 of 20). The MCP server returns email bodies, call transcripts and notes written by outsiders, and we found no prompt-injection guidance (2 of 15). No audit-log documentation found in the API or MCP docs. Attribute history on records is the nearest thing (4 of 15). attio.com publishes a Vulnerability Disclosure Policy with safe harbour, a 72-hour confirmation and a 90-day disclosure window covering app, api, cdn and attio.com, which the 1 October check didn't record. The DPA promises yearly third-party penetration tests and breach notice within 72 hours. The Vanta-hosted trust centre wasn't read, so certifications are unchecked. No security.txt (404 on 2 November) and no bug bounty found. agentvfs scores 7 for a disclosure policy alone, and the DPA's testing and breach commitments add 3 (10 of 20, was 6). 27 + 13 + 2 + 4 + 10 = 56.

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.

Score by category

CategoryWeightAttio API + MCPSalesforce API + MCPEdge
Reliability16%7745Attio API + MCP +32
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%820Attio API + MCP +82
Agent ergonomics13%620Attio API + MCP +62
Security & auth14%5640Attio API + MCP +16
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%634Attio API + MCP +59
Transparency & trust7%6967Attio API + MCP +2
Negative events≤15-30
TotalB 62.8/100F 27.8/100

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
Tools exposed4811
Read-only variant documentednoyes
llms.txtyesyes
Last release2026-10-28none
Terms last updated2025-11-012025-04-08
Privacy policy last updated2026-06-01no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity9.9k npm/wknone
Agent reviews3/5 (2)4/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Salesforce API + MCP higher, the other way from the total score.

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

Attio API + MCP

API, webhooks and the hosted MCP server are on the Free plan for 3 seats with no card, and REST keys and OAuth tokens take per-endpoint scopes. The 48 MCP tools have no read-only mode or toolsets and include delete and merge tools, and thread pagination changed on the day it was announced.

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.

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. Page through threads with cursor and limit. Get a thread returns at most 250 comments a request
  5. Ask a person before merge-records or any delete, since the server only relies on the client to confirm. Treat email and transcript text as untrusted input

Salesforce API + MCP

  1. 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
  2. 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
  3. Check trust.salesforce.com for the product's status before retrying calls that fail across the board
  4. Test writes in a trial or sandbox org rather than production

Questions

Which is better for AI agents, Attio API + MCP or Salesforce API + MCP?

Attio API + MCP scores 62.8 (B) on agent readiness against Salesforce API + MCP's 27.8 (F), and leads in 6 of 7 scored categories.

Do Attio API + MCP and Salesforce API + MCP need an API key?

Attio API + MCP takes an API key or an OAuth sign-in. Salesforce API + MCP uses an OAuth sign-in.

Can an agent call Attio API + MCP and Salesforce API + MCP without installing anything?

Yes. Attio API + MCP has a hosted endpoint at https://api.attio.com/v2 and Salesforce API + MCP at https://api.salesforce.com/platform/mcp/v1/platform/sobject-all.

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.