Get an audit

Head to head · Crm records · October 2026 research run

folk API + MCP vs Salesforce API + MCP

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

folk API + MCPfolk · HTTP API C61/100#235 of 452 Salesforce API + MCPSalesforce · HTTP API C60.7/100#242 of 452

Which one, for what

Pick folk API + MCP for

  • schema & documentation (+15)
  • maintenance & community (+42)
  • transparency & trust (+9)

Pick Salesforce API + MCP for

  • agent ergonomics (+6)
  • security & auth (+29)

Score by category

CategoryWeight this runfolk API + MCPSalesforce API + MCPEdge
Reliability16%205558Salesforce API + MCP +3
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29176folk API + MCP +15
Agent ergonomics13%16.27076Salesforce API + MCP +6
Security & auth14%17.54372Salesforce API + MCP +29
Payments & pricing10%12.53030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86018folk API + MCP +42
Transparency & trust7%8.88374folk API + MCP +9
Negative events≤1500
Total61 · C60.7 · C

Facts side by side

Factfolk API + MCPSalesforce API + MCP
KindHTTP APIHTTP API
VendorfolkSalesforce
Hosted endpointhttps://api.folk.app/v1https://api.salesforce.com/platform/mcp/v1/platform/sobject-all
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth
PricingPaidPaid
x402nono
Licencenonenone
Tools exposed3811
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentedyesyes
llms.txtyesyes
MCP registrynot listednot listed
Last release2026-09-15none
Popularitynonenone
Agent reviews3.5/5 (2)4/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.

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

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

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

Get an auditSee a sample report