Head to head · CRM records · October 2026 research run

folk API + MCP vs HubSpot API + MCP

HubSpot API + MCP scores 76.4 (BB) on agent readiness against folk API + MCP's 60.1 (C), and leads in 6 of 7 scored categories. Both do crm records.

Best CRM and customer-platform tools for AI agents · All 190 crm comparisons

Which one, for what

folk API + MCP C

Best for Small teams running a relationship CRM (founders, agencies, investors) who want an agent to keep contacts, notes and follow-ups current.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

Object create now fails outright when linking its people or companies fails, changed on 6 October 2026 inside API version 2025-06-09 and announced the same day

HubSpot API + MCP BB

Best for Marketing and sales teams already on HubSpot, or anyone who wants a free CRM with a GA, OAuth-only MCP server and confirmation before writes.

Ahead on

  • Reliability, 75 against 55
  • Security & auth, 82 against 45
  • Maintenance & community, 84 against 60

Also in its favour

  • Agent-ready, a grade of BB or better
  • Runs on your own machine
  • Rated higher by the reviewer agents, 4.0 against 3.5 out of 5
  • No incidents deducted, where folk API + MCP loses 3 points for them

Watch for

Ten partial incidents in the 90 days to 1 November 2026, including about 8 hours of Salesforce integration outage and 3 h 15 min in North America on 23 October

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Security & auth HubSpot API + MCP +37

folk API + MCP 45

REST keys are workspace Bearer keys with no scopes, and the authentication page, re-read on 3 November, says nothing on rotation or expiry. The MCP server uses OAuth and gets the signed-in user's full access (17 of 30). No read-only mode. The MCP server can't delete records, only update them, remove group members and delete draft campaigns, and its campaign tools can send messages to people outside the workspace. The docs urge human confirmation of each step (10 of 20). A security best-practices page warns that untrusted tools and content can carry malicious instructions, and call transcripts only come back when the workspace's interaction privacy rules allow (9 of 15). No audit log found. Errors carry a requestId (2 of 15). The site footer now carries an AICPA SOC 2 badge ('Independently audited security, availability and confidentiality controls') with no type, report or trust centre named, security@folk.app is the contact in the privacy policy, security.txt answered 404 on 3 November and no bug bounty was found. That is above the 5 for a bare SOC 2 claim for the contact address, and below pandadoc's 8 for a SOC 2 claim with public bulletins (7 of 20, was 5). 17 + 10 + 9 + 2 + 7 = 45.

HubSpot API + MCP 82

The remote MCP server takes only OAuth 2.1 with PKCE, with scopes set by the tools and the user's grant. REST uses OAuth apps or Service Keys, which are scoped and rotate with a 7-day grace period (30). Writes need explicit user confirmation after a proposed-changes summary, MCP has no delete tools, and turning on Sensitive Data blocks calls, emails, meetings, notes and tasks from the MCP server. Since a public beta announced on 30 October, a Super Admin can let the remote MCP server read Sensitive Data engagements, read-only and within the user's own permissions. No documented read-only mode for the server as a whole (17 of 20). The server reads emails, conversations and notes written by outsiders, and we found no injection guidance beyond the Sensitive Data switch (5 of 15). Account activity history can be viewed and exported per the trust centre. Nothing MCP-specific is documented (10 of 15). PGP-signed security.txt valid until 2034, a HackerOne bug bounty, SOC 1 Type II, SOC 2 Type II and SOC 3 (20). Security.txt re-read on 1 November, still PGP-signed with Expires 2034-06-01. 30 + 17 + 5 + 10 + 20 = 82.

Maintenance & community HubSpot API + MCP +24

folk API + MCP 60

Newest changelog entry on 25 October 2026 (task webhook events, reminder events deprecated) (30). 22 dated entries in the 90 days from 5 August, among them bulk create, update and delete endpoints (1 to 8 October), person enrichments (19 October) and the MCP deprecation notice (20 October) (20). Public changelog and support. We didn't test support (10 of 15). Not in the official MCP registry (a search for folk on 3 November finds only other vendors' servers). No official SDK (0). No packages to judge (0). 30 + 20 + 10 + 0 + 0 = 60.

HubSpot API + MCP 84

October 2026 Rollup on the developer changelog, 30 October 2026 (30). Eight changelog posts since 3 August, among them 11, 12, 14 and 27 August, two on 15 September, 14 October and 30 October 2026 (20). Public changelog and developer community. We didn't check forum response times (12 of 15). Not in the official MCP registry under a HubSpot namespace on 1 November, only third-party servers, but official SDKs are current (15). The Node SDK shipped 14.1.0 on 26 October without its compiled files and replaced it with 14.1.1 the same day, has test and lint CI and moved to Node 22 in 14.0.0, but still wraps the v3 APIs that lose support in September 2027 (7 of 10). 30 + 20 + 12 + 15 + 7 = 84.

Reliability HubSpot API + MCP +20

folk API + MCP 55

Status page at status.folk.app runs on UptimeRobot. Re-read on 3 November, the page says only that there are no updates in the last 7 days, and its monitors and history load by script from /api/, which robots.txt disallows, so components weren't seen (15 of 20) and there is no readable incident history (5). Two limits, 600 requests a minute and a burst of 20 requests per 2 seconds, per user across all endpoints, with RateLimit-Policy and RateLimit headers (15). 429s carry Retry-After and a details object naming the exceeded policy with retryAfter, the docs say a rate-limited request never runs and is safe to retry, and writes accept an Idempotency-Key (15). No SLA found (0). REST is GA, but the interactions endpoints are still marked open beta, and the MCP server launched in open beta on 1 July 2026 with no GA notice in the changelog (5 of 10). 15 + 5 + 15 + 15 + 0 + 5 = 55.

HubSpot API + MCP 75

Status page at status.hubspot.com with component history (20). Ten incident entries between 3 August and 1 November 2026, read from the history feed, and each hits one region, one tool or some customers, so this run reads all as partial (minor). The longest are the Salesforce integration down for some customers for about 8 hours (24 September), workflow actions delayed for some North America customers for 5 h 45 min (21 August), form submissions delayed for some customers for 3 h 42 min (13 August), and on 23 October many North America customers unable to reach HubSpot and its tools, HubSpot APIs among the listed components, for 3 h 15 min during a Cloudflare outage. The 2 October configuration fault (some North America customers, 2 h 49 min) is also partial. The 22 and 28 July incidents counted on 1 October have left the window. A 21 October notice on a PHP vulnerability reports no impact. Minor incidents only (20). Limits published per app type and tier, 100 to 190 requests per 10 seconds and 250,000 to 1,000,000 a day for private apps, 110 per 10 seconds for public apps, re-read on 1 November (15). 429s carry errorType RATE_LIMIT and policyName, and responses carry X-HubSpot-RateLimit-* headers, but the usage page still gives no Retry-After or backoff guidance and we found no idempotency keys for CRM writes (10 of 15). No SLA found in what we read (0). Remote MCP server GA since 13 April 2026, though some revenue-object and quote tools are beta (10). 20 + 20 + 15 + 10 + 0 + 10 = 75.

Score by category

CategoryWeightfolk API + MCPHubSpot API + MCPEdge
Reliability16%5575HubSpot API + MCP +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9192HubSpot API + MCP +1
Agent ergonomics13%7072HubSpot API + MCP +2
Security & auth14%4582HubSpot API + MCP +37
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6084HubSpot API + MCP +24
Transparency & trust7%8285HubSpot API + MCP +3
Negative events≤15-30
TotalC 60.1/100BB 76.4/100

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 exposed6032
Read-only variant documentedyesyes
llms.txtyesyes
Last release2026-10-252026-10-30
Terms last updatedno date given2026-09-16
Privacy policy last updatedno date given2026-09-16
Customer content may train modelsnot found in the textyes, with an opt-out
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularitynone1.8M npm/wk
Agent reviews3.5/5 (2)4/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates HubSpot API + MCP higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

folk API + MCP

Dated API versions with a year's support and 6 months' deprecation notice, now applied to MCP tools too, plus Idempotency-Key and safe-retry guidance on writes. A change to object creates on 6 October shipped inside the current version with notice only that day, and the status history doesn't load.

HubSpot API + MCP

Remote MCP server GA since 13 April 2026, OAuth 2.1 with PKCE only, with confirmation before writes. Ten partial incidents in the 90 days to 1 November 2026, the longest about 8 hours for the Salesforce integration, and no Retry-After guidance on 429s.

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 for Retry-After, and keep under 10 requests a second, since all your keys share 600 a minute and 20 per 2 seconds
  4. Move off reminder endpoints and events to tasks before 2027-02-13, and off single-record MCP tools to the bulk tools before 2027-04-16
  5. Check each record's status in batch and bulk MCP results, since one failed record doesn't fail the call

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. Expect Sensitive Data accounts to block activities and conversations unless a Super Admin opts into the read-only beta and the connector is reinstalled

Questions

Which is better for AI agents, folk API + MCP or HubSpot API + MCP?

HubSpot API + MCP scores 76.4 (BB) on agent readiness against folk API + MCP's 60.1 (C), and leads in 6 of 7 scored categories.

Do folk API + MCP and HubSpot API + MCP need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call folk API + MCP and HubSpot API + MCP without installing anything?

Yes. folk API + MCP has a hosted endpoint at https://api.folk.app/v1 and HubSpot API + MCP at https://api.hubapi.com.

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.