Get an audit

Head to head · Crm records · October 2026 research run

Close API + MCP vs Streak API + MCP

Close API + MCP has a score of 66.9 (B) against Streak API + MCP's 46.5 (D). Both do crm records. The largest gap is schema & documentation, 47 points.

Close API + MCPClose · HTTP API B66.9/100#152 of 452 Streak API + MCPStreak · HTTP API D46.5/100#395 of 452

Which one, for what

Pick Close API + MCP for

  • reliability (+13)
  • schema & documentation (+47)
  • agent ergonomics (+28)
  • security & auth (+14)
  • payments & pricing (+10)
  • maintenance & community (+19)

Pick Streak API + MCP for

No category where it leads by five points or more.

Score by category

CategoryWeight this runClose API + MCPStreak API + MCPEdge
Reliability16%208168Close API + MCP +13
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28235Close API + MCP +47
Agent ergonomics13%16.25628Close API + MCP +28
Security & auth14%17.56652Close API + MCP +14
Payments & pricing10%12.53020Close API + MCP +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87960Close API + MCP +19
Transparency & trust7%8.86966Close API + MCP +3
Negative events≤1500
Total66.9 · B46.5 · D

Facts side by side

FactClose API + MCPStreak API + MCP
KindHTTP APIHTTP API
VendorCloseStreak
Hosted endpointhttps://api.close.com/api/v1https://api.streak.com/api/v1
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or 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.txtyesyes
MCP registrycom.close/close-mcpnot listed
Last release2026-09-102026-09-16
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.

Streak API + MCP

MCP server is OAuth only and revocable from account settings. MCP tool list and count not published.

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

Streak API + MCP

  1. Keep under 10 requests a second, or tell Streak first, since there's no published hard limit
  2. Expect no email bodies through MCP and fetch thread context through Gmail instead
  3. Send the API key as the Basic auth username with an empty password
  4. Check the plan before relying on webhooks, which start at Pro+
  5. Handle a 410 as an API version that's no longer supported

Other comparisons with Close API + MCP or Streak 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