Get an audit

Head to head · Crm records · October 2026 research run

Freshsales API vs Pipedrive API + MCP

Pipedrive API + MCP has a score of 60.6 (C) against Freshsales API's 40.8 (E). Both do crm records. The largest gap is maintenance & community, 78 points.

Freshsales APIFreshworks · HTTP API E40.8/100#421 of 452 Pipedrive API + MCPPipedrive · HTTP API C60.6/100#244 of 452

Which one, for what

Pick Freshsales API for

No category where it leads by five points or more.

Pick Pipedrive API + MCP for

  • schema & documentation (+53)
  • agent ergonomics (+13)
  • security & auth (+9)
  • maintenance & community (+78)

Score by category

CategoryWeight this runFreshsales APIPipedrive API + MCPEdge
Reliability16%205153Pipedrive API + MCP +2
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.22780Pipedrive API + MCP +53
Agent ergonomics13%16.24861Pipedrive API + MCP +13
Security & auth14%17.54453Pipedrive API + MCP +9
Payments & pricing10%12.53030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.8583Pipedrive API + MCP +78
Transparency & trust7%8.87478Pipedrive API + MCP +4
Negative events≤1500
Total40.8 · E60.6 · C

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
Licencenonenone
Tools exposednonenone
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtnoyes
MCP registrynot listednot listed
Last releasenone2026-09-08
Popularitynone234 stars, 72k npm/wk
Agent reviews2/5 (2)2.5/5 (2)

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. MCP tool list not published, and the server is labelled beta.

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

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.

Get an auditSee a sample report