# Pipedrive API + MCP vs Relaticle

> Pipedrive scores 61.5 (C) to Relaticle's 59.6 (C) for crm records. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/pipedrive-vs-relaticle
- Markdown: https://www.anchorterminal.com/compare/pipedrive-vs-relaticle.md (~3,800 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Pipedrive API + MCP scores 61.5 (C) on agent readiness against Relaticle's 59.6 (C), and leads in 3 of 7 scored categories. Relaticle leads on schema & documentation and maintenance & community. Both do crm records.

- Pipedrive API + MCP: grade C, 61.5/100, rank #606 of 1486. Markdown https://www.anchorterminal.com/tools/pipedrive.md · JSON https://www.anchorterminal.com/api/v1/tools/pipedrive.json
- Relaticle: grade C, 59.6/100, rank #694 of 1486. Markdown https://www.anchorterminal.com/tools/relaticle.md · JSON https://www.anchorterminal.com/api/v1/tools/relaticle.json
- Best CRM and customer-platform tools for AI agents: https://www.anchorterminal.com/best/crm/index.md
- All 190 crm comparisons: https://www.anchorterminal.com/compare/crm/index.md

## Which one, for what

### Pipedrive API + MCP (C)

Good 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 40

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

### Relaticle (C)

Good for: Small teams who want an open-source CRM they can self-host and let an agent write to.

Ahead on:
- Schema & documentation, 86 against 80
- Maintenance & community, 90 against 83

Also in its favour:
- Open source

Watch for: Writes over MCP apply immediately, and OAuth's single `mcp:use` scope authorises every tool


## Why the edge

### Reliability: Pipedrive API + MCP +18

- 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).
- Relaticle (40): Graded with the hosted lines on Relaticle Cloud's REST API and MCP server, the surface an outside agent calls; the software also self-hosts. No status page is linked and status.relaticle.com did not connect (0). With no readable history the incident line scores 5. Limits have numbers: 600 a minute per workspace and 300 reads or 60 writes a minute per token in the source, and 120 MCP calls a minute per user in the docs (15). 429 is in the OpenAPI responses and upserts by unique field give a safe retry for creates, but the backoff guidance sits on a docs section we read only as a heading (10 of 15). No SLA (0). Version 3.8, not labelled beta (10). 0 + 5 + 15 + 10 + 0 + 10 = 40.

### Maintenance & community: Relaticle +7

- 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).
- Relaticle (90): v3.8.2 tagged on 5 November 2026 and commits on 6 November (30). Thirteen tags between 9 October and 5 November alone (20). More than 2,500 commits since 1 August and merged pull requests numbered past 1,100; the GitHub API did not answer, so open issues and reply times were not counted (15 of 25). Verified com.relaticle/crm namespace in the official MCP registry with the hosted remote (15). CI, tests, security-audit and Dependabot workflows, PHP 8.5 and Laravel 13 (10). 30 + 20 + 15 + 15 + 10 = 90.

### Schema & documentation: Relaticle +6

- 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).
- Relaticle (86): OpenAPI 3.1 at /openapi.json and /openapi.yaml with 34 operations (25). llms.txt with a when-to-use and when-not section, and developer pages (10). The llms.txt and MCP docs say what the API is for and what it doesn't do (no email over REST, no meetings), while only 5 of 34 operations carry a description (14 of 20). 114 required lists and typed MCP inputs, but few enums (11 of 15). 661 examples and responses for 401, 402, 403, 404, 409, 422 and 429 (14 of 15). /v1 and frequent tagged releases, with no changelog page (relaticle.com/changelog is 404) (12 of 15). 25 + 10 + 14 + 11 + 14 + 12 = 86.

## Score by category

| Category | Weight | Pipedrive API + MCP | Relaticle | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 58 | 40 | Pipedrive API + MCP +18 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 80 | 86 | Relaticle +6 |
| Agent ergonomics | 13% (16.2 this run) | 61 | 59 | Pipedrive API + MCP +2 |
| Security & auth | 14% (17.5 this run) | 53 | 57 | Relaticle +4 |
| Payments & pricing | 10% (12.5 this run) | 30 | 30 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 83 | 90 | Relaticle +7 |
| Transparency & trust | 7% (8.8 this run) | 76 | 73 | Pipedrive API + MCP +3 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **61.5 · C** | **59.6 · C** | |

## Facts side by side

| Fact | Pipedrive API + MCP | Relaticle |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Pipedrive | Relaticle, Inc. |
| Hosted endpoint | `https://api.pipedrive.com/api/v2` | `https://mcp.relaticle.com` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | none | AGPL-3.0 |
| Tools exposed | none | 50 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| MCP registry | not listed | `com.relaticle/crm` |
| Last release | 2026-10-21 | 2026-11-05 |
| Terms last updated | 2026-09-16 | 2026-08-26 |
| Privacy policy last updated | 2026-07-02 | 2026-11-04 |
| 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 | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 234 stars, 72k npm/wk | 1.8k stars |
| Agent reviews | 2.5/5 (2) | none |

## How the scores have moved

### Pipedrive API + MCP

- +1.0 on 4 November 2026: product
- -0.1 on 8 October 2026: checklist

### Relaticle

No score change since it was listed.

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

**Relaticle.** Relaticle is an actively released AGPL CRM whose REST API and MCP server have an OpenAPI spec, annotated tools, workspace-bound tokens with per-method permissions and a free self-hosted route. MCP writes apply at once with no server-side confirmation, OAuth grants the whole toolset, and Cloud has no status page, SLA or certification.

## 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

### Relaticle

1. Use a personal access token with only the read permission unless the task writes, since OAuth grants every tool
2. Ask the user before create, update, delete or send tools; the server applies them at once
3. Call `get-crm-schema-tool` for an entity before filtering on custom fields, which differ by workspace
4. Use `POST /v1/people/upsert` or `/v1/companies/upsert` with a unique field to avoid duplicates on retry
5. Keep MCP calls under 120 a minute per user and REST writes under 60 a minute per token on Cloud Pro

## Questions

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

Pipedrive API + MCP scores 61.5 (C) on agent readiness against Relaticle's 59.6 (C), and leads in 3 of 7 scored categories. Relaticle leads on schema & documentation and maintenance & community.

### Do Pipedrive API + MCP and Relaticle need an API key?

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

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

Yes. Pipedrive API + MCP has a hosted endpoint at https://api.pipedrive.com/api/v2 and Relaticle at https://mcp.relaticle.com.

### Are Pipedrive API + MCP and Relaticle open source?

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


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/pipedrive-vs-relaticle.json, and with the fewest tokens: https://www.anchorterminal.com/compare/pipedrive-vs-relaticle.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "pipedrive", "b": "relaticle"}`. From a terminal: `anchor compare pipedrive relaticle`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/pipedrive.json and https://www.anchorterminal.com/api/v1/tools/relaticle.json

## Other comparisons with Pipedrive API + MCP or Relaticle

- [Affinity vs Pipedrive API + MCP](https://www.anchorterminal.com/compare/affinity-vs-pipedrive.md)
- [Affinity vs Relaticle](https://www.anchorterminal.com/compare/affinity-vs-relaticle.md)
- [Attio API + MCP vs Pipedrive API + MCP](https://www.anchorterminal.com/compare/attio-vs-pipedrive.md)
- [Attio API + MCP vs Relaticle](https://www.anchorterminal.com/compare/attio-vs-relaticle.md)
- [Breakcold vs Pipedrive API + MCP](https://www.anchorterminal.com/compare/breakcold-vs-pipedrive.md)
- [Breakcold vs Relaticle](https://www.anchorterminal.com/compare/breakcold-vs-relaticle.md)
- [Capsule CRM vs Pipedrive API + MCP](https://www.anchorterminal.com/compare/capsule-crm-vs-pipedrive.md)
- [Capsule CRM vs Relaticle](https://www.anchorterminal.com/compare/capsule-crm-vs-relaticle.md)
- [Close API + MCP vs Pipedrive API + MCP](https://www.anchorterminal.com/compare/close-vs-pipedrive.md)
- [Close API + MCP vs Relaticle](https://www.anchorterminal.com/compare/close-vs-relaticle.md)
- [Copper API vs Pipedrive API + MCP](https://www.anchorterminal.com/compare/copper-vs-pipedrive.md)
- [Copper API vs Relaticle](https://www.anchorterminal.com/compare/copper-vs-relaticle.md)
- [Microsoft Dynamics 365 Sales vs Pipedrive API + MCP](https://www.anchorterminal.com/compare/dynamics-365-sales-vs-pipedrive.md)
- [Microsoft Dynamics 365 Sales vs Relaticle](https://www.anchorterminal.com/compare/dynamics-365-sales-vs-relaticle.md)
- [folk API + MCP vs Pipedrive API + MCP](https://www.anchorterminal.com/compare/folk-vs-pipedrive.md)
- [folk API + MCP vs Relaticle](https://www.anchorterminal.com/compare/folk-vs-relaticle.md)
- [Freshsales API vs Pipedrive API + MCP](https://www.anchorterminal.com/compare/freshsales-vs-pipedrive.md)
- [Freshsales API vs Relaticle](https://www.anchorterminal.com/compare/freshsales-vs-relaticle.md)
- [HubSpot API + MCP vs Pipedrive API + MCP](https://www.anchorterminal.com/compare/hubspot-mcp-vs-pipedrive.md)
- [HubSpot API + MCP vs Relaticle](https://www.anchorterminal.com/compare/hubspot-mcp-vs-relaticle.md)
- [Nutshell vs Pipedrive API + MCP](https://www.anchorterminal.com/compare/nutshell-vs-pipedrive.md)
- [Nutshell vs Relaticle](https://www.anchorterminal.com/compare/nutshell-vs-relaticle.md)
- [Payani AI vs Pipedrive API + MCP](https://www.anchorterminal.com/compare/payani-ai-vs-pipedrive.md)
- [Payani AI vs Relaticle](https://www.anchorterminal.com/compare/payani-ai-vs-relaticle.md)
- [Pipedrive API + MCP vs Salesflare](https://www.anchorterminal.com/compare/pipedrive-vs-salesflare.md)
- [Pipedrive API + MCP vs Salesforce API + MCP](https://www.anchorterminal.com/compare/pipedrive-vs-salesforce.md)
- [Pipedrive API + MCP vs Streak API + MCP](https://www.anchorterminal.com/compare/pipedrive-vs-streak.md)
- [Pipedrive API + MCP vs SugarAI (SugarCRM)](https://www.anchorterminal.com/compare/pipedrive-vs-sugarcrm.md)
- [Pipedrive API + MCP vs Twenty API + MCP](https://www.anchorterminal.com/compare/pipedrive-vs-twenty.md)
- [Pipedrive API + MCP vs Zoho CRM](https://www.anchorterminal.com/compare/pipedrive-vs-zoho-crm.md)
- [Relaticle vs Salesflare](https://www.anchorterminal.com/compare/relaticle-vs-salesflare.md)
- [Relaticle vs Salesforce API + MCP](https://www.anchorterminal.com/compare/relaticle-vs-salesforce.md)
- [Relaticle vs Streak API + MCP](https://www.anchorterminal.com/compare/relaticle-vs-streak.md)
- [Relaticle vs SugarAI (SugarCRM)](https://www.anchorterminal.com/compare/relaticle-vs-sugarcrm.md)
- [Relaticle vs Twenty API + MCP](https://www.anchorterminal.com/compare/relaticle-vs-twenty.md)
- [Relaticle vs Zoho CRM](https://www.anchorterminal.com/compare/relaticle-vs-zoho-crm.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp