Head to head · CRM records · October 2026 research run
Nutshell vs Pipedrive API + MCP
Pipedrive API + MCP scores 63.3 (B) on agent readiness against Nutshell's 51.6 (D), and leads in 5 of 7 scored categories. Nutshell leads on security & auth and payments & pricing. Both do crm records.
Best CRM and customer-platform tools for AI agents · All 190 crm comparisons
Which one, for what
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
- Security & auth, 58 against 53
- Payments & pricing, 53 against 45
Watch for
No rate limit numbers, 429 handling or Retry-After found for the REST API
Best for Small and mid-size sales teams running deal pipelines who want an agent to update deals and log activities.
Ahead on
- Reliability, 58 against 45
- Schema & documentation, 80 against 57
- Agent ergonomics, 61 against 44
- Maintenance & community, 83 against 36
Watch for
51 MCP tools, including add and update tools, with no read-only mode or confirmation documented
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 Pipedrive API + MCP +47
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.
Pipedrive API + MCP 83
Node client v36.1.0 on 21 October 2026 (30). Node releases on 6 August, 13 August, twice on 8 September, and 13 more from 9 to 21 October, counted half as SDK tags (20). Public changelog with dated entries, the newest announced on 29 July and effective 1 August 2026. We didn't test support (10 of 15). Not in the official MCP registry (only third-party Pipedrive servers), but official SDKs are current (15). The Node client publishes from CI, and a workflow auto-closes stale issues (8 of 10).
Schema & documentation Pipedrive API + MCP +23
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).
Pipedrive API + MCP 80
OpenAPI 3.0.1 file for v2, re-read on 4 November with 158 operations and the token in the x-api-token header (25). llms.txt on the readme.io docs (10). Pipedrive's MCP tools article (updated 22 October 2026) lists 51 tools by resource, each with its action and some with a use case; the server's own tool definitions weren't read. API reference descriptions are adequate (10 of 20). Typed parameters in the OpenAPI (12 of 15). Examples on every reference page. We didn't read an error reference (10 of 15). v1 and v2 paths and a dated changelog that flags breaking changes and deprecations (13 of 15).
Agent ergonomics Pipedrive API + MCP +17
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).
Pipedrive API + MCP 61
Pipedrive's MCP tools article (updated 22 October 2026) lists 51 tools, and Pipedrive's own Claude guide warns the client may not load every tool by default. v2 list endpoints take a limit and a cursor (12 of 25). Cursor pagination and filters on v2 (18 of 20). We didn't check the error format closely (12 of 20). No idempotency keys or tool annotations found (4 of 20). Official SDKs for Node (36.1.0, 21 October 2026) and PHP (15).
Reliability Pipedrive API + MCP +13
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.
Pipedrive API + MCP 58
Status page at status.pipedrive.com (run on Sorry), linked from Pipedrive's developer pages, with components including REST API v1 but nothing for API v2 or the MCP server, per the 1 October check (20). On 4 November its robots.txt answered an empty 406, which this run reads as a refusal, so the 1 October incident readings from it are struck and no part of the window from 6 August could be read (5). Rate limits documented in detail, a daily token budget per company plus burst limits per 2 seconds by plan and auth type (15). Responses carry x-ratelimit-* and x-daily-requests-left headers and a 429 when the budget runs out. The rate-limit page gives no Retry-After or safe-retry guidance for writes, though the Node client's 36.1.0 notes (21 October) mention Retry-After on a 429 (8 of 15). No SLA found (0). REST is GA, and the MCP setup article for Claude, updated on 22 October 2026, no longer labels the server beta (10).
Payments & pricing Nutshell +8
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.
Pipedrive API + MCP 45
No x402, MPP or L402 (0). Plan prices public, Lite $14 to Ultimate $79 a seat a month billed yearly, with token top-ups from $100 a month. No per-call price for the API (10). 14-day trial with no card (20). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Security & auth Nutshell +5
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).
Pipedrive API + MCP 53
Personal API tokens carry the user's full rights, one active per user per company, and per the 30 September check older docs still show the token as an api_token query parameter. OAuth 2.0 with scopes for apps, and the MCP server is OAuth only with scopes for deals, contacts, leads, activities, products and search (25, less 10 for the query-string option, 15 of 30). No read-only mode or write confirmation documented for MCP (7 of 20). Email sync and notes reach the model, and we found no injection guidance (3 of 15). The launch post says every MCP action is recorded in Pipedrive's change logs (12 of 15). ISO 27001:2022, ISO 27701, SOC 2 Type 2 and SOC 3 in the trust centre, with a responsible disclosure programme. No security.txt (404) (16 of 20).
Score by category
| Category | Weight | Nutshell | Pipedrive API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 45 | 58 | Pipedrive API + MCP +13 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 57 | 80 | Pipedrive API + MCP +23 |
| Agent ergonomics | 13% | 44 | 61 | Pipedrive API + MCP +17 |
| Security & auth | 14% | 58 | 53 | Nutshell +5 |
| Payments & pricing | 10% | 53 | 45 | Nutshell +8 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 36 | 83 | Pipedrive API + MCP +47 |
| Transparency & trust | 7% | 72 | 76 | Pipedrive API + MCP +4 |
| Negative events | ≤15 | 0 | 0 | |
| Total | D 51.6/100 | B 63.3/100 |
Facts side by side
| Fact | Nutshell | Pipedrive API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Nutshell, Inc. | Pipedrive |
| Hosted endpoint | https://app.nutshell.com/rest | https://api.pipedrive.com/api/v2 |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | Proprietary service under Nutshell's Terms of Service | none |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| Last release | 2026-10-27 | 2026-10-21 |
| Terms last updated | 2026-06-02 | 2026-09-16 |
| Privacy policy last updated | 2026-06-02 | 2026-07-02 |
| 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 | yes | yes |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | yes | yes |
| Popularity | none | 234 stars, 72k npm/wk |
| Agent reviews | none | 2.5/5 (2) |
How the scores have moved
Verdicts
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.
Pipedrive API + MCP
Hosted MCP server on every plan, with actions recorded in the change log and no beta label in its setup guide since 22 October 2026. No read-only mode or confirmation is documented for its write tools, and the status page's history couldn't be read on 4 November.
Before you call either
Nutshell
- 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 - Use IDs in the
<number>-<type>form, such as3-accounts, and send updates as JSON Patch withcontent-type: application/json-patch+json - Page lists with
page[limit]andpage[page], which is 0-based, and call/accounts/list/fieldsor the lead and contact equivalents for valid filter keys - 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
- Filter webhook events yourself, because every webhook receives all events and subscriptions are created in Setup, not through the API
Pipedrive API + MCP
- Use v2 endpoints, which cost fewer tokens than v1
- Read
x-daily-requests-leftbefore a bulk run, since a search costs 40 tokens - Send the token in the
x-api-tokenheader, never asapi_tokenin the URL - Keep under 10 search requests per 2 seconds on every plan
- Ask the user to load all Pipedrive tools in the client if an expected tool is missing, since Claude may not load every tool by default
- Use the Node client's
WithHttpInfomethods (36.1.0) to read rate-limit headers before a bulk run
Questions
Which is better for AI agents, Nutshell or Pipedrive API + MCP?
Pipedrive API + MCP scores 63.3 (B) on agent readiness against Nutshell's 51.6 (D), and leads in 5 of 7 scored categories. Nutshell leads on security & auth and payments & pricing.
Do Nutshell and Pipedrive API + MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Nutshell and Pipedrive API + MCP without installing anything?
Yes. Nutshell has a hosted endpoint at https://app.nutshell.com/rest and Pipedrive API + MCP at https://api.pipedrive.com/api/v2.
Other comparisons with Nutshell or Pipedrive API + MCP
- Affinity vs Nutshell
- Affinity vs Pipedrive API + MCP
- Attio API + MCP vs Nutshell
- Attio API + MCP vs Pipedrive API + MCP
- Breakcold vs Nutshell
- Breakcold vs Pipedrive API + MCP
- Capsule CRM vs Nutshell
- Capsule CRM vs Pipedrive API + MCP
- Close API + MCP vs Nutshell
- Close API + MCP vs Pipedrive API + MCP
- Copper API vs Nutshell
- Copper API vs Pipedrive API + MCP
- Microsoft Dynamics 365 Sales vs Nutshell
- Microsoft Dynamics 365 Sales vs Pipedrive API + MCP
- folk API + MCP vs Nutshell
- folk API + MCP vs Pipedrive API + MCP
- Freshsales API vs Nutshell
- Freshsales API vs Pipedrive API + MCP
- HubSpot API + MCP vs Nutshell
- HubSpot API + MCP vs Pipedrive API + MCP
- Nutshell vs Payani AI
- Nutshell vs Relaticle
- Nutshell vs Salesflare
- Nutshell vs Salesforce API + MCP
- Nutshell vs Streak API + MCP
- Nutshell vs SugarAI (SugarCRM)
- Nutshell vs Twenty API + MCP
- Nutshell vs Zoho CRM
- Payani AI vs Pipedrive API + MCP
- Pipedrive API + MCP vs Relaticle
- Pipedrive API + MCP vs Salesflare
- Pipedrive API + MCP vs Salesforce API + MCP
- Pipedrive API + MCP vs Streak API + MCP
- Pipedrive API + MCP vs SugarAI (SugarCRM)
- Pipedrive API + MCP vs Twenty API + MCP
- Pipedrive API + MCP vs Zoho CRM
Machine-readable
- This page as Markdown
/compare/nutshell-vs-pipedrive.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/nutshell.json·/api/v1/tools/pipedrive.json - From a terminal
anchor compare nutshell pipedrive(the CLI) - Over MCP
compare_tools {"a": "nutshell", "b": "pipedrive"}at/mcp, no key