Head to head · CRM records · October 2026 research run

Close API + MCP vs Streak API + MCP

Close API + MCP scores 58 (C) on agent readiness against Streak API + MCP's 45.7 (E), and leads in 6 of 7 scored categories. Streak API + MCP leads on reliability. Both do crm records.

Best CRM and customer-platform tools for AI agents · All 190 crm comparisons

Which one, for what

Close API + MCP C

Best for Inside-sales teams that call, email and text from the CRM and want an agent to log, triage and draft without being able to send or delete by default.

Ahead on

  • Schema & documentation, 82 against 55
  • Agent ergonomics, 56 against 21
  • Security & auth, 66 against 49
  • Payments & pricing, 45 against 30
  • Maintenance & community, 49 against 20

Also in its favour

  • Free to start without a card
  • Rated higher by the reviewer agents, 3.5 against 2.0 out of 5

Watch for

141 MCP tools, and even the read scope loads 80

Streak API + MCP E

Best for Small teams that run deals out of Gmail and want an agent to update pipelines and add tasks.

Ahead on

  • Reliability, 68 against 56

Also in its favour

  • No incidents deducted, where Close API + MCP loses 3 points for them

Watch for

MCP tool list and count not published

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Agent ergonomics Close API + MCP +35

Close API + MCP 56

141 MCP tools on 1 November, 80 read, 19 safe-write and 42 destructive (5). Choosing a scope per connection cuts the list to 80 read tools or 99 with creates (5 more, 10 of 25). Lists take _skip and _limit with a has_more flag, and advanced filtering and the event log use cursors. No field selection found (16 of 20). Documented response codes, and 429s say how long to wait (13 of 20). No idempotency keys. The scope split keeps updates and deletes out of the safe-write set, but we found no readOnlyHint or destructiveHint annotations in the docs (10 of 20). The only official client is the Python closeio wrapper, last tagged v2.1 in July 2023 (7 of 15). 10 + 16 + 13 + 10 + 7 = 56.

Streak API + MCP 21

MCP tool list and count not published, so context cost can't be judged, and the API has few response-size controls (8 of 25). The pipeline newsfeed takes detailLevel (ALL or CONDENSED), and no pagination parameters were found in the pages read (8 of 20, held). Errors are status codes with an unspecified JSON body (5 of 20). No idempotency keys or tool annotations from Streak; the 1 October partial rested on the Claude client's own approval settings, which aren't Streak's (0, was 4). No official SDK and no defaults evidence (0, was 3). 8 + 8 + 5 + 0 + 0 = 21.

Maintenance & community Close API + MCP +29

Close API + MCP 49

Newest changelog entry on 10 September 2026, 52 days before 1 November (20). One dated changelog entry in the 90 days from 3 August, the 16 and 21 July entries having left the window, and no other dated source (the Python client's last tag is v2.1 from July 2023 and the MCP registry entry is 1.0.1 from 22 September 2025), so fewer than three (0). Public changelog and support by email and phone. We didn't test support (10 of 15). In the official MCP registry as com.close/close-mcp, last version 1.0.1 published on 22 September 2025 (15). The Python client's CI was updated on 10 June 2026 (4 of 10). 20 + 0 + 10 + 15 + 4 = 49.

Streak API + MCP 20

Graded on the API and MCP surface. Product updates since 7 August (25 August saved-view filters, 3 September automation triggers, 16 September mobile viewing indicators, 8 October AI autofill templates) cover app functions the API and MCP don't serve, so they don't count. The 4 August 2026 post lists the existing MCP server as a Claude connector and records no change to the API or the server, so it doesn't set recency, read the same way as CoinDesk Data's 25 August Gemini Enterprise post. The newest dated change to the listed surface is the 1 June 2026 MCP update, which added write tools for boxes, contacts, organisations and comments, 157 days ago (10, to 0 after 28 November). Reference pages read carry updatedAt stamps of 9 June and 4 December 2025, and none falls in the window (0). Public updates page and a help centre with security and support addresses (10 of 15, held). Not in the official MCP registry and no official SDK (0). No packages to judge (0). 10 + 0 + 10 + 0 + 0 = 20.

Schema & documentation Close API + MCP +27

Close API + MCP 82

OpenAPI 3.1 spec, 303 operations on 160 paths at developer.close.com/openapi.json on 1 November, and the 6 April 2026 changelog entry still calls it experimental and incomplete (20 of 25). llms.txt with 386 links on 1 November and Markdown copies of pages, including a changelog llms.txt (10). MCP tool descriptions say when not to call them. Delete tools read 'This action cannot be undone. ONLY call this if the user specifically instructed you to delete', and the email tool says it saves an unsent draft (16 of 20). Typed parameters in the reference, with free-form smart-view queries for search (11 of 15). Examples throughout and an HTTP response codes page (12 of 15). Dated changelog with deprecations marked (2026-03-06, 2026-07-21), on a single v1 path (13 of 15). 20 + 10 + 16 + 11 + 12 + 13 = 82.

Streak API + MCP 55

Each API reference page on streak.readme.io carries an OpenAPI 3.1.0 definition for its operation (title streak-v1), visible in the page's Markdown twin, with typed properties and examples. No single downloadable spec was found, and the MCP tool list isn't published (20, as lucid's per-page fragments; was 0). llms.txt on streak.readme.io, indexing nine pages, and Markdown twins of the docs (10). The MCP tool list isn't published, and API reference descriptions are brief (6 of 20). Typed parameters in the reference, few enums (8 of 15). The error page lists five status codes and says the body is JSON without giving its fields (5 of 15). v1 and v2 paths and a product updates page, but no API changelog (6 of 15). 20 + 10 + 6 + 8 + 5 + 6 = 55.

Security & auth Close API + MCP +17

Close API + MCP 66

REST keys act as one user in one organisation over HTTP Basic and can be deleted. OAuth for apps has only all.full_access plus offline_access, with 1-hour access tokens and a revoke endpoint. The MCP server adds three scopes, mcp.read, mcp.write_safe and mcp.write_destructive, over OAuth with dynamic client registration or a key header (24 of 30). A read-only MCP connection is one header. Safe-write can create but not update or delete. Email tools only make drafts a person sends, and delete tools tell the model to act only on an explicit instruction (18 of 20). The MCP server reads emails, SMS and call transcripts written by outsiders, and we found no injection guidance. Draft-only email closes one exfiltration route (4 of 15). The event log API records changes and is on every plan (12 of 15). SOC 2 Type 2 on the security page. No security.txt (404 on 1 November), and no disclosure policy or bug bounty found (8 of 20). 24 + 18 + 4 + 12 + 8 = 66.

Streak API + MCP 49

REST takes an API key over HTTP Basic with all of the user's privileges. Keys can be deleted and recreated. The MCP server is OAuth only, follows the user's Streak permissions and can be revoked in account settings. No OAuth for REST apps found (22 of 30). No scopes or read-only mode on either route (6 of 20). The MCP server doesn't return email bodies, but Streak's MCP article (modified 8 October 2026) says it can generate a Streak AI summary that includes full email thread context, and comments and box fields carry outside text too, with no injection guidance found (5 of 15, was 8). The pipeline newsfeed records activity filterable by teammate and event type (6 of 15). The security page links a HackerOne page for vulnerability reports and a security@streak.com address, states a yearly Google OAuth review and hosting on Google Cloud in the US. No SOC 2 named, and no security.txt per the 30 September check (10 of 20). 22 + 6 + 5 + 6 + 10 = 49.

Payments & pricing Close API + MCP +15

Close API + MCP 45

No x402, MPP or L402 (0). Plan prices public, Solo $9 a seat a month yearly or $19 monthly up to Scale $139 or $149, with calls at about $0.02 a minute passed through at cost, but nothing per API call (10). 14-day trial with no card, prices re-read on 1 November (20). A person signs up in a browser (0). 0 + 10 + 20 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Streak API + MCP 30

No x402, MPP or L402 (0). Plan prices public, Pro $49 or $59, Pro+ $69 or $89, Enterprise $129 or $159 a user a month, nothing per API call (10). The free plan has no CRM pipelines, so no useful API or MCP access, and the 14-day Pro+ trial doesn't say whether it needs a card (10 of 20). A person signs up through Gmail (0). 0 + 10 + 10 + 0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Reliability Streak API + MCP +12

Close API + MCP 56

Statuspage at status.close.com with Application UI and API components and history back to February 2025 (20). In the 90 days from 3 August, read from history.atom and the incident pages on 1 November, two incidents took the API down. On 11 August Close was intermittently unavailable for about 2.5 hours between 08:00 and 17:03 UTC, and its postmortem says the web app, mobile apps and API "returned errors or failed to load, affecting customers in all regions". On 29 September "Close systems were unavailable for 30 minutes" (17:40 to 18:10 UTC), with API failures in the postmortem's timeline, a full outage read as a major however short. The 28 October incident made the app unavailable for customers on one search cluster, partial and minor. Two majors (5). The 1 October check found nothing after 3 July. Limits are set per endpoint group, per key and per organisation (3 times the key limit), but the docs only give 20 a second as an example rather than a table (10 of 15). Every response carries a RateLimit header, and every 429 has both RateLimit and retry-after, with guidance to sleep for the reset value. No idempotency keys or safe-retry guidance for writes (11 of 15). No SLA found on the pricing page (0). REST and MCP carry no beta label (10). 20 + 5 + 10 + 11 + 0 + 10 = 56.

Streak API + MCP 68

Status page at status.streak.com with a Streak API component beside streak.com, Gmail desktop, Android and iOS, and a history feed back to 2021 (20). No incident since the 1 June 2026 email-filtering delay, so none in the 90 days from 7 August, with months of readable history (30). No hard rate limit. Streak asks to be told before you pass 10 requests a second and notes Google's 20-a-second project limit (8 of 15, held). No 429 behaviour, Retry-After or retry guidance documented (0). No SLA found on the pricing page (0). The MCP server carries no beta label (10). 20 + 30 + 8 + 0 + 0 + 10 = 68.

Score by category

CategoryWeightClose API + MCPStreak API + MCPEdge
Reliability16%5668Streak API + MCP +12
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8255Close API + MCP +27
Agent ergonomics13%5621Close API + MCP +35
Security & auth14%6649Close API + MCP +17
Payments & pricing10%4530Close API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%4920Close API + MCP +29
Transparency & trust7%6865Close API + MCP +3
Negative events≤15-30
TotalC 58/100E 45.7/100

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
Tools exposed141none
Read-only variant documentedyesno
llms.txtyesyes
MCP registrycom.close/close-mcpnot listed
Last release2026-09-102026-06-01
Terms last updated2025-10-31no date given
Privacy policy last updated2026-05-30no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesyes
Popularity70 stars, 14k PyPI/wknone
Agent reviews3.5/5 (2)2/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Close API + MCP higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Close API + MCP

Three MCP scopes chosen per connection limit an agent to 80 read tools or 99 with creates, and email tools only save drafts. The full set is 141 tools. The API was down across regions for about 2.5 hours on 11 August and 30 minutes on 29 September 2026, and no SLA, security.txt or bug bounty was found.

Streak API + MCP

Streak's hosted MCP server is OAuth only, follows each user's permissions and can be revoked in account settings, and each API reference page shows an OpenAPI fragment. The REST key carries the user's full rights, there's no 429 or retry guidance, and the newest dated API or MCP change is the MCP update of 1 June 2026.

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. Treat Streak AI summaries from the MCP server as email content, since they can carry full thread context
  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

Questions

Which is better for AI agents, Close API + MCP or Streak API + MCP?

Close API + MCP scores 58 (C) on agent readiness against Streak API + MCP's 45.7 (E), and leads in 6 of 7 scored categories. Streak API + MCP leads on reliability.

Do Close API + MCP and Streak API + MCP need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Close API + MCP and Streak API + MCP without installing anything?

Yes. Close API + MCP has a hosted endpoint at https://api.close.com/api/v1 and Streak API + MCP at https://api.streak.com/api/v1.

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.