Head to head · CRM records · October 2026 research run

Freshsales API vs Pipedrive API + MCP

Pipedrive API + MCP scores 63.3 (B) on agent readiness against Freshsales API's 39.5 (E), and leads in 6 of 7 scored categories. Both do crm records.

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

Which one, for what

Freshsales API E

Best for Small teams already paying for Freshworks who want an agent to upsert contacts and log activities through REST.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

No MCP server for Freshsales

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 36
  • Schema & documentation, 80 against 27
  • Agent ergonomics, 61 against 48
  • Security & auth, 53 against 44
  • Maintenance & community, 83 against 5

Also in its favour

  • A hosted endpoint, with nothing to install
  • Rated higher by the reviewer agents, 2.5 against 2.0 out of 5

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 +78

Freshsales API 5

No public API changelog or release notes for the Freshsales API found; the reference page was last modified on 9 October 2024 per its server header, so no last change date (0). No dated entries in the last 90 days found (0). Freshworks runs community forums, but there's no API changelog to follow (5 of 15). No official Freshsales SDK. The FDK is for marketplace apps, not API calls (0). No packages to judge (0). Freshworks' MCP integration articles cover Freshdesk and Freshservice, not Freshsales (checked 10 November 2026). 0 + 0 + 5 + 0 + 0 = 5.

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 +53

Freshsales API 27

No OpenAPI or other machine-readable spec found (0). No llms.txt or Markdown docs (0). One long HTML reference page with short endpoint descriptions and no when-not-to-use guidance (8 of 20). Field tables and filter bodies, with free-form filter JSON for views and search (8 of 15). curl examples throughout, an error format of errors.code and errors.message and a list of status codes (11 of 15). No version scheme or API changelog found (0).

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

Reliability Pipedrive API + MCP +22

Freshsales API 36

Freshworks runs its own status page at status.freshworks.com across products and regions, but it renders only with JavaScript and its components were never read in a way this run uses (the 1 October incidents API answer is struck), so no Freshsales component counts (0; freshdesk, same page, 4 November). No readable incident history (5). 1,000 API requests an hour per account, published (15). 429 is documented ("exceeded the API limit set per hour per account"), with no Retry-After or backoff guidance. Contact upsert and bulk upsert make creates safe to retry (6 of 15, an earlier partial held). No SLA found on the pricing page (0). The REST API is GA (10). 0 + 5 + 15 + 6 + 0 + 10 = 36.

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

Agent ergonomics Pipedrive API + MCP +13

Freshsales API 48

No MCP server for Freshsales. include embeds related records on request and lists default to 25 per page. No field selection to trim responses (10 of 25). page pagination, filtered views, search and filter endpoints (14 of 20). Errors carry a code and a message, with status codes documented (12 of 20). /api/contacts/upsert and bulk_upsert (100 records a request) give idempotent creates for contacts, but nothing similar for deals. bulk_destroy deletes in bulk (8 of 20). Every account has its own host, so an agent needs the bundle alias as well as the key, and there's no official SDK (4 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).

Security & auth Pipedrive API + MCP +9

Freshsales API 44

One per-user API key in Authorization: Token token=<key>, limited by that user's role and visibility. No scopes, no OAuth for the CRM API, and we found no rotation docs (13 of 30). No read-only key. Access is whatever the user's role allows, and bulk delete endpoints exist (3 of 20). Records carry email, notes and chat text from outside parties, and we found no injection guidance (3 of 15). Audit logs listed on the Enterprise plan (8 of 15). HackerOne disclosure programme, a security.txt with contact and policy (no Expires field), and ISO, AICPA and Cyber Essentials Plus logos on the security page (17 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

CategoryWeightFreshsales APIPipedrive API + MCPEdge
Reliability16%3658Pipedrive API + MCP +22
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%2780Pipedrive API + MCP +53
Agent ergonomics13%4861Pipedrive API + MCP +13
Security & auth14%4453Pipedrive API + MCP +9
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%583Pipedrive API + MCP +78
Transparency & trust7%7376Pipedrive API + MCP +3
Negative events≤1500
TotalE 39.5/100B 63.3/100

Facts side by side

FactFreshsales APIPipedrive API + MCP
KindHTTP APIHTTP API
VendorFreshworksPipedrive
Hosted endpointno (local only)https://api.pipedrive.com/api/v2
TransportsHTTPHTTP, Streamable HTTP
AuthAPI keyOAuth or key
PricingPaidPaid
x402nono
Read-only variant documentednono
llms.txtnoyes
Last releasenone2026-10-21
Terms last updated2026-04-012026-09-16
Privacy policy last updatedno date given2026-07-02
Customer content may train modelsyes, with an opt-outnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waiveryesyes
Popularitynone234 stars, 72k npm/wk
Agent reviews2/5 (2)2.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Pipedrive API + MCP higher.

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

Freshsales API

Contact upsert and bulk upsert of up to 100 records make creates safe to retry. No MCP server for Freshsales.

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

Freshsales API

  1. Build the base URL from the bundle alias shown under the API key, https://<alias>.myfreshworks.com/crm/sales/api/
  2. Use /api/contacts/upsert rather than create, so a retry updates instead of duplicating
  3. Budget calls, since 1,000 an hour covers the whole account and 429s carry no Retry-After
  4. Add include=owner,sales_accounts to pull related records in one call
  5. Expect to see only what the key owner's role can see

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

Questions

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

Pipedrive API + MCP scores 63.3 (B) on agent readiness against Freshsales API's 39.5 (E), and leads in 6 of 7 scored categories.

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

Freshsales API needs an API key. Pipedrive API + MCP takes an API key or an OAuth sign-in.

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

No hosted endpoint is listed for Freshsales API. Pipedrive API + MCP has a hosted endpoint at https://api.pipedrive.com/api/v2.

Other comparisons with Freshsales API or Pipedrive 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.