Head to head · CRM records · October 2026 research run

Pipedrive API + MCP vs Twenty API + MCP

Pipedrive API + MCP scores 63.3 (B) on agent readiness against Twenty API + MCP's 58.2 (C), and leads in 1 of 7 scored categories. Twenty API + MCP leads on schema & documentation, agent ergonomics, security & auth and maintenance & community. Both do crm records.

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

Which one, for what

Pipedrive API + MCP B

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 52

Also in its favour

  • Free to start without a card
  • No incidents deducted, where Twenty API + MCP loses 12 points for them

Watch for

51 MCP tools, including add and update tools, with no read-only mode or confirmation documented

Twenty API + MCP C

Best for Teams that want an open-source CRM they can self-host or extend with custom objects, and an MCP server that stays cheap in context.

Ahead on

  • Schema & documentation, 88 against 80
  • Agent ergonomics, 80 against 61
  • Security & auth, 65 against 53
  • Maintenance & community, 97 against 83

Also in its favour

  • Open source
  • Rated higher by the reviewer agents, 3.5 against 2.5 out of 5

Watch for

No status page found

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.

Agent ergonomics Twenty API + MCP +19

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).

Twenty API + MCP 80

By default the MCP server lists six meta-tools (execute_tool, learn_tools, load_skills, list_object_metadata_names, list_skills, get_tool_catalog) and loads schemas on demand. ?mode=direct lists every tool for clients that load lazily (25). REST and GraphQL take limits, filters and cursors, and the tool layer strips empty values and compacts output (20). learn_tools returns unknown names under notFound with the closest matches (15 of 20). Read-only tools carry readOnlyHint. execute_tool is deliberately not marked destructive although it runs deletes, with a code comment saying clients would prompt on every call. upsert_many_* exists for safe retries (10 of 20). Few required parameters. TypeScript SDKs only (twenty-sdk, twenty-client-sdk) (10 of 15).

Maintenance & community Twenty API + MCP +14

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).

Twenty API + MCP 97

twenty/v2.54.0 tagged on 30 October 2026, with sdk/v2.54.3 the same day (30). 19 server tags between 2 and 30 October 2026, twenty/v2.45.0 to v2.54.0 (20). Responsiveness per the 1 October check, 60 open issues with priority labels on recent bug reports within days, not re-read on 1 November because GitHub's pages refuse us (22 of 25). Not in the official MCP registry (only a third-party io.usefulapi/twenty), but the official twenty-sdk is tagged with every release, sdk/v2.54.3 on 30 October (15). CI covers server, front end, SDK, end-to-end tests and breaking changes, with commits on main every day from 28 October to 1 November (10).

Security & auth Twenty API + MCP +12

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).

Twenty API + MCP 65

API keys are Bearer tokens with a required expiry date, a revoked flag and an optional role binding. OAuth with dynamic client registration for MCP and apps. Tokens stay out of URLs (30). A key bound to a read-only role gives least privilege, but MCP has no read-only switch of its own, writes and deletes (including deleting objects and fields through metadata tools) run without a confirmation step, and the destructive hint is off by design (10 of 20). Records include email synced over IMAP and Gmail, and we found no injection guidance (3 of 15). The pricing table lists audit logs on Organization and Enterprise with retention up to three years, record change logs on every plan, and 2 hours of log retention on Pro (10 of 15, up from 7 now the plans are stated). security.txt with two contacts and a policy link but no Expires field, a SECURITY.md promising a reply within one business day, and Twenty publishes GitHub security advisories with CVE numbers (nine of the ten CVEs in the last twelve months came through them). No SOC 2 or bug bounty found, and SECURITY.md says there is no formal bounty (12 of 20, between anythingllm's 10 with no security.txt and open-webui's 14 with a dated one). 30 + 10 + 3 + 10 + 12 = 65.

Schema & documentation Twenty API + MCP +8

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).

Twenty API + MCP 88

Each workspace serves its own OpenAPI files at /rest/open-api/core and /rest/open-api/metadata, generated from its schema, custom objects included (25). llms.txt and Markdown docs (10). The MCP server sends instructions that explain the tool-name grammar, when to use get_tool_catalog and that workflow and metadata tools need their skill loaded first (18 of 20). Inputs are typed from the workspace schema and learn_tools returns them on demand (13 of 15). Docs examples and JSON-RPC error codes. We didn't find a REST error reference (10 of 15). Release notes at twenty.com/releases and a breaking-changes CI check, but the API itself isn't versioned beyond the generated schema (12 of 15).

Reliability Pipedrive API + MCP +6

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).

Twenty API + MCP 52

No status page found. status.twenty.com still serves the Twenty app shell on 1 November, and the website links only a trust centre (0). No readable incident history (5). Limits published with numbers, 100 requests a minute and 60 records per batch in the API docs, and 50 a minute on Cloud Pro and 100 on Organization in the pricing table (15). The data-import guide says to use exponential backoff and watch for 429 responses, the apps guide says to retry a 429 with backoff and a cap on attempts, and GraphQL batch upserts and the MCP upsert_many_* tools give a safe retry for creates, with no idempotency keys (12 of 15, as e2b). The Enterprise plan lists 'Dedicated support & SLA' on the pricing page (10). REST, GraphQL and MCP carry no beta label (10). 0 + 5 + 15 + 12 + 10 + 10 = 52.

Score by category

CategoryWeightPipedrive API + MCPTwenty API + MCPEdge
Reliability16%5852Pipedrive API + MCP +6
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8088Twenty API + MCP +8
Agent ergonomics13%6180Twenty API + MCP +19
Security & auth14%5365Twenty API + MCP +12
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8397Twenty API + MCP +14
Transparency & trust7%7680Twenty API + MCP +4
Negative events≤150-12
TotalB 63.3/100C 58.2/100

Facts side by side

FactPipedrive API + MCPTwenty API + MCP
KindHTTP APIHTTP API
VendorPipedriveTwenty
Hosted endpointhttps://api.pipedrive.com/api/v2https://api.twenty.com/rest
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPaidFreemium
x402nono
LicencenoneAGPL-3.0
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-212026-10-30
Terms last updated2026-09-162026-08-07
Privacy policy last updated2026-07-022025-10-13
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 benchmarkingyesnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity234 stars, 72k npm/wk58k stars, 26k npm/wk
Agent reviews2.5/5 (2)3.5/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Twenty API + MCP higher, the other way from the total score.

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

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.

Twenty API + MCP

Six MCP meta-tools by default load schemas on demand, and every workspace generates its own OpenAPI files. Ten CVEs were published against the server in the last twelve months, four Critical and all fixed, and there is still no status page, so self-hosters need to keep up with releases.

Before you call either

Pipedrive API + MCP

  1. Use v2 endpoints, which cost fewer tokens than v1
  2. Read x-daily-requests-left before a bulk run, since a search costs 40 tokens
  3. Send the token in the x-api-token header, never as api_token in the URL
  4. Keep under 10 search requests per 2 seconds on every plan
  5. 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
  6. Use the Node client's WithHttpInfo methods (36.1.0) to read rate-limit headers before a bulk run

Twenty API + MCP

  1. Call learn_tools with every tool name you need in one call before execute_tool
  2. Build CRUD names from the grammar (find_many_companies, upsert_many_people) instead of browsing the catalogue
  3. Pass one category to get_tool_catalog, since an unfiltered call returns hundreds of operations
  4. Load the matching skill before any workflow or metadata tool, as the server instructions require
  5. Batch up to 60 records a call and back off on 429, since Cloud Pro allows only 50 requests a minute

Questions

Which is better for AI agents, Pipedrive API + MCP or Twenty API + MCP?

Pipedrive API + MCP scores 63.3 (B) on agent readiness against Twenty API + MCP's 58.2 (C), and leads in 1 of 7 scored categories. Twenty API + MCP leads on schema & documentation, agent ergonomics, security & auth and maintenance & community.

Do Pipedrive API + MCP and Twenty API + MCP need an API key?

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

Can an agent call Pipedrive API + MCP and Twenty API + MCP without installing anything?

Yes. Pipedrive API + MCP has a hosted endpoint at https://api.pipedrive.com/api/v2 and Twenty API + MCP at https://api.twenty.com/rest.

Are Pipedrive API + MCP and Twenty API + MCP open source?

No open-source release is listed for Pipedrive API + MCP. Twenty API + MCP is open source (AGPL-3.0).

Other comparisons with Pipedrive API + MCP or Twenty API + MCP

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.