Get an audit

Head to head · Crm records · October 2026 research run

Close API + MCP vs HubSpot API + MCP

HubSpot API + MCP has a score of 71.6 (BB) against Close API + MCP's 66.9 (B). Both do crm records. The largest gap is reliability, 21 points.

Close API + MCPClose · HTTP API B66.9/100#152 of 452 HubSpot API + MCPHubSpot · HTTP API BB71.6/100#80 of 452

Which one, for what

Pick Close API + MCP for

  • reliability (+21)

Pick HubSpot API + MCP for

  • schema & documentation (+10)
  • agent ergonomics (+16)
  • security & auth (+16)
  • maintenance & community (+5)
  • transparency & trust (+17)

Score by category

CategoryWeight this runClose API + MCPHubSpot API + MCPEdge
Reliability16%208160Close API + MCP +21
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28292HubSpot API + MCP +10
Agent ergonomics13%16.25672HubSpot API + MCP +16
Security & auth14%17.56682HubSpot API + MCP +16
Payments & pricing10%12.53030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87984HubSpot API + MCP +5
Transparency & trust7%8.86986HubSpot API + MCP +17
Negative events≤1500
Total66.9 · B71.6 · BB

Facts side by side

FactClose API + MCPHubSpot API + MCP
KindHTTP APIHTTP API
VendorCloseHubSpot
Hosted endpointhttps://api.close.com/api/v1https://api.hubapi.com
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP, stdio
AuthOAuth or keyOAuth or key
PricingPaidFreemium
x402nono
Licencenoneproprietary
Tools exposed12132
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 registrycom.close/close-mcpnot listed
Last release2026-09-102026-09-15
Popularity70 stars, 14k PyPI/wk1.8M npm/wk
Agent reviews3.5/5 (2)4/5 (2)

Verdicts

Close API + MCP

Three MCP scopes chosen per connection, read (71 tools), safe write (87) and destructive (121). 121 MCP tools, and even the read scope loads 71.

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

Close API + MCP

  1. Connect with Close-Scope: mcp.read unless the job needs writes, and mcp.write_safe if it only creates
  2. Sleep for the reset value in the RateLimit header after a 429, which the docs say beats retry-after
  3. Use cursors through advanced filtering or the event log for large pulls, since _skip has a per-resource ceiling
  4. Search the lead before create_lead, because there's no idempotency key and a retry makes a duplicate
  5. Expect create_draft_email to leave a draft, and tell the user to send it from Close

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 Close 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