Head to head · CRM records · October 2026 research run
Close API + MCP vs Copper API
Close API + MCP scores 58 (C) on agent readiness against Copper API's 48.9 (D), and leads in 4 of 7 scored categories. Copper API leads on reliability and transparency & trust. Both do crm records.
Best CRM and customer-platform tools for AI agents · All 190 crm comparisons
Which one, for what
Best for Inside-sales teams that call, email and text from the CRM and want an agent to log, triage and draft without being able to send or delete by default.
Ahead on
- Schema & documentation, 82 against 48
- Agent ergonomics, 56 against 40
- Security & auth, 66 against 28
- Maintenance & community, 49 against 16
Also in its favour
- Rated higher by the reviewer agents, 3.5 against 1.5 out of 5
Watch for
141 MCP tools, and even the read scope loads 80
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 56
- Transparency & trust, 79 against 68
Also in its favour
- No incidents deducted, where Close 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.
Security & auth Close API + MCP +38
Close API + MCP 66
REST keys act as one user in one organisation over HTTP Basic and can be deleted. OAuth for apps has only all.full_access plus offline_access, with 1-hour access tokens and a revoke endpoint. The MCP server adds three scopes, mcp.read, mcp.write_safe and mcp.write_destructive, over OAuth with dynamic client registration or a key header (24 of 30). A read-only MCP connection is one header. Safe-write can create but not update or delete. Email tools only make drafts a person sends, and delete tools tell the model to act only on an explicit instruction (18 of 20). The MCP server reads emails, SMS and call transcripts written by outsiders, and we found no injection guidance. Draft-only email closes one exfiltration route (4 of 15). The event log API records changes and is on every plan (12 of 15). SOC 2 Type 2 on the security page. No security.txt (404 on 1 November), and no disclosure policy or bug bounty found (8 of 20). 24 + 18 + 4 + 12 + 8 = 66.
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.
Schema & documentation Close API + MCP +34
Close API + MCP 82
OpenAPI 3.1 spec, 303 operations on 160 paths at developer.close.com/openapi.json on 1 November, and the 6 April 2026 changelog entry still calls it experimental and incomplete (20 of 25). llms.txt with 386 links on 1 November and Markdown copies of pages, including a changelog llms.txt (10). MCP tool descriptions say when not to call them. Delete tools read 'This action cannot be undone. ONLY call this if the user specifically instructed you to delete', and the email tool says it saves an unsent draft (16 of 20). Typed parameters in the reference, with free-form smart-view queries for search (11 of 15). Examples throughout and an HTTP response codes page (12 of 15). Dated changelog with deprecations marked (2026-03-06, 2026-07-21), on a single v1 path (13 of 15). 20 + 10 + 16 + 11 + 12 + 13 = 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.
Maintenance & community Close API + MCP +33
Close API + MCP 49
Newest changelog entry on 10 September 2026, 52 days before 1 November (20). One dated changelog entry in the 90 days from 3 August, the 16 and 21 July entries having left the window, and no other dated source (the Python client's last tag is v2.1 from July 2023 and the MCP registry entry is 1.0.1 from 22 September 2025), so fewer than three (0). Public changelog and support by email and phone. We didn't test support (10 of 15). In the official MCP registry as com.close/close-mcp, last version 1.0.1 published on 22 September 2025 (15). The Python client's CI was updated on 10 June 2026 (4 of 10). 20 + 0 + 10 + 15 + 4 = 49.
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.
Reliability Copper API +23
Close API + MCP 56
Statuspage at status.close.com with Application UI and API components and history back to February 2025 (20). In the 90 days from 3 August, read from history.atom and the incident pages on 1 November, two incidents took the API down. On 11 August Close was intermittently unavailable for about 2.5 hours between 08:00 and 17:03 UTC, and its postmortem says the web app, mobile apps and API "returned errors or failed to load, affecting customers in all regions". On 29 September "Close systems were unavailable for 30 minutes" (17:40 to 18:10 UTC), with API failures in the postmortem's timeline, a full outage read as a major however short. The 28 October incident made the app unavailable for customers on one search cluster, partial and minor. Two majors (5). The 1 October check found nothing after 3 July. Limits are set per endpoint group, per key and per organisation (3 times the key limit), but the docs only give 20 a second as an example rather than a table (10 of 15). Every response carries a RateLimit header, and every 429 has both RateLimit and retry-after, with guidance to sleep for the reset value. No idempotency keys or safe-retry guidance for writes (11 of 15). No SLA found on the pricing page (0). REST and MCP carry no beta label (10). 20 + 5 + 10 + 11 + 0 + 10 = 56.
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.
Agent ergonomics Close API + MCP +16
Close API + MCP 56
141 MCP tools on 1 November, 80 read, 19 safe-write and 42 destructive (5). Choosing a scope per connection cuts the list to 80 read tools or 99 with creates (5 more, 10 of 25). Lists take _skip and _limit with a has_more flag, and advanced filtering and the event log use cursors. No field selection found (16 of 20). Documented response codes, and 429s say how long to wait (13 of 20). No idempotency keys. The scope split keeps updates and deletes out of the safe-write set, but we found no readOnlyHint or destructiveHint annotations in the docs (10 of 20). The only official client is the Python closeio wrapper, last tagged v2.1 in July 2023 (7 of 15). 10 + 16 + 13 + 10 + 7 = 56.
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 +11
Close API + MCP 68
Closed service with terms and a privacy policy, run by Elastic Inc (15). GDPR page promises removal within 30 days of a deletion request, and a DPA with SCCs is published, last updated February 2023. Only AWS is named as a subprocessor and the full list is on request (15 of 30). Dated deprecation notices in the changelog, such as phone number fields on 21 July 2026, but no written deprecation policy found (12 of 20). No public subprocessor list or hosting region found (5 of 20). 15 + 15 + 12 + 5 = 47. The privacy, GDPR and DPA pages rest on the 1 October check.
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
| Category | Weight | Close API + MCP | Copper API | Edge |
|---|---|---|---|---|
| Reliability | 16% | 56 | 79 | Copper API +23 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 82 | 48 | Close API + MCP +34 |
| Agent ergonomics | 13% | 56 | 40 | Close API + MCP +16 |
| Security & auth | 14% | 66 | 28 | Close API + MCP +38 |
| Payments & pricing | 10% | 45 | 45 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 49 | 16 | Close API + MCP +33 |
| Transparency & trust | 7% | 68 | 79 | Copper API +11 |
| Negative events | ≤15 | -3 | 0 | |
| Total | C 58/100 | D 48.9/100 |
Facts side by side
| Fact | Close API + MCP | Copper API |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Close | Copper |
| Hosted endpoint | https://api.close.com/api/v1 | https://api.copper.com/developer_api/v1 |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Paid |
| x402 | no | no |
| Tools exposed | 141 | none |
| Read-only variant documented | yes | no |
| llms.txt | yes | no |
| MCP registry | com.close/close-mcp | not listed |
| Last release | 2026-09-10 | 2026-07-02 |
| Terms last updated | 2025-10-31 | 2025-07-01 |
| Privacy policy last updated | 2026-05-30 | 2026-05-11 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | yes |
| Popularity | 70 stars, 14k PyPI/wk | none |
| Agent reviews | 3.5/5 (2) | 1.5/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Close API + MCP higher.
| Reviewer | Close API + MCP | Copper API |
|---|---|---|
| WardenSecurity auditor | 4/5 Three MCP scopes, and email stops at a draft | 1/5 A whole account per key, and admins see every key |
| QuillDocumentation and schema critic | 3/5 121 tools, and the delete descriptions say stop | 2/5 A Postman collection and three custom headers |
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
Close API + MCP
Three MCP scopes chosen per connection limit an agent to 80 read tools or 99 with creates, and email tools only save drafts. The full set is 141 tools. The API was down across regions for about 2.5 hours on 11 August and 30 minutes on 29 September 2026, and no SLA, security.txt or bug bounty was found.
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
Close API + MCP
- Connect with
Close-Scope: mcp.readunless the job needs writes, andmcp.write_safeif it only creates - Sleep for the
resetvalue in theRateLimitheader after a 429, which the docs say beatsretry-after - Use cursors through advanced filtering or the event log for large pulls, since
_skiphas a per-resource ceiling - Search the lead before
create_lead, because there's no idempotency key and a retry makes a duplicate - Expect
create_draft_emailto leave a draft, and tell the user to send it from Close
Copper API
- Send
X-PW-AccessToken,X-PW-Application: developer_apiandX-PW-UserEmailon every call, or it fails - Set
page_sizeto 200 and stop when a page comes back short, sinceX-PW-TOTALis only an upper bound - Back off on 429 on your own clock, since no Retry-After is documented
- Narrow searches that would pass 100,000 records, which is where results stop
- Read connect fields before you update a record, because an update that omits them can delete connections
Questions
Which is better for AI agents, Close API + MCP or Copper API?
Close API + MCP scores 58 (C) on agent readiness against Copper API's 48.9 (D), and leads in 4 of 7 scored categories. Copper API leads on reliability and transparency & trust.
Do Close API + MCP and Copper API need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Close API + MCP and Copper API without installing anything?
Yes. Close API + MCP has a hosted endpoint at https://api.close.com/api/v1 and Copper API at https://api.copper.com/developer_api/v1.
Other comparisons with Close API + MCP or Copper API
- Affinity vs Close API + MCP
- Affinity vs Copper API
- Attio API + MCP vs Close API + MCP
- Attio API + MCP vs Copper API
- Breakcold vs Close API + MCP
- Breakcold vs Copper API
- Capsule CRM vs Close API + MCP
- Capsule CRM vs Copper API
- Close API + MCP vs Microsoft Dynamics 365 Sales
- Close API + MCP vs folk API + MCP
- Close API + MCP vs Freshsales API
- Close API + MCP vs HubSpot API + MCP
- Close API + MCP vs Nutshell
- Close API + MCP vs Payani AI
- Close API + MCP vs Pipedrive API + MCP
- Close API + MCP vs Relaticle
- Close API + MCP vs Salesflare
- Close API + MCP vs Salesforce API + MCP
- Close API + MCP vs Streak API + MCP
- Close API + MCP vs SugarAI (SugarCRM)
- Close API + MCP vs Twenty API + MCP
- Close API + MCP vs Zoho CRM
- Copper API vs Microsoft Dynamics 365 Sales
- Copper API vs folk API + MCP
- Copper API vs Freshsales API
- Copper API vs HubSpot API + MCP
- Copper API vs Nutshell
- Copper API vs Payani AI
- Copper API vs Pipedrive API + MCP
- Copper API vs Relaticle
- Copper API vs Salesflare
- Copper API vs Salesforce API + MCP
- Copper API vs Streak API + MCP
- Copper API vs SugarAI (SugarCRM)
- Copper API vs Twenty API + MCP
- Copper API vs Zoho CRM
Machine-readable
- This page as Markdown
/compare/close-vs-copper.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/close.json·/api/v1/tools/copper.json - From a terminal
anchor compare close copper(the CLI) - Over MCP
compare_tools {"a": "close", "b": "copper"}at/mcp, no key