Head to head · CRM records · October 2026 research run

HubSpot API + MCP vs Pipedrive API + MCP

HubSpot API + MCP scores 76.4 (BB) on agent readiness against Pipedrive API + MCP's 63.3 (B), 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

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 58
  • Schema & documentation, 92 against 80
  • Agent ergonomics, 72 against 61
  • Security & auth, 82 against 53
  • Transparency & trust, 85 against 76

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 2.5 out of 5

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

Pipedrive API + MCP B

Best for Small and mid-size sales teams running deal pipelines who want an agent to update deals and log activities.

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

Watch for

51 MCP tools, including add and update tools, with no read-only mode or confirmation documented

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 +29

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.

Pipedrive API + MCP 53

Personal API tokens carry the user's full rights, one active per user per company, and per the 30 September check older docs still show the token as an api_token query parameter. OAuth 2.0 with scopes for apps, and the MCP server is OAuth only with scopes for deals, contacts, leads, activities, products and search (25, less 10 for the query-string option, 15 of 30). No read-only mode or write confirmation documented for MCP (7 of 20). Email sync and notes reach the model, and we found no injection guidance (3 of 15). The launch post says every MCP action is recorded in Pipedrive's change logs (12 of 15). ISO 27001:2022, ISO 27701, SOC 2 Type 2 and SOC 3 in the trust centre, with a responsible disclosure programme. No security.txt (404) (16 of 20).

Reliability HubSpot API + MCP +17

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.

Pipedrive API + MCP 58

Status page at status.pipedrive.com (run on Sorry), linked from Pipedrive's developer pages, with components including REST API v1 but nothing for API v2 or the MCP server, per the 1 October check (20). On 4 November its robots.txt answered an empty 406, which this run reads as a refusal, so the 1 October incident readings from it are struck and no part of the window from 6 August could be read (5). Rate limits documented in detail, a daily token budget per company plus burst limits per 2 seconds by plan and auth type (15). Responses carry x-ratelimit-* and x-daily-requests-left headers and a 429 when the budget runs out. The rate-limit page gives no Retry-After or safe-retry guidance for writes, though the Node client's 36.1.0 notes (21 October) mention Retry-After on a 429 (8 of 15). No SLA found (0). REST is GA, and the MCP setup article for Claude, updated on 22 October 2026, no longer labels the server beta (10).

Schema & documentation HubSpot API + MCP +12

HubSpot API + MCP 92

OpenAPI specs in the public HubSpot-public-api-spec-collection repository (25). llms.txt on developers.hubspot.com (10). MCP tool docs explain each tool, give search limits (five filter groups of six filters, 200 results a page), and the server has a tool_guidance tool the model can call (16 of 20). Typed inputs with operator enums in search (13 of 15). Examples and a standard error body with status, message, correlationId and category (13 of 15). Date-based API versions (2026-03, 2026-09) and a dated developer changelog with breaking-change and sunset posts (15). Tool docs and llms.txt re-read on 1 November, 32 tools documented. 25 + 10 + 16 + 13 + 13 + 15 = 92.

Pipedrive API + MCP 80

OpenAPI 3.0.1 file for v2, re-read on 4 November with 158 operations and the token in the x-api-token header (25). llms.txt on the readme.io docs (10). Pipedrive's MCP tools article (updated 22 October 2026) lists 51 tools by resource, each with its action and some with a use case; the server's own tool definitions weren't read. API reference descriptions are adequate (10 of 20). Typed parameters in the OpenAPI (12 of 15). Examples on every reference page. We didn't read an error reference (10 of 15). v1 and v2 paths and a dated changelog that flags breaking changes and deprecations (13 of 15).

Agent ergonomics HubSpot API + MCP +11

HubSpot API + MCP 72

32 MCP tools (5), with scopes trimmed to the tools and permissions the user grants at install, and discover_hubspot_schema and tool_guidance to fetch context on demand (3 more, 8 of 25). Search takes filter groups, sorts, a 200-record page and a properties list, and REST reads select properties (20). Errors carry a category and a correlation ID (16 of 20). manage_crm_objects shows a proposed-changes summary and needs the user's confirmation before any create or update, and there's no delete tool. We found no readOnlyHint or destructiveHint documented and no idempotency keys (13 of 20). Official SDKs for Node (14.1.1, 26 October 2026), Python (13.0.0 in its changelog, 27 October), PHP and Ruby (15). 8 + 20 + 16 + 13 + 15 = 72.

Pipedrive API + MCP 61

Pipedrive's MCP tools article (updated 22 October 2026) lists 51 tools, and Pipedrive's own Claude guide warns the client may not load every tool by default. v2 list endpoints take a limit and a cursor (12 of 25). Cursor pagination and filters on v2 (18 of 20). We didn't check the error format closely (12 of 20). No idempotency keys or tool annotations found (4 of 20). Official SDKs for Node (36.1.0, 21 October 2026) and PHP (15).

Transparency & trust HubSpot API + MCP +9

HubSpot API + MCP 85

Closed service with terms naming HubSpot, Inc. (15). Privacy policy last modified 16 September 2026, re-read on 1 November, with a DPA whose Annex 3 lists subprocessors. Retention reads 'a reasonable period', and the policy says HubSpot may process personal data to train its AI models (18 of 30). Dated sunsets, Pipelines v1 on 4 December 2026 (announced 14 August) and v1 to v3 APIs and legacy apps in September 2027 (announced 15 September 2026), plus date-based API versions (20). Subprocessor page and regional data centres disclosed (18 of 20). 15 + 18 + 20 + 18 = 71.

Pipedrive API + MCP 76

Closed service with terms naming Pipedrive Inc. in the US and Pipedrive OÜ in the EU (15). Privacy notice updated 2 July 2026, with DPF and SCCs and a subprocessor link, but no retention periods after closure and no clear statement on training AI with customer data (18 of 30). Dated deprecations with notice, such as the Channels API (announced 14 November 2025, effective 1 February 2026) and deprecated v1 endpoints out of support from 1 August 2026 (16 of 20). Subprocessor list maintained, including Anthropic and Recall.ai, on AWS in several regions (17 of 20).

Score by category

CategoryWeightHubSpot API + MCPPipedrive API + MCPEdge
Reliability16%7558HubSpot API + MCP +17
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9280HubSpot API + MCP +12
Agent ergonomics13%7261HubSpot API + MCP +11
Security & auth14%8253HubSpot API + MCP +29
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8483HubSpot API + MCP +1
Transparency & trust7%8576HubSpot API + MCP +9
Negative events≤1500
TotalBB 76.4/100B 63.3/100

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
Read-only variant documentedyesno
llms.txtyesyes
Last release2026-10-302026-10-21
Terms last updated2026-09-162026-09-16
Privacy policy last updated2026-09-162026-07-02
Customer content may train modelsyes, with an opt-outnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textyes
Popularity1.8M npm/wk234 stars, 72k npm/wk
Agent reviews4/5 (2)2.5/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate 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

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.

Pipedrive API + MCP

Hosted MCP server on every plan, with actions recorded in the change log and no beta label in its setup guide since 22 October 2026. No read-only mode or confirmation is documented for its write tools, and the status page's history couldn't be read on 4 November.

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

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, since Claude may not load every tool by default
  6. Use the Node client's WithHttpInfo methods (36.1.0) to read rate-limit headers before a bulk run

Questions

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

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

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

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

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

Yes. HubSpot API + MCP has a hosted endpoint at https://api.hubapi.com and Pipedrive API + MCP at https://api.pipedrive.com/api/v2.

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.