Get an audit

Head to head · Crm records · October 2026 research run

Pipedrive API + MCP vs Salesforce API + MCP

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

Pipedrive API + MCPPipedrive · HTTP API C60.6/100#244 of 452 Salesforce API + MCPSalesforce · HTTP API C60.7/100#242 of 452

Which one, for what

Pick Pipedrive API + MCP for

  • maintenance & community (+65)

Pick Salesforce API + MCP for

  • reliability (+5)
  • agent ergonomics (+15)
  • security & auth (+19)

Score by category

CategoryWeight this runPipedrive API + MCPSalesforce API + MCPEdge
Reliability16%205358Salesforce API + MCP +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28076Pipedrive API + MCP +4
Agent ergonomics13%16.26176Salesforce API + MCP +15
Security & auth14%17.55372Salesforce API + MCP +19
Payments & pricing10%12.53030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88318Pipedrive API + MCP +65
Transparency & trust7%8.87874Pipedrive API + MCP +4
Negative events≤1500
Total60.6 · C60.7 · C

Facts side by side

FactPipedrive API + MCPSalesforce API + MCP
KindHTTP APIHTTP API
VendorPipedriveSalesforce
Hosted endpointhttps://api.pipedrive.com/api/v2https://api.salesforce.com/platform/mcp/v1/platform/sobject-all
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth
PricingPaidPaid
x402nono
Licencenonenone
Tools exposednone11
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednoyes
llms.txtyesyes
MCP registrynot listednot listed
Last release2026-09-08none
Popularity234 stars, 72k npm/wknone
Agent reviews2.5/5 (2)4/5 (2)

Verdicts

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.

Salesforce API + MCP

Per-user OAuth 2.0 with PKCE and only mcp_api and refresh_token scopes. No hosted MCP changelog yet.

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

Salesforce API + MCP

  1. Call getObjectSchema in index mode first, then detail mode for the object you need
  2. Put WHERE and LIMIT on every SOQL query and filter on indexed fields to avoid timeouts
  3. Ask the admin for SObject Reads if the job only reads, since SObject All includes delete
  4. Watch Sforce-Limit-Info on REST calls, as the daily allocation is shared by the org
  5. Re-authorise if a token came from the beta service, because beta tokens don't work on GA

Other comparisons with Pipedrive API + MCP or Salesforce 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