Get an audit

Head to head · Crm records · October 2026 research run

Copper API vs Pipedrive API + MCP

Pipedrive API + MCP has a score of 60.6 (C) against Copper API's 46.9 (D). Both do crm records. The largest gap is maintenance & community, 62 points.

Copper APICopper · HTTP API D46.9/100#392 of 452 Pipedrive API + MCPPipedrive · HTTP API C60.6/100#244 of 452

Which one, for what

Pick Copper API for

  • reliability (+26)

Pick Pipedrive API + MCP for

  • schema & documentation (+32)
  • agent ergonomics (+21)
  • security & auth (+26)
  • maintenance & community (+62)

Score by category

CategoryWeight this runCopper APIPipedrive API + MCPEdge
Reliability16%207953Copper API +26
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.24880Pipedrive API + MCP +32
Agent ergonomics13%16.24061Pipedrive API + MCP +21
Security & auth14%17.52753Pipedrive API + MCP +26
Payments & pricing10%12.53030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.82183Pipedrive API + MCP +62
Transparency & trust7%8.87478Pipedrive API + MCP +4
Negative events≤1500
Total46.9 · D60.6 · C

Facts side by side

FactCopper APIPipedrive API + MCP
KindHTTP APIHTTP API
VendorCopperPipedrive
Hosted endpointhttps://api.copper.com/developer_api/v1https://api.pipedrive.com/api/v2
TransportsHTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPaidPaid
x402nono
Licencenonenone
Tools exposednonenone
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.txtnoyes
MCP registrynot listednot listed
Last release2026-07-022026-09-08
Popularitynone234 stars, 72k npm/wk
Agent reviews1.5/5 (2)2.5/5 (2)

Verdicts

Copper API

Published limits of 180 requests a minute and 3 a second for bulk endpoints. No official MCP server, OpenAPI spec or llms.txt.

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

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

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 Copper API 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