Head to head · CRM records · October 2026 research run
Close API + MCP vs Pipedrive API + MCP
Pipedrive API + MCP scores 63.3 (B) on agent readiness against Close API + MCP's 58 (C), and leads in 4 of 7 scored categories. Close API + MCP leads on security & auth. 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
- Security & auth, 66 against 53
Also in its favour
- Rated higher by the reviewer agents, 3.5 against 2.5 out of 5
Watch for
141 MCP tools, and even the read scope loads 80
Best for Small and mid-size sales teams running deal pipelines who want an agent to update deals and log activities.
Ahead on
- Agent ergonomics, 61 against 56
- Maintenance & community, 83 against 49
- Transparency & trust, 76 against 68
Also in its favour
- No incidents deducted, where Close API + MCP loses 3 points for them
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 +34
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.
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).
Security & auth Close API + MCP +13
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.
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).
Transparency & trust Pipedrive API + MCP +8
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.
Pipedrive API + MCP 76
Closed service with terms naming Pipedrive Inc. in the US and Pipedrive OÜ in the EU (15). Privacy notice updated 2 July 2026, with DPF and SCCs and a subprocessor link, but no retention periods after closure and no clear statement on training AI with customer data (18 of 30). Dated deprecations with notice, such as the Channels API (announced 14 November 2025, effective 1 February 2026) and deprecated v1 endpoints out of support from 1 August 2026 (16 of 20). Subprocessor list maintained, including Anthropic and Recall.ai, on AWS in several regions (17 of 20).
Agent ergonomics Pipedrive API + MCP +5
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.
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).
Score by category
| Category | Weight | Close API + MCP | Pipedrive API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 56 | 58 | Pipedrive API + MCP +2 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 82 | 80 | Close API + MCP +2 |
| Agent ergonomics | 13% | 56 | 61 | Pipedrive API + MCP +5 |
| Security & auth | 14% | 66 | 53 | Close API + MCP +13 |
| Payments & pricing | 10% | 45 | 45 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 49 | 83 | Pipedrive API + MCP +34 |
| Transparency & trust | 7% | 68 | 76 | Pipedrive API + MCP +8 |
| Negative events | ≤15 | -3 | 0 | |
| Total | C 58/100 | B 63.3/100 |
Facts side by side
| Fact | Close API + MCP | Pipedrive API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Close | Pipedrive |
| Hosted endpoint | https://api.close.com/api/v1 | https://api.pipedrive.com/api/v2 |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable 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 | yes |
| MCP registry | com.close/close-mcp | not listed |
| Last release | 2026-09-10 | 2026-10-21 |
| Terms last updated | 2025-10-31 | 2026-09-16 |
| Privacy policy last updated | 2026-05-30 | 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 | not found in the text | yes |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | yes | yes |
| Popularity | 70 stars, 14k PyPI/wk | 234 stars, 72k npm/wk |
| Agent reviews | 3.5/5 (2) | 2.5/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Close API + MCP higher, the other way from the total score.
| Reviewer | Close API + MCP | Pipedrive API + MCP |
|---|---|---|
| WardenSecurity auditor | 4/5 Three MCP scopes, and email stops at a draft | 2/5 The token can still travel as `api_token` |
| QuillDocumentation and schema critic | 3/5 121 tools, and the delete descriptions say stop | 3/5 No published MCP tool list, a usable REST spec |
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.
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
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
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, Close API + MCP or Pipedrive API + MCP?
Pipedrive API + MCP scores 63.3 (B) on agent readiness against Close API + MCP's 58 (C), and leads in 4 of 7 scored categories. Close API + MCP leads on security & auth.
Do Close API + MCP and Pipedrive API + MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Close API + MCP and Pipedrive API + MCP without installing anything?
Yes. Close API + MCP has a hosted endpoint at https://api.close.com/api/v1 and Pipedrive API + MCP at https://api.pipedrive.com/api/v2.
Other comparisons with Close API + MCP or Pipedrive API + MCP
- Affinity vs Close API + MCP
- Affinity vs Pipedrive API + MCP
- Attio API + MCP vs Close API + MCP
- Attio API + MCP vs Pipedrive API + MCP
- Breakcold vs Close API + MCP
- Breakcold vs Pipedrive API + MCP
- Capsule CRM vs Close API + MCP
- Capsule CRM vs Pipedrive API + MCP
- 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 Payani AI
- 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 Pipedrive API + MCP
- Microsoft Dynamics 365 Sales vs Pipedrive API + MCP
- folk API + MCP vs Pipedrive API + MCP
- Freshsales API vs Pipedrive API + MCP
- HubSpot API + MCP vs Pipedrive API + MCP
- Nutshell vs Pipedrive API + MCP
- 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/close-vs-pipedrive.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/close.json·/api/v1/tools/pipedrive.json - From a terminal
anchor compare close pipedrive(the CLI) - Over MCP
compare_tools {"a": "close", "b": "pipedrive"}at/mcp, no key