Get an audit

Head to head · Crm records · October 2026 research run

folk API + MCP vs Pipedrive API + MCP

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

folk API + MCPfolk · HTTP API C61/100#235 of 452 Pipedrive API + MCPPipedrive · HTTP API C60.6/100#244 of 452

Which one, for what

Pick folk API + MCP for

  • schema & documentation (+11)
  • agent ergonomics (+9)
  • transparency & trust (+5)

Pick Pipedrive API + MCP for

  • security & auth (+10)
  • maintenance & community (+23)

Score by category

CategoryWeight this runfolk API + MCPPipedrive API + MCPEdge
Reliability16%205553folk API + MCP +2
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29180folk API + MCP +11
Agent ergonomics13%16.27061folk API + MCP +9
Security & auth14%17.54353Pipedrive API + MCP +10
Payments & pricing10%12.53030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86083Pipedrive API + MCP +23
Transparency & trust7%8.88378folk API + MCP +5
Negative events≤1500
Total61 · C60.6 · C

Facts side by side

Factfolk API + MCPPipedrive API + MCP
KindHTTP APIHTTP API
VendorfolkPipedrive
Hosted endpointhttps://api.folk.app/v1https://api.pipedrive.com/api/v2
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPaidPaid
x402nono
Licencenonenone
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-08
Popularitynone234 stars, 72k npm/wk
Agent reviews3.5/5 (2)2.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.

Pipedrive API + MCP

Hosted MCP server on every plan, with actions recorded in the change log. MCP tool list not published, and the server is labelled beta.

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

Pipedrive API + MCP

  1. Use v2 endpoints, which cost fewer tokens than v1
  2. Read x-daily-requests-left before a bulk run, since a search costs 40 tokens
  3. Send the token in the x-api-token header, never as api_token in the URL
  4. Keep under 10 search requests per 2 seconds on every plan
  5. Ask the user to load all Pipedrive tools in the client if an expected tool is missing

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