Head to head · CRM records · October 2026 research run

Attio API + MCP vs Copper API

Attio API + MCP scores 62.8 (B) on agent readiness against Copper API's 48.9 (D), and leads in 4 of 7 scored categories. Copper API leads on transparency & trust. Both do crm records.

Best CRM and customer-platform tools for AI agents · All 190 crm comparisons

Which one, for what

Attio API + MCP B

Best for Small teams and startups that want an agent to search across records, notes, emails and calls and then update the CRM, starting free.

Ahead on

  • Schema & documentation, 82 against 48
  • Agent ergonomics, 62 against 40
  • Security & auth, 56 against 28
  • Maintenance & community, 63 against 16

Also in its favour

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

Watch for

48 MCP tools with no read-only mode or toolsets, including delete and merge tools

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

  • Transparency & trust, 79 against 69

Also in its favour

  • No incidents deducted, where Attio API + MCP loses 3 points for them

Watch for

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

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 Attio API + MCP +47

Attio API + MCP 63

REST changelog entries on 28 October (writable avatar_url and logo_url), 27 October, 15 October and 14 October 2026, and MCP entries on 14 October and 1 October (30). Seventeen dated entries (13 REST, 4 MCP) across the REST and MCP changelogs since 4 August 2026 (20). Closed service with public changelogs and a support address. We didn't test support (10 of 15). Not in the official MCP registry. A search for attio on 2 November returns only third-party servers (kesslerio, kaszek, Smithery). No official REST SDK (0). The only npm package is the App SDK CLI, version not re-read (3 of 10). 30 + 20 + 10 + 0 + 3 = 63.

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.

Schema & documentation Attio API + MCP +34

Attio API + MCP 82

Three public OpenAPI files (API, standard objects, webhooks) at api.attio.com/openapi, per the 1 October check (25). llms.txt now lists 399 links, with Markdown copies of every page (10). Each MCP tool gets a one-line purpose and example prompts in the docs. We couldn't read the hosted server's own tool definitions, so when-not-to-use guidance is unchecked (12 of 20). Typed parameters in the OpenAPI, but filters are a nested JSON object the agent has to build (11 of 15). Examples on reference pages and a documented error body with status_code, type, code and message (12 of 15). Dated public changelogs for the REST API, the MCP server and the App SDK, but no versioning or deprecation policy beyond the v2 path (12 of 15). 25 + 10 + 12 + 11 + 12 + 12 = 82.

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.

Security & auth Attio API + MCP +28

Attio API + MCP 56

Workspace API keys and OAuth tokens share one set of per-endpoint scopes, a token revocation endpoint shipped on 11 September 2026, and since 15 October OAuth tokens can be user-level, limited to one member's data and permissions. The MCP server is OAuth only and works as the signed-in user. HTTP Basic is supported but discouraged, and we found no query-string token option (27 of 30). A read-scoped key gives least privilege on REST. The MCP server has no read-only mode, its writes rely on client confirmation, and it can delete comments and tasks and merge records. A REST endpoint added on 4 September 2026 deletes a whole custom object, which the changelog calls destructive and irreversible (13 of 20). The MCP server returns email bodies, call transcripts and notes written by outsiders, and we found no prompt-injection guidance (2 of 15). No audit-log documentation found in the API or MCP docs. Attribute history on records is the nearest thing (4 of 15). attio.com publishes a Vulnerability Disclosure Policy with safe harbour, a 72-hour confirmation and a 90-day disclosure window covering app, api, cdn and attio.com, which the 1 October check didn't record. The DPA promises yearly third-party penetration tests and breach notice within 72 hours. The Vanta-hosted trust centre wasn't read, so certifications are unchecked. No security.txt (404 on 2 November) and no bug bounty found. agentvfs scores 7 for a disclosure policy alone, and the DPA's testing and breach commitments add 3 (10 of 20, was 6). 27 + 13 + 2 + 4 + 10 = 56.

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.

Agent ergonomics Attio API + MCP +22

Attio API + MCP 62

The MCP server now lists 48 tools, after delete-task on 1 October and six activity tools on 14 October 2026, with no toolsets, no read-only subset and no dynamic loading (5). Semantic search tools over notes, emails and call recordings save a few listing calls (3 more, 8 of 25). REST lists take limit, offset, filters and sorts, and comment threads paginate at 80 replies and 250 comments a page (20). Errors carry a machine code and a message, and 429s say when to retry (15 of 20). The docs say the server uses MCP safety annotations, with reads auto-approved and writes asking the user to confirm in the client, and REST has upsert endpoints. We didn't read the annotations on the tools themselves (12 of 20). No official REST SDK in any language. The npm package attio is the App SDK CLI, not an API client (7 of 15). 8 + 20 + 15 + 12 + 7 = 62.

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.

Transparency & trust Copper API +10

Attio API + MCP 69

Closed service. New customers since June 2026 accept the Attio Services Agreement (last updated May 2026), which names Attio Inc. for US customers since 5 November 2025 and Attio Limited (London) otherwise. Earlier customers keep the Legacy Customer Terms (15). Privacy policy updated October 2026 and a DPA (last updated September 2026) with a sub-processor annex, 30 days' notice of new sub-processors to subscribers, 30 days to export after termination, deletion on request within 30 days and breach notice within 72 hours. Retention otherwise reads 'as long as necessary' (20 of 30). No deprecation policy found. The changelogs carry dated changes but no deprecation notices, and the 27 October change to call recordings took effect the day it was posted (4 of 20). Sub-processors named in the DPA annex, including Google Cloud, Cloudflare, OpenAI and Anthropic, but no hosting regions stated (12 of 20). 15 + 20 + 4 + 12 = 51.

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.

Score by category

CategoryWeightAttio API + MCPCopper APIEdge
Reliability16%7779Copper API +2
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8248Attio API + MCP +34
Agent ergonomics13%6240Attio API + MCP +22
Security & auth14%5628Attio API + MCP +28
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6316Attio API + MCP +47
Transparency & trust7%6979Copper API +10
Negative events≤15-30
TotalB 62.8/100D 48.9/100

Facts side by side

FactAttio API + MCPCopper API
KindHTTP APIHTTP API
VendorAttioCopper
Hosted endpointhttps://api.attio.com/v2https://api.copper.com/developer_api/v1
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyOAuth or key
PricingFreemiumPaid
x402nono
Tools exposed48none
Read-only variant documentednono
llms.txtyesno
Last release2026-10-282026-07-02
Terms last updated2025-11-012025-07-01
Privacy policy last updated2026-06-012026-05-11
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesyes
Popularity9.9k npm/wknone
Agent reviews3/5 (2)1.5/5 (2)

The panel on both

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

Attio API + MCP

API, webhooks and the hosted MCP server are on the Free plan for 3 seats with no card, and REST keys and OAuth tokens take per-endpoint scopes. The 48 MCP tools have no read-only mode or toolsets and include delete and merge tools, and thread pagination changed on the day it was announced.

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.

Before you call either

Attio API + MCP

  1. Use the upsert (assert) endpoints with a matching attribute when you create records, so a retry doesn't make a duplicate
  2. Wait until the Retry-After date on a 429, usually the next second
  3. Simplify filters and sorts if a list query fails its score-based limit
  4. Page through threads with cursor and limit. Get a thread returns at most 250 comments a request
  5. Ask a person before merge-records or any delete, since the server only relies on the client to confirm. Treat email and transcript text as untrusted input

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

Questions

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

Attio API + MCP scores 62.8 (B) on agent readiness against Copper API's 48.9 (D), and leads in 4 of 7 scored categories. Copper API leads on transparency & trust.

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

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

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

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

Other comparisons with Attio API + MCP or Copper API

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.