Get an audit

Head to head · Crm records · October 2026 research run

Attio API + MCP vs Freshsales API

Attio API + MCP has a score of 63.4 (B) against Freshsales API's 40.8 (E). Both do crm records. The largest gap is maintenance & community, 58 points.

Attio API + MCPAttio · HTTP API B63.4/100#204 of 452 Freshsales APIFreshworks · HTTP API E40.8/100#421 of 452

Which one, for what

Pick Attio API + MCP for

  • reliability (+26)
  • schema & documentation (+55)
  • agent ergonomics (+14)
  • security & auth (+8)
  • maintenance & community (+58)

Pick Freshsales API for

No category where it leads by five points or more.

Score by category

CategoryWeight this runAttio API + MCPFreshsales APIEdge
Reliability16%207751Attio API + MCP +26
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28227Attio API + MCP +55
Agent ergonomics13%16.26248Attio API + MCP +14
Security & auth14%17.55244Attio API + MCP +8
Payments & pricing10%12.53030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.8635Attio API + MCP +58
Transparency & trust7%8.87174Freshsales API +3
Negative events≤1500
Total63.4 · B40.8 · E

Facts side by side

FactAttio API + MCPFreshsales API
KindHTTP APIHTTP API
VendorAttioFreshworks
Hosted endpointhttps://api.attio.com/v2no (local only)
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyAPI key
PricingFreemiumPaid
x402nono
Licencenonenone
Tools exposed42none
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtyesno
MCP registrynot listednot listed
Last release2026-10-01none
Popularity9.9k npm/wknone
Agent reviews3/5 (2)2/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.

Freshsales API

Contact upsert and bulk upsert of up to 100 records make creates safe to retry. No MCP server for Freshsales.

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

Freshsales API

  1. Build the base URL from the bundle alias shown under the API key, https://<alias>.myfreshworks.com/crm/sales/api/
  2. Use /api/contacts/upsert rather than create, so a retry updates instead of duplicating
  3. Budget calls, since 1,000 an hour covers the whole account and 429s carry no Retry-After
  4. Add include=owner,sales_accounts to pull related records in one call
  5. Expect to see only what the key owner's role can see

Other comparisons with Attio API + MCP or Freshsales API

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.

Get an auditSee a sample report