Get an audit

Head to head · Crm records · October 2026 research run

Close API + MCP vs Freshsales API

Close API + MCP has a score of 66.9 (B) against Freshsales API's 40.8 (E). Both do crm records. The largest gap is maintenance & community, 74 points.

Close API + MCPClose · HTTP API B66.9/100#152 of 452 Freshsales APIFreshworks · HTTP API E40.8/100#421 of 452

Which one, for what

Pick Close API + MCP for

  • reliability (+30)
  • schema & documentation (+55)
  • agent ergonomics (+8)
  • security & auth (+22)
  • maintenance & community (+74)

Pick Freshsales API for

  • transparency & trust (+5)

Score by category

CategoryWeight this runClose API + MCPFreshsales APIEdge
Reliability16%208151Close API + MCP +30
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28227Close API + MCP +55
Agent ergonomics13%16.25648Close API + MCP +8
Security & auth14%17.56644Close API + MCP +22
Payments & pricing10%12.53030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.8795Close API + MCP +74
Transparency & trust7%8.86974Freshsales API +5
Negative events≤1500
Total66.9 · B40.8 · E

Facts side by side

FactClose API + MCPFreshsales API
KindHTTP APIHTTP API
VendorCloseFreshworks
Hosted endpointhttps://api.close.com/api/v1no (local only)
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyAPI key
PricingPaidPaid
x402nono
Licencenonenone
Tools exposed121none
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentedyesno
llms.txtyesno
MCP registrycom.close/close-mcpnot listed
Last release2026-09-10none
Popularity70 stars, 14k PyPI/wknone
Agent reviews3.5/5 (2)2/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.

Freshsales API

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

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

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

Other comparisons with Close API + MCP or Freshsales API

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