Get an audit

Head to head · Crm records · October 2026 research run

folk API + MCP vs Twenty API + MCP

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

folk API + MCPfolk · HTTP API C61/100#235 of 452 Twenty API + MCPTwenty · HTTP API B65.9/100#166 of 452

Which one, for what

Pick folk API + MCP for

  • reliability (+9)

Pick Twenty API + MCP for

  • agent ergonomics (+10)
  • security & auth (+15)
  • maintenance & community (+37)

Score by category

CategoryWeight this runfolk API + MCPTwenty API + MCPEdge
Reliability16%205546folk API + MCP +9
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29188folk API + MCP +3
Agent ergonomics13%16.27080Twenty API + MCP +10
Security & auth14%17.54358Twenty API + MCP +15
Payments & pricing10%12.53030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86097Twenty API + MCP +37
Transparency & trust7%8.88380folk API + MCP +3
Negative events≤1500
Total61 · C65.9 · B

Facts side by side

Factfolk API + MCPTwenty API + MCP
KindHTTP APIHTTP API
VendorfolkTwenty
Hosted endpointhttps://api.folk.app/v1https://api.twenty.com/rest
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPaidFreemium
x402nono
LicencenoneAGPL-3.0
Tools exposed38none
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 release2026-09-152026-09-30
Popularitynone58k stars, 26k npm/wk
Agent reviews3.5/5 (2)3.5/5 (2)

Verdicts

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.

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

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

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 folk 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.

Get an auditSee a sample report