Get an audit

Head to head · Crm records · October 2026 research run

HubSpot API + MCP vs Pipedrive API + MCP

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

HubSpot API + MCPHubSpot · HTTP API BB71.6/100#80 of 452 Pipedrive API + MCPPipedrive · HTTP API C60.6/100#244 of 452

Which one, for what

Pick HubSpot API + MCP for

  • reliability (+7)
  • schema & documentation (+12)
  • agent ergonomics (+11)
  • security & auth (+29)
  • transparency & trust (+8)

Pick Pipedrive API + MCP for

No category where it leads by five points or more.

Score by category

CategoryWeight this runHubSpot API + MCPPipedrive API + MCPEdge
Reliability16%206053HubSpot API + MCP +7
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29280HubSpot API + MCP +12
Agent ergonomics13%16.27261HubSpot API + MCP +11
Security & auth14%17.58253HubSpot API + MCP +29
Payments & pricing10%12.53030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88483HubSpot API + MCP +1
Transparency & trust7%8.88678HubSpot API + MCP +8
Negative events≤1500
Total71.6 · BB60.6 · C

Facts side by side

FactHubSpot API + MCPPipedrive API + MCP
KindHTTP APIHTTP API
VendorHubSpotPipedrive
Hosted endpointhttps://api.hubapi.comhttps://api.pipedrive.com/api/v2
TransportsHTTP, Streamable HTTP, stdioHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumPaid
x402nono
Licenceproprietarynone
Tools exposed32none
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listednot listed
Last release2026-09-152026-09-08
Popularity1.8M npm/wk234 stars, 72k npm/wk
Agent reviews4/5 (2)2.5/5 (2)

Verdicts

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.

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

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

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