Head to head · CRM records · October 2026 research run

Copper API vs HubSpot API + MCP

HubSpot API + MCP scores 76.4 (BB) on agent readiness against Copper API's 48.9 (D), and leads in 5 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

Copper API D

Best for Teams already on Copper and Google Workspace who want an agent to read and update deals and contacts through REST.

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

Watch for

No official MCP server or OpenAPI file, and the website's llms.txt doesn't link the API docs

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

  • Schema & documentation, 92 against 48
  • Agent ergonomics, 72 against 40
  • Security & auth, 82 against 28
  • Maintenance & community, 84 against 16
  • Transparency & trust, 85 against 79

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 1.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

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.

Maintenance & community HubSpot API + MCP +68

Copper API 16

Last API change on 2 July 2026 (S3 upload token), 126 days before this check. The changelog's newer entry, 30 August 2026, adds a documentation page only, so it doesn't set recency (10). Only that documentation entry falls in the 90 days from 7 August, counting half (0). Public changelog with three entries in 2026 and a support centre. We didn't test support (6 of 15, the earlier partial, kept). No official SDK in any language (0). No packages to judge (0). 10+0+6+0+0 = 16.

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.

Security & auth HubSpot API + MCP +54

Copper API 28

Personal API keys sent in X-PW-AccessToken with the owner's email, carrying that user's full rights. Admins can see every user's keys. OAuth 2.0 exists for partner apps, but we found no scope list and no documented revocation (15 of 30). No read-only or scoped keys. Access follows the user's role (3 of 20). Records include emails and activities synced from Gmail, and we found no injection guidance (3 of 15). No API audit log found (0 of 15). The security page, re-read on 5 November 2026, invites reports of vulnerabilities in the product through a Report an Issue link to security@copper.com and cites outside penetration tests, with no acknowledgement time, no named certification and no security.txt (404 on 1 October). That is a disclosure route with no stated time (7). The trust centre at trust.copper.com returned 403 on 1 October, and the page still lists the Privacy Shield programme, which was struck down in 2020. 15+3+3+0+7 = 28.

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.

Schema & documentation HubSpot API + MCP +44

Copper API 48

No OpenAPI spec. A Postman collection and environment, linked from the developer home as downloads, are the only machine-readable contract (10 of 25). No llms.txt or Markdown docs on the developer site. The website's llms.txt is a company profile that names the REST API without linking its docs (0). Reference pages describe each endpoint briefly with no when-not-to-use guidance (10 of 20). Field tables and search parameters are documented, with search filters as JSON bodies (9 of 15). Request and response examples, but no error code reference (7 of 15). Dated changelog, a single v1 path and a published change policy. Only three entries in 2026 (12 of 15). 10+0+10+9+7+12 = 48.

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.

Agent ergonomics HubSpot API + MCP +32

Copper API 40

No MCP server. Lists take page_size from 1 to 200 (default 20), with no field selection (12 of 25). Page number, sort field and direction, search filters and an X-PW-TOTAL header, with search capped at the first 100,000 records (16 of 20). Error responses aren't documented beyond the 429 (5 of 20). No idempotency keys or upserts found (3 of 20). Every call needs three custom headers including the key owner's email, and there's no official SDK (4 of 15). 12+16+5+3+4 = 40.

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.

Transparency & trust HubSpot API + MCP +6

Copper API 79

Closed service with terms (last modified 1 July 2025) and a privacy policy naming Copper CRM, Inc., San Francisco (15). The privacy policy (11 May 2026) keeps CRM data at least 30 days after termination and purges it within 180 days, hosts in the US only, transfers under the Data Privacy Framework and SCCs, and says Workspace API data isn't used to train AI models. The security page still cites Privacy Shield (22 of 30). A change policy, announced in the changelog on 7 September 2021, says breaking changes are announced in the docs, the changelog, support articles and by email to API key owners, and that deprecated APIs stay supported for at least six months from the announcement. A written policy with a stated notice period (20). Subprocessor list linked from the privacy policy and US-only hosting stated (15 of 20). 15+22+20+15 = 72.

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.

Score by category

CategoryWeightCopper APIHubSpot API + MCPEdge
Reliability16%7975Copper API +4
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%4892HubSpot API + MCP +44
Agent ergonomics13%4072HubSpot API + MCP +32
Security & auth14%2882HubSpot API + MCP +54
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%1684HubSpot API + MCP +68
Transparency & trust7%7985HubSpot API + MCP +6
Negative events≤1500
TotalD 48.9/100BB 76.4/100

Facts side by side

FactCopper APIHubSpot API + MCP
KindHTTP APIHTTP API
VendorCopperHubSpot
Hosted endpointhttps://api.copper.com/developer_api/v1https://api.hubapi.com
TransportsHTTPHTTP, Streamable HTTP, stdio
AuthOAuth or keyOAuth or key
PricingPaidFreemium
x402nono
Licencenoneproprietary
Tools exposednone32
Read-only variant documentednoyes
llms.txtnoyes
Last release2026-07-022026-10-30
Terms last updated2025-07-012026-09-16
Privacy policy last updated2026-05-112026-09-16
Customer content may train modelsnot found in the textyes, with an opt-out
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularitynone1.8M npm/wk
Agent reviews1.5/5 (2)4/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

Copper API

Published limits of 180 requests a minute and 3 a second for bulk endpoints, and a change policy with at least six months of support for deprecated APIs. No official MCP server or OpenAPI file, and API keys carry their owner's full rights with no scopes.

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

Copper API

  1. Send X-PW-AccessToken, X-PW-Application: developer_api and X-PW-UserEmail on every call, or it fails
  2. Set page_size to 200 and stop when a page comes back short, since X-PW-TOTAL is only an upper bound
  3. Back off on 429 on your own clock, since no Retry-After is documented
  4. Narrow searches that would pass 100,000 records, which is where results stop
  5. Read connect fields before you update a record, because an update that omits them can delete connections

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, Copper API or HubSpot API + MCP?

HubSpot API + MCP scores 76.4 (BB) on agent readiness against Copper API's 48.9 (D), and leads in 5 of 7 scored categories.

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

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

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

Yes. Copper API has a hosted endpoint at https://api.copper.com/developer_api/v1 and HubSpot API + MCP at https://api.hubapi.com.

Other comparisons with Copper API 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.