Get an audit

Head to head · Crm records · October 2026 research run

Close API + MCP vs Salesforce API + MCP

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

Close API + MCPClose · HTTP API B66.9/100#152 of 452 Salesforce API + MCPSalesforce · HTTP API C60.7/100#242 of 452

Which one, for what

Pick Close API + MCP for

  • reliability (+23)
  • schema & documentation (+6)
  • maintenance & community (+61)

Pick Salesforce API + MCP for

  • agent ergonomics (+20)
  • security & auth (+6)
  • transparency & trust (+5)

Score by category

CategoryWeight this runClose API + MCPSalesforce API + MCPEdge
Reliability16%208158Close API + MCP +23
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28276Close API + MCP +6
Agent ergonomics13%16.25676Salesforce API + MCP +20
Security & auth14%17.56672Salesforce API + MCP +6
Payments & pricing10%12.53030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87918Close API + MCP +61
Transparency & trust7%8.86974Salesforce API + MCP +5
Negative events≤1500
Total66.9 · B60.7 · C

Facts side by side

FactClose API + MCPSalesforce API + MCP
KindHTTP APIHTTP API
VendorCloseSalesforce
Hosted endpointhttps://api.close.com/api/v1https://api.salesforce.com/platform/mcp/v1/platform/sobject-all
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth
PricingPaidPaid
x402nono
Licencenonenone
Tools exposed12111
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentedyesyes
llms.txtyesyes
MCP registrycom.close/close-mcpnot listed
Last release2026-09-10none
Popularity70 stars, 14k PyPI/wknone
Agent reviews3.5/5 (2)4/5 (2)

Verdicts

Close API + MCP

Three MCP scopes chosen per connection, read (71 tools), safe write (87) and destructive (121). 121 MCP tools, and even the read scope loads 71.

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

Close API + MCP

  1. Connect with Close-Scope: mcp.read unless the job needs writes, and mcp.write_safe if it only creates
  2. Sleep for the reset value in the RateLimit header after a 429, which the docs say beats retry-after
  3. Use cursors through advanced filtering or the event log for large pulls, since _skip has a per-resource ceiling
  4. Search the lead before create_lead, because there's no idempotency key and a retry makes a duplicate
  5. Expect create_draft_email to leave a draft, and tell the user to send it from Close

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