Get an audit

Head to head · Crm records · October 2026 research run

folk API + MCP vs HubSpot API + MCP

HubSpot API + MCP has a score of 71.6 (BB) against folk API + MCP's 61 (C). Both do crm records. The largest gap is security & auth, 39 points.

folk API + MCPfolk · HTTP API C61/100#235 of 452 HubSpot API + MCPHubSpot · HTTP API BB71.6/100#80 of 452

Which one, for what

Pick folk API + MCP for

No category where it leads by five points or more.

Pick HubSpot API + MCP for

  • reliability (+5)
  • security & auth (+39)
  • maintenance & community (+24)

Score by category

CategoryWeight this runfolk API + MCPHubSpot API + MCPEdge
Reliability16%205560HubSpot API + MCP +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29192HubSpot API + MCP +1
Agent ergonomics13%16.27072HubSpot API + MCP +2
Security & auth14%17.54382HubSpot API + MCP +39
Payments & pricing10%12.53030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86084HubSpot API + MCP +24
Transparency & trust7%8.88386HubSpot API + MCP +3
Negative events≤1500
Total61 · C71.6 · BB

Facts side by side

Factfolk API + MCPHubSpot API + MCP
KindHTTP APIHTTP API
VendorfolkHubSpot
Hosted endpointhttps://api.folk.app/v1https://api.hubapi.com
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP, stdio
AuthOAuth or keyOAuth or key
PricingPaidFreemium
x402nono
Licencenoneproprietary
Tools exposed3832
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-15
Popularitynone1.8M npm/wk
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.

HubSpot API + MCP

Remote MCP server GA since 13 April 2026, OAuth 2.1 with PKCE only. Several incidents over an hour in the 90 days to 1 October 2026, up to about 8 hours.

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

HubSpot API + MCP

  1. Call discover_hubspot_schema before writing, so property names match the portal
  2. Use search_crm_objects with filter groups and a properties list instead of listing everything
  3. Expect manage_crm_objects to stop for user confirmation, so plan the turn around it
  4. Read policyName on a 429 to tell a 10-second burst from the daily cap
  5. Ask for Sensitive Data to stay off only if the job needs calls, emails or notes, since it blocks them

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