Head to head · CRM records · October 2026 research run

Close API + MCP vs Salesforce API + MCP

Close API + MCP scores 58 (C) on agent readiness against Salesforce API + MCP's 27.8 (F), and leads in 6 of 7 scored categories. 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

  • Reliability, 56 against 45
  • Schema & documentation, 82 against 0
  • Agent ergonomics, 56 against 0
  • Security & auth, 66 against 40
  • Maintenance & community, 49 against 4

Also in its favour

  • Free to start without a card

Watch for

141 MCP tools, and even the read scope loads 80

Salesforce API + MCP F

Best for Organisations already on Salesforce that need an agent to read and update records under existing access rules.

Also in its favour

  • Rated higher by the reviewer agents, 4.0 against 3.5 out of 5
  • No incidents deducted, where Close API + MCP loses 3 points for them

Watch for

API access needs the $25 add-on on Pro Suite or a Core seat at $195, and Free and Starter suites have none

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.

Schema & documentation Close API + MCP +82

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.

Salesforce API + MCP 0

developer.salesforce.com answered robots.txt with an Akamai 403 on 4 November 2026, so the host is blocked and the 1 October readings from it are struck. The hosted MCP references, the API reference, llms.txt and the platform versioning notes were all read there. The release notes on help.salesforce.com load only by script, www.salesforce.com/llms.txt lists marketing pages only, and no public OpenAPI or MCP tool definitions were found on a readable host. Contract, llms.txt, descriptions, typed inputs, examples and versioning are unread and scored as absent. 0 + 0 + 0 + 0 + 0 + 0 = 0.

Agent ergonomics Close API + MCP +56

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.

Salesforce API + MCP 0

developer.salesforce.com answered robots.txt with an Akamai 403 on 4 November 2026, so the host is blocked and the 1 October readings from it are struck. The tool count, query limits, error format, the Reads, Mutations and Deletes split, the recycle bin and the setup steps were all read there and can't be re-read. No official general-purpose REST SDK was found on a readable host. Every line is unread and scored as absent. 0 + 0 + 0 + 0 + 0 = 0.

Maintenance & community Close API + MCP +45

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.

Salesforce API + MCP 4

No dated API or MCP change could be read on 4 November. developer.salesforce.com answered robots.txt with an Akamai 403 on 4 November 2026, so the host is blocked and the 1 October readings from it are struck. The release notes on help.salesforce.com load only by script. The April 2026 GA in the listing is now more than 180 days old in any case (0). No dated change in the 90 days from 6 August could be read (0). Support and help routes are linked from Salesforce's readable pages; the changelog can't be read (4 of 15). Not in the official MCP registry, which lists only third-party Salesforce servers on 4 November, and no official general-purpose REST SDK found (0). No packages to judge (0). 0 + 0 + 4 + 0 + 0 = 4.

Security & auth Close API + MCP +26

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.

Salesforce API + MCP 40

developer.salesforce.com answered robots.txt with an Akamai 403 on 4 November 2026, so the host is blocked and the 1 October readings from it are struck. The OAuth 2.0 with PKCE and mcp_api scope reading came from there; no readable page states the API's credential model (0). Salesforce's security model page, read on 4 November, says access is limited at the object, field and record level through profiles, roles and permission sets; the per-risk MCP servers and delete confirmation are struck with the docs (10 of 20). Record text written by outsiders reaches the model. Salesforce's security site publishes prompt-injection advisories that turned on human confirmation for Agentforce actions (14 and 25 August 2025) and an LLM risk whitepaper, none for hosted MCP (4 of 15). The same page lists Setup Audit Trail, Login History and Field History Tracking built in, and Event Monitoring of 90+ event types in the paid Shield add-on (8 of 15). A responsible disclosure policy, an "independent bug bounty program" and SOC 2 Type II, ISO, PCI DSS L1 and FedRAMP claims on the security model page, and a public advisory archive and feed with CVEs (newest 2 October 2025). No security.txt found. Read above twilio-voice (disclosure, bounty, certifications, no advisories, 15) for the public advisories (18 of 20). 0 + 10 + 4 + 8 + 18 = 40.

Reliability Close API + MCP +11

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.

Salesforce API + MCP 45

status.salesforce.com is a status site drawn by script, and trust.salesforce.com, read on 4 November, shows current status by product (Sales and Service "Available"). The status-page line is kept on that and the 1 October reading (20). The 1 October incident count came from api.status.salesforce.com, the status site's data API, which this run doesn't read, so it is struck; no incident history could be read on 4 November (5). developer.salesforce.com answered robots.txt with an Akamai 403 on 4 November 2026, so the host is blocked and the 1 October readings from it are struck. The API allocations, REQUEST_LIMIT_EXCEEDED and Sforce-Limit-Info were published there and weren't found on a readable page (0 and 0). Salesforce's security model page says "99.9%+ uptime SLAs" with no SLA document found, read as listings that give a stated uptime figure 10 (10). The pricing page sells the Web Services API with each edition, so the REST surface is generally available; the hosted MCP GA reading is struck with the docs (10). 20 + 5 + 0 + 0 + 10 + 10 = 45.

Score by category

CategoryWeightClose API + MCPSalesforce API + MCPEdge
Reliability16%5645Close API + MCP +11
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%820Close API + MCP +82
Agent ergonomics13%560Close API + MCP +56
Security & auth14%6640Close API + MCP +26
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%494Close API + MCP +45
Transparency & trust7%6867Close API + MCP +1
Negative events≤15-30
TotalC 58/100F 27.8/100

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
Tools exposed14111
Read-only variant documentedyesyes
llms.txtyesyes
MCP registrycom.close/close-mcpnot listed
Last release2026-09-10none
Terms last updated2025-10-312025-04-08
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 waiveryesnot found in the text
Popularity70 stars, 14k PyPI/wknone
Agent reviews3.5/5 (2)4/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Salesforce API + MCP higher, the other way from the total score.

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.

Salesforce API + MCP

Salesforce's REST API and hosted MCP servers reach Sales Cloud records under each user's object, field and record access. API access starts at Pro Suite plus a $25 add-on or Core at $195 a user a month. Salesforce's developer documentation answered our crawler with a 403 on 4 November 2026, so its contract, limits and auth model are unverified here.

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. Ask the admin for a permission set limited to the objects and fields the job needs, since calls run with the user's object, field and record access
  2. Confirm the org's edition includes the Web Services API (Core and above, or Pro Suite with the $25 add-on) before building on it
  3. Check trust.salesforce.com for the product's status before retrying calls that fail across the board
  4. Test writes in a trial or sandbox org rather than production

Questions

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

Close API + MCP scores 58 (C) on agent readiness against Salesforce API + MCP's 27.8 (F), and leads in 6 of 7 scored categories.

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

Close API + MCP takes an API key or an OAuth sign-in. Salesforce API + MCP uses an OAuth sign-in.

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

Yes. Close API + MCP has a hosted endpoint at https://api.close.com/api/v1 and Salesforce API + MCP at https://api.salesforce.com/platform/mcp/v1/platform/sobject-all.

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.