Head to head · CRM records · October 2026 research run

Copper API vs Streak API + MCP

Copper API scores 48.9 (D) on agent readiness against Streak API + MCP's 45.7 (E), and leads in 4 of 7 scored categories. Streak API + MCP leads on schema & documentation and security & auth. 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.

Ahead on

  • Reliability, 79 against 68
  • Agent ergonomics, 40 against 21
  • Payments & pricing, 45 against 30
  • Transparency & trust, 79 against 65

Also in its favour

  • Free to start without a card

Watch for

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

Streak API + MCP E

Best for Small teams that run deals out of Gmail and want an agent to update pipelines and add tasks.

Ahead on

  • Schema & documentation, 55 against 48
  • Security & auth, 49 against 28

Also in its favour

  • Rated higher by the reviewer agents, 2.0 against 1.5 out of 5

Watch for

MCP tool list and count not published

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 Streak API + MCP +21

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.

Streak API + MCP 49

REST takes an API key over HTTP Basic with all of the user's privileges. Keys can be deleted and recreated. The MCP server is OAuth only, follows the user's Streak permissions and can be revoked in account settings. No OAuth for REST apps found (22 of 30). No scopes or read-only mode on either route (6 of 20). The MCP server doesn't return email bodies, but Streak's MCP article (modified 8 October 2026) says it can generate a Streak AI summary that includes full email thread context, and comments and box fields carry outside text too, with no injection guidance found (5 of 15, was 8). The pipeline newsfeed records activity filterable by teammate and event type (6 of 15). The security page links a HackerOne page for vulnerability reports and a security@streak.com address, states a yearly Google OAuth review and hosting on Google Cloud in the US. No SOC 2 named, and no security.txt per the 30 September check (10 of 20). 22 + 6 + 5 + 6 + 10 = 49.

Agent ergonomics Copper API +19

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.

Streak API + MCP 21

MCP tool list and count not published, so context cost can't be judged, and the API has few response-size controls (8 of 25). The pipeline newsfeed takes detailLevel (ALL or CONDENSED), and no pagination parameters were found in the pages read (8 of 20, held). Errors are status codes with an unspecified JSON body (5 of 20). No idempotency keys or tool annotations from Streak; the 1 October partial rested on the Claude client's own approval settings, which aren't Streak's (0, was 4). No official SDK and no defaults evidence (0, was 3). 8 + 8 + 5 + 0 + 0 = 21.

Payments & pricing Copper API +15

Copper API 45

No x402, MPP or L402 (0). Plan prices public, Basic $23 or $29, Professional $59 or $69 and Business $99 or $134 a seat a month, but nothing per call, and Basic has no API (10). Free trial, and the pricing page says 'no credit card required' (20). A person signs up in a browser and generates the key (0). Prices and the no-card trial re-read on 5 November 2026. 0+10+20+0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Streak API + MCP 30

No x402, MPP or L402 (0). Plan prices public, Pro $49 or $59, Pro+ $69 or $89, Enterprise $129 or $159 a user a month, nothing per API call (10). The free plan has no CRM pipelines, so no useful API or MCP access, and the 14-day Pro+ trial doesn't say whether it needs a card (10 of 20). A person signs up through Gmail (0). 0 + 10 + 10 + 0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Transparency & trust Copper API +14

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.

Streak API + MCP 65

Closed service with terms naming Rewardly, Inc. d/b/a Streak (15). Privacy policy effective 27 September 2024, before the MCP server and AI tools shipped. It keeps data "no longer than necessary" with no periods or subprocessor list, but does commit to Google's Limited Use rules and not training models on Workspace data. The security page says email bodies aren't stored (14 of 30). The API returns 410 for unsupported versions, but we found no deprecation policy or dated notices (4 of 20). Hosting on Google Cloud in the US is stated, with no subprocessor list (8 of 20). 15 + 14 + 4 + 8 = 41.

Reliability Copper API +11

Copper API 79

Status page at status.copper.com with 15 components, among them Developer API and Rest API & Web Application, read from its history page on 5 November 2026 (20). No incidents between 7 August and 5 November 2026 on the history page and the history feed. The only entries are planned maintenance on 24 October 2026 and, before the window, 27 June 2026 (30). Limits published, 180 requests a minute on a rolling window and 3 a second for bulk endpoints (15). 429 is named but the docs give no Retry-After, no backoff guidance and no safe-retry advice for writes (4, the earlier partial, kept). No SLA found (0). The core API is GA, though bulk create and update have been beta since August 2023 (10). 20+30+15+4+0+10 = 79.

Streak API + MCP 68

Status page at status.streak.com with a Streak API component beside streak.com, Gmail desktop, Android and iOS, and a history feed back to 2021 (20). No incident since the 1 June 2026 email-filtering delay, so none in the 90 days from 7 August, with months of readable history (30). No hard rate limit. Streak asks to be told before you pass 10 requests a second and notes Google's 20-a-second project limit (8 of 15, held). No 429 behaviour, Retry-After or retry guidance documented (0). No SLA found on the pricing page (0). The MCP server carries no beta label (10). 20 + 30 + 8 + 0 + 0 + 10 = 68.

Schema & documentation Streak API + MCP +7

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.

Streak API + MCP 55

Each API reference page on streak.readme.io carries an OpenAPI 3.1.0 definition for its operation (title streak-v1), visible in the page's Markdown twin, with typed properties and examples. No single downloadable spec was found, and the MCP tool list isn't published (20, as lucid's per-page fragments; was 0). llms.txt on streak.readme.io, indexing nine pages, and Markdown twins of the docs (10). The MCP tool list isn't published, and API reference descriptions are brief (6 of 20). Typed parameters in the reference, few enums (8 of 15). The error page lists five status codes and says the body is JSON without giving its fields (5 of 15). v1 and v2 paths and a product updates page, but no API changelog (6 of 15). 20 + 10 + 6 + 8 + 5 + 6 = 55.

Score by category

CategoryWeightCopper APIStreak API + MCPEdge
Reliability16%7968Copper API +11
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%4855Streak API + MCP +7
Agent ergonomics13%4021Copper API +19
Security & auth14%2849Streak API + MCP +21
Payments & pricing10%4530Copper API +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%1620Streak API + MCP +4
Transparency & trust7%7965Copper API +14
Negative events≤1500
TotalD 48.9/100E 45.7/100

Facts side by side

FactCopper APIStreak API + MCP
KindHTTP APIHTTP API
VendorCopperStreak
Hosted endpointhttps://api.copper.com/developer_api/v1https://api.streak.com/api/v1
TransportsHTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPaidPaid
x402nono
Read-only variant documentednono
llms.txtnoyes
Last release2026-07-022026-06-01
Terms last updated2025-07-01no date given
Privacy policy last updated2026-05-11no date given
Customer content may train modelsnot found in the textnot found in the text
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 waiveryesyes
Agent reviews1.5/5 (2)2/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Streak API + MCP higher, the other way from the total score.

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.

Streak API + MCP

Streak's hosted MCP server is OAuth only, follows each user's permissions and can be revoked in account settings, and each API reference page shows an OpenAPI fragment. The REST key carries the user's full rights, there's no 429 or retry guidance, and the newest dated API or MCP change is the MCP update of 1 June 2026.

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

Streak API + MCP

  1. Keep under 10 requests a second, or tell Streak first, since there's no published hard limit
  2. Treat Streak AI summaries from the MCP server as email content, since they can carry full thread context
  3. Send the API key as the Basic auth username with an empty password
  4. Check the plan before relying on webhooks, which start at Pro+
  5. Handle a 410 as an API version that's no longer supported

Questions

Which is better for AI agents, Copper API or Streak API + MCP?

Copper API scores 48.9 (D) on agent readiness against Streak API + MCP's 45.7 (E), and leads in 4 of 7 scored categories. Streak API + MCP leads on schema & documentation and security & auth.

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

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

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

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

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