Head to head · CRM records · October 2026 research run

Close API + MCP vs Nutshell

Close API + MCP scores 58 (C) on agent readiness against Nutshell's 51.6 (D), and leads in 5 of 7 scored categories. Nutshell leads on payments & pricing. Both do crm records.

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

Which one, for what

Close API + MCP C

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

  • Reliability, 56 against 45
  • Schema & documentation, 82 against 57
  • Agent ergonomics, 56 against 44
  • Security & auth, 66 against 58
  • Maintenance & community, 49 against 36

Watch for

141 MCP tools, and even the read scope loads 80

Nutshell D

Best for Small sales teams already on Nutshell who want an agent to read and update pipeline data over MCP or REST at a low seat price.

Ahead on

  • Payments & pricing, 53 against 45

Also in its favour

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

Watch for

No rate limit numbers, 429 handling or Retry-After found for the REST API

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.

Schema & documentation Close API + MCP +25

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.

Nutshell 57

Each of the 114 REST reference pages carries the OpenAPI 3.0 definition of its operation, but whole-spec download is disabled (18 of 25). llms.txt and Markdown for every docs page (10). 78 of 114 operations have a description, and the newer ones state scope and visibility rules (11 of 20). Enums on sort fields and patterns on IDs, but filters and custom fields are open objects and page[limit] is typed as a string on some operations (9 of 15). Schema examples are present, and error responses appear on 9 operations with no error body schema (5 of 15). The spec is version 2.0.0 and pages carry update stamps, with no dated API changelog (4 of 15).

Maintenance & community Close API + MCP +13

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.

Nutshell 36

The MCP server help article, updated 27 October 2026, documents create and update tools that the 8 October reading did not find, a dated change to a listed surface 8 days before the check (30 of 30). The REST reference pages carry update stamps, the newest 21 August 2026, but the stamps record no API change, and the product updates page is undated, so no other dated entry counts. One dated change in the 90 days from 6 August (0). No API changelog. Live support on every plan per the pricing page, untested (6 of 25). No current official SDK, and the MCP registry was not checked (0). No packages to judge (0). 30 + 0 + 6 + 0 + 0 = 36.

Agent ergonomics Close API + MCP +12

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.

Nutshell 44

The MCP server has about 18 groups of search and report tools and six groups of create and update tools per the help centre, updated 27 October 2026. The tool definitions sit behind OAuth and were not read. REST lists take page[limit] with no field selection (13 of 25). page[page], sort, q and filter[...] keys, with field lists from /accounts/list/fields, and no stated maximum page size (16 of 20). Error responses appear on 9 of 114 operations with no error body schema, partly met (4 of 20). No idempotency keys. Deletes can be undone within 30 days, and the MCP server cannot delete records, partly met (6 of 20). Few required fields, and no official REST SDK. The only client is a PHP JSON-RPC sample last pushed in 2023 (5 of 15).

Reliability Close API + MCP +11

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.

Nutshell 45

Read with the hosted lines. Status page at status.nutshell.com with 12 components and history back to 2017. None is named for the REST API or the MCP server, and the Nutshell application component is the CRM app as a whole, read as a vendor page with no component for the product (15). The incident line is re-read from the page's history feed. In the 90 days from 6 August one incident touched the product, a database cluster fault on 28 September 2026 that left Nutshell unavailable for some customers, partial, so minor (20 of 30). The 21 October PHP2Shell response disabled landing pages, email link tracking and scheduler pages on custom domains, not the API, and the 12 August and 16 October entries are announced maintenance. No rate limit numbers for REST, and the JSON-RPC docs say only that limits vary (0). No 429, Retry-After, backoff or idempotency guidance found (0). No SLA found, and the terms supply the service as is (0). The REST API is GA and the MCP server carries no beta label (10). 15 + 20 + 0 + 0 + 0 + 10 = 45.

Security & auth Close API + MCP +8

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.

Nutshell 58

The MCP server uses OAuth authorisation code with PKCE, dynamic client registration, a revocation endpoint and read and write scopes. REST uses unscoped API keys sent as an HTTP Basic password with a user's email, and a key can be allowed to impersonate any user (24 of 30). The MCP server now creates and updates records, but a connection approved with read-style access stays read-only, it acts with the user's own role, and it cannot delete. No read-only API key type was found (12 of 20). Records hold emails, notes and form submissions, with no injection guidance found (3 of 15). An audit log on Business and Enterprise covers logins, bulk edits and exports, and API changes are logged under the key name or the impersonated user (8 of 15). SOC 2 Type 1 from December 2025, a CASA assessment, a disclosure address with no acknowledgement time, no bounty and no security.txt (11 of 20).

Payments & pricing Nutshell +8

Close API + MCP 45

No x402, MPP or L402 (0). Plan prices public, Solo $9 a seat a month yearly or $19 monthly up to Scale $139 or $149, with calls at about $0.02 a minute passed through at cost, but nothing per API call (10). 14-day trial with no card, prices re-read on 1 November (20). A person signs up in a browser (0). 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.

Nutshell 53

No x402, MPP or L402 (0). Plan prices are public, $13 to $79 a seat a month billed yearly, with nothing per call (10). 14-day trial with no card, and the API is included (20). A person signs up in a browser and an admin creates the key. The docs publish sandbox credentials for a shared demo account, which lets an agent test calls with no signup but not reach its own data (5 of 20). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

Score by category

CategoryWeightClose API + MCPNutshellEdge
Reliability16%5645Close API + MCP +11
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8257Close API + MCP +25
Agent ergonomics13%5644Close API + MCP +12
Security & auth14%6658Close API + MCP +8
Payments & pricing10%4553Nutshell +8
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%4936Close API + MCP +13
Transparency & trust7%6872Nutshell +4
Negative events≤15-30
TotalC 58/100D 51.6/100

Facts side by side

FactClose API + MCPNutshell
KindHTTP APIHTTP API
VendorCloseNutshell, Inc.
Hosted endpointhttps://api.close.com/api/v1https://app.nutshell.com/rest
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyOAuth or key
PricingPaidPaid
x402nono
LicencenoneProprietary service under Nutshell's Terms of Service
Tools exposed141none
Read-only variant documentedyesyes
llms.txtyesyes
MCP registrycom.close/close-mcpnot listed
Last release2026-09-102026-10-27
Terms last updated2025-10-312026-06-02
Privacy policy last updated2026-05-302026-06-02
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticeyesyes
Arbitration or class-action waiveryesyes
Popularity70 stars, 14k PyPI/wknone
Agent reviews3.5/5 (2)none

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.

Nutshell

The REST reference is served as Markdown with an OpenAPI fragment per operation, and the hosted MCP server uses OAuth with PKCE and can create and update records but not delete them. No rate limit numbers, error format or API changelog were found in the reviewed documentation, and API keys carry no scopes.

Before you call either

Close API + MCP

  1. Connect with Close-Scope: mcp.read unless the job needs writes, and mcp.write_safe if it only creates
  2. Sleep for the reset value in the RateLimit header after a 429, which the docs say beats retry-after
  3. Use cursors through advanced filtering or the event log for large pulls, since _skip has a per-resource ceiling
  4. Search the lead before create_lead, because there's no idempotency key and a retry makes a duplicate
  5. Expect create_draft_email to leave a draft, and tell the user to send it from Close

Nutshell

  1. Authenticate REST calls with HTTP Basic, a Nutshell user's email as username and the API key as password, against https://app.nutshell.com/rest
  2. Use IDs in the <number>-<type> form, such as 3-accounts, and send updates as JSON Patch with content-type: application/json-patch+json
  3. Page lists with page[limit] and page[page], which is 0-based, and call /accounts/list/fields or the lead and contact equivalents for valid filter keys
  4. Ask for create and update access on the MCP consent page if the agent must write. A read-style grant stays read-only, and the MCP server cannot delete, so use REST for deletes
  5. Filter webhook events yourself, because every webhook receives all events and subscriptions are created in Setup, not through the API

Questions

Which is better for AI agents, Close API + MCP or Nutshell?

Close API + MCP scores 58 (C) on agent readiness against Nutshell's 51.6 (D), and leads in 5 of 7 scored categories. Nutshell leads on payments & pricing.

Do Close API + MCP and Nutshell need an API key?

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

Can an agent call Close API + MCP and Nutshell without installing anything?

Yes. Close API + MCP has a hosted endpoint at https://api.close.com/api/v1 and Nutshell at https://app.nutshell.com/rest.

Other comparisons with Close API + MCP or Nutshell

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.