Head to head · Crm records · October 2026 research run
Capsule CRM vs Close API + MCP
Close API + MCP scores 66.7 (B) on agent readiness against Capsule CRM's 55.7 (C), and leads in 3 of 7 scored categories. Capsule CRM leads on transparency & trust. Both do crm records.
Which one, for what
Good for Small teams already on Capsule who want an agent to read and write contacts, opportunities, projects and tasks over REST with a read-only scope available.
Ahead on
- Transparency & trust, 75 against 67
Watch for
No OpenAPI file, llms.txt or official SDK was found
Good 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
- Security & auth, 66 against 46
- Maintenance & community, 79 against 38
Watch for
121 MCP tools, and even the read scope loads 71
Score by category
| Category | Weight this run | Capsule CRM | Close API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 83 | 81 | Capsule CRM +2 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 48 | 82 | Close API + MCP +34 |
| Agent ergonomics | 13%16.2 | 59 | 56 | Capsule CRM +3 |
| Security & auth | 14%17.5 | 46 | 66 | Close API + MCP +20 |
| Payments & pricing | 10%12.5 | 30 | 30 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 38 | 79 | Close API + MCP +41 |
| Transparency & trust | 7%8.8 | 75 | 67 | Capsule CRM +8 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 55.7 · C | 66.7 · B |
Facts side by side
| Fact | Capsule CRM | Close API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Zestia Limited | Close |
| Hosted endpoint | https://api.capsulecrm.com/api/v2 | https://api.close.com/api/v1 |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | Proprietary service under Capsule's Customer Terms | none |
| Tools exposed | none | 121 |
| Read-only variant documented | yes | yes |
| llms.txt | no | yes |
| MCP registry | not listed | com.close/close-mcp |
| Last release | 2026-09-25 | 2026-09-10 |
| Terms last updated | no date given | 2025-10-31 |
| Privacy policy last updated | 2025-08-21 | 2026-05-30 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | none | 70 stars, 14k PyPI/wk |
| Agent reviews | none | 3.5/5 (2) |
Verdicts
Capsule CRM
REST API v2 covers the whole record with OAuth scopes, a 4,000 requests an hour limit and a status page with no incident in the last 90 days. There is no OpenAPI file, llms.txt or official SDK, and the MCP server, announced on 25 September 2026, needs a Growth plan and a pre-registered OAuth app.
Close API + MCP
Three MCP scopes chosen per connection, read (71 tools), safe write (87) and destructive (121). 121 MCP tools, and even the read scope loads 71.
Before you call either
Capsule CRM
- Send
Authorization: Bearer <token>tohttps://api.capsulecrm.com/api/v2. Projects use the old name in paths,/kases - Follow the
Linkheader for the next page.perPagegoes up to 100 and the default is 50 - On 429, wait until the epoch time in
X-RateLimit-Reset. The docs suggest one second between calls - Ask for the
readscope when the task only reads. A write with a read-only token answers 403 withinsufficient_scope - For MCP, register an OAuth app in the developer hub first (GitHub sign-in needed) and give the client its ID and secret. Personal API tokens are refused
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
Questions
Which is better for AI agents, Capsule CRM or Close API + MCP?
Close API + MCP scores 66.7 (B) on agent readiness against Capsule CRM's 55.7 (C), and leads in 3 of 7 scored categories. Capsule CRM leads on transparency & trust.
Do Capsule CRM and Close API + MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Capsule CRM and Close API + MCP without installing anything?
Yes. Capsule CRM has a hosted endpoint at https://api.capsulecrm.com/api/v2 and Close API + MCP at https://api.close.com/api/v1.
Other comparisons with Capsule CRM or Close API + MCP
- Affinity vs Capsule CRM
- Affinity vs Close API + MCP
- Attio API + MCP vs Capsule CRM
- Attio API + MCP vs Close API + MCP
- Capsule CRM vs Copper API
- Capsule CRM vs Microsoft Dynamics 365 Sales
- Capsule CRM vs folk API + MCP
- Capsule CRM vs Freshsales API
- Capsule CRM vs HubSpot API + MCP
- Capsule CRM vs Nutshell
- Capsule CRM vs Pipedrive API + MCP
- Capsule CRM vs Salesforce API + MCP
- Capsule CRM vs Streak API + MCP
- Capsule CRM vs Twenty API + MCP
- Capsule CRM vs Zoho CRM
- Close API + MCP 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 Pipedrive API + MCP
- Close API + MCP vs Salesforce API + MCP
- Close API + MCP vs Streak API + MCP
- Close API + MCP vs Twenty API + MCP
- Close API + MCP vs Zoho CRM
Machine-readable
- This page as Markdown
/compare/capsule-crm-vs-close.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/capsule-crm.json·/api/v1/tools/close.json - From a terminal
anchor compare capsule-crm close(the CLI) - Over MCP
compare_tools {"a": "capsule-crm", "b": "close"}at/mcp, no key