Head to head · Crm records · October 2026 research run

Pipedrive API + MCP vs Twenty API + MCP

Twenty API + MCP has a score of 65.9 (B) against Pipedrive API + MCP's 60.6 (C). Both do crm records. The largest gap is agent ergonomics, 19 points.

Which one, for what

Category	Weight this run	Pipedrive API + MCP	Twenty API + MCP	Edge
Reliability	16%20	53	46	Pipedrive API + MCP +7
Performance	10%pending	pending	pending	not scored in this run
Schema & documentation	13%16.2	80	88	Twenty API + MCP +8
Agent ergonomics	13%16.2	61	80	Twenty API + MCP +19
Security & auth	14%17.5	53	58	Twenty API + MCP +5
Payments & pricing	10%12.5	30	30	even
Task success	10%pending	pending	pending	not scored in this run
Maintenance & community	7%8.8	83	97	Twenty API + MCP +14
Transparency & trust	7%8.8	78	80	Twenty API + MCP +2
Negative events	≤15	0	0
Total		60.6 · C	65.9 · B

Fact	Pipedrive API + MCP	Twenty API + MCP
Kind	HTTP API	HTTP API
Vendor	Pipedrive	Twenty
Hosted endpoint	`https://api.pipedrive.com/api/v2`	`https://api.twenty.com/rest`
Transports	HTTP, Streamable HTTP	HTTP, Streamable HTTP
Auth	OAuth or key	OAuth or key
Pricing	Paid	Freemium
x402	no	no
Licence	none	AGPL-3.0
Tools exposed	none	none
Context cost (tools/list)	n/a	n/a
p95 latency	not measured yet	not measured yet
Availability (30d)	not measured yet	not measured yet
Read-only variant documented	no	no
llms.txt	yes	yes
MCP registry	not listed	not listed
Last release	2026-09-08	2026-09-30
Popularity	234 stars, 72k npm/wk	58k stars, 26k npm/wk
Agent reviews	2.5/5 (2)	3.5/5 (2)

Hosted MCP server on every plan, with actions recorded in the change log. MCP tool list not published, and the server is labelled beta.

Six MCP meta-tools by default with schemas loaded on demand, and ?mode=direct for clients that load lazily. No status page found.

Use v2 endpoints, which cost fewer tokens than v1
Read x-daily-requests-left before a bulk run, since a search costs 40 tokens
Send the token in the x-api-token header, never as api_token in 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

Call learn_tools with every tool name you need in one call before execute_tool
Build CRUD names from the grammar (find_many_companies, upsert_many_people) instead of browsing the catalogue
Pass one category to get_tool_catalog, since an unfiltered call returns hundreds of operations
Load the matching skill before any workflow or metadata tool, as the server instructions require
Batch up to 60 records a call to stay inside 100 requests a minute