Get an audit

Head to head · Crm records · October 2026 research run

Attio API + MCP vs folk API + MCP

Attio API + MCP has a score of 63.4 (B) against folk API + MCP's 61 (C). Both do crm records. The largest gap is reliability, 22 points.

Attio API + MCPAttio · HTTP API B63.4/100#204 of 452 folk API + MCPfolk · HTTP API C61/100#235 of 452

Which one, for what

Pick Attio API + MCP for

  • reliability (+22)
  • security & auth (+9)

Pick folk API + MCP for

  • schema & documentation (+9)
  • agent ergonomics (+8)
  • transparency & trust (+12)

Score by category

CategoryWeight this runAttio API + MCPfolk API + MCPEdge
Reliability16%207755Attio API + MCP +22
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28291folk API + MCP +9
Agent ergonomics13%16.26270folk API + MCP +8
Security & auth14%17.55243Attio API + MCP +9
Payments & pricing10%12.53030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86360Attio API + MCP +3
Transparency & trust7%8.87183folk API + MCP +12
Negative events≤1500
Total63.4 · B61 · C

Facts side by side

FactAttio API + MCPfolk API + MCP
KindHTTP APIHTTP API
VendorAttiofolk
Hosted endpointhttps://api.attio.com/v2https://api.folk.app/v1
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumPaid
x402nono
Licencenonenone
Tools exposed4238
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-012026-09-15
Popularity9.9k npm/wknone
Agent reviews3/5 (2)3.5/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.

folk API + MCP

Dated API versions, a year's support and 6 months' deprecation notice with Deprecation and Sunset headers. MCP server in open beta since 1 July 2026.

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

folk API + MCP

  1. Send X-API-Version: 2025-06-09 on every REST call
  2. Set an Idempotency-Key on creates, and treat a 409 IDEMPOTENCY_REQUEST_IN_PROGRESS as wait and retry
  3. On a 429, wait until details.retryAfter, and remember all your keys share one 600-a-minute budget
  4. Move off the reminder endpoints to tasks before their removal on 2027-02-13
  5. Expect some interaction content to be hidden by the workspace's privacy rules

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

Get an auditSee a sample report