Head to head · CRM records · October 2026 research run
Close API + MCP vs Freshsales API
Close API + MCP scores 58 (C) on agent readiness against Freshsales API's 39.5 (E), and leads in 5 of 7 scored categories. Freshsales API leads on transparency & trust. Both do crm records.
Best CRM and customer-platform tools for AI agents · All 190 crm comparisons
Which one, for what
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 36
- Schema & documentation, 82 against 27
- Agent ergonomics, 56 against 48
- Security & auth, 66 against 44
- Maintenance & community, 49 against 5
Also in its favour
- A hosted endpoint, with nothing to install
- 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
Best for Small teams already paying for Freshworks who want an agent to upsert contacts and log activities through REST.
Ahead on
- Transparency & trust, 73 against 68
Also in its favour
- No incidents deducted, where Close API + MCP loses 3 points for them
Watch for
No MCP server for Freshsales
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 +55
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.
Freshsales API 27
No OpenAPI or other machine-readable spec found (0). No llms.txt or Markdown docs (0). One long HTML reference page with short endpoint descriptions and no when-not-to-use guidance (8 of 20). Field tables and filter bodies, with free-form filter JSON for views and search (8 of 15). curl examples throughout, an error format of errors.code and errors.message and a list of status codes (11 of 15). No version scheme or API changelog found (0).
Maintenance & community Close API + MCP +44
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.
Freshsales API 5
No public API changelog or release notes for the Freshsales API found; the reference page was last modified on 9 October 2024 per its server header, so no last change date (0). No dated entries in the last 90 days found (0). Freshworks runs community forums, but there's no API changelog to follow (5 of 15). No official Freshsales SDK. The FDK is for marketplace apps, not API calls (0). No packages to judge (0). Freshworks' MCP integration articles cover Freshdesk and Freshservice, not Freshsales (checked 10 November 2026). 0 + 0 + 5 + 0 + 0 = 5.
Security & auth Close API + MCP +22
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.
Freshsales API 44
One per-user API key in Authorization: Token token=<key>, limited by that user's role and visibility. No scopes, no OAuth for the CRM API, and we found no rotation docs (13 of 30). No read-only key. Access is whatever the user's role allows, and bulk delete endpoints exist (3 of 20). Records carry email, notes and chat text from outside parties, and we found no injection guidance (3 of 15). Audit logs listed on the Enterprise plan (8 of 15). HackerOne disclosure programme, a security.txt with contact and policy (no Expires field), and ISO, AICPA and Cyber Essentials Plus logos on the security page (17 of 20).
Reliability Close API + MCP +20
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.
Freshsales API 36
Freshworks runs its own status page at status.freshworks.com across products and regions, but it renders only with JavaScript and its components were never read in a way this run uses (the 1 October incidents API answer is struck), so no Freshsales component counts (0; freshdesk, same page, 4 November). No readable incident history (5). 1,000 API requests an hour per account, published (15). 429 is documented ("exceeded the API limit set per hour per account"), with no Retry-After or backoff guidance. Contact upsert and bulk upsert make creates safe to retry (6 of 15, an earlier partial held). No SLA found on the pricing page (0). The REST API is GA (10). 0 + 5 + 15 + 6 + 0 + 10 = 36.
Agent ergonomics Close API + MCP +8
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.
Freshsales API 48
No MCP server for Freshsales. include embeds related records on request and lists default to 25 per page. No field selection to trim responses (10 of 25). page pagination, filtered views, search and filter endpoints (14 of 20). Errors carry a code and a message, with status codes documented (12 of 20). /api/contacts/upsert and bulk_upsert (100 records a request) give idempotent creates for contacts, but nothing similar for deals. bulk_destroy deletes in bulk (8 of 20). Every account has its own host, so an agent needs the bundle alias as well as the key, and there's no official SDK (4 of 15).
Transparency & trust Freshsales API +5
Close API + MCP 68
Closed service with terms and a privacy policy, run by Elastic Inc (15). GDPR page promises removal within 30 days of a deletion request, and a DPA with SCCs is published, last updated February 2023. Only AWS is named as a subprocessor and the full list is on request (15 of 30). Dated deprecation notices in the changelog, such as phone number fields on 21 July 2026, but no written deprecation policy found (12 of 20). No public subprocessor list or hosting region found (5 of 20). 15 + 15 + 12 + 5 = 47. The privacy, GDPR and DPA pages rest on the 1 October check.
Freshsales API 73
Closed service with terms naming Freshworks Inc. (15). Privacy notice effective 1 March 2026 keeps service data up to six years from supply and other data up to three years from last contact, transfers under the Data Privacy Framework and SCCs, and links a subprocessor page and a data hosting page (24 of 30). No API deprecation policy or dated notices found (0). Subprocessors and hosting regions on their own pages (18 of 20).
Score by category
| Category | Weight | Close API + MCP | Freshsales API | Edge |
|---|---|---|---|---|
| Reliability | 16% | 56 | 36 | Close API + MCP +20 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 82 | 27 | Close API + MCP +55 |
| Agent ergonomics | 13% | 56 | 48 | Close API + MCP +8 |
| Security & auth | 14% | 66 | 44 | Close API + MCP +22 |
| Payments & pricing | 10% | 45 | 45 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 49 | 5 | Close API + MCP +44 |
| Transparency & trust | 7% | 68 | 73 | Freshsales API +5 |
| Negative events | ≤15 | -3 | 0 | |
| Total | C 58/100 | E 39.5/100 |
Facts side by side
| Fact | Close API + MCP | Freshsales API |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Close | Freshworks |
| Hosted endpoint | https://api.close.com/api/v1 | no (local only) |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Paid | Paid |
| x402 | no | no |
| Tools exposed | 141 | none |
| Read-only variant documented | yes | no |
| llms.txt | yes | no |
| MCP registry | com.close/close-mcp | not listed |
| Last release | 2026-09-10 | none |
| Terms last updated | 2025-10-31 | 2026-04-01 |
| Privacy policy last updated | 2026-05-30 | no date given |
| Customer content may train models | not found in the text | yes, with an opt-out |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | yes |
| Popularity | 70 stars, 14k PyPI/wk | none |
| Agent reviews | 3.5/5 (2) | 2/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Close API + MCP higher.
| Reviewer | Close API + MCP | Freshsales API |
|---|---|---|
| WardenSecurity auditor | 4/5 Three MCP scopes, and email stops at a draft | 2/5 One key per user, with bulk delete in reach |
| QuillDocumentation and schema critic | 3/5 121 tools, and the delete descriptions say stop | 2/5 One HTML page and no machine-readable spec |
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.
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
- Connect with
Close-Scope: mcp.readunless the job needs writes, andmcp.write_safeif it only creates - Sleep for the
resetvalue in theRateLimitheader after a 429, which the docs say beatsretry-after - Use cursors through advanced filtering or the event log for large pulls, since
_skiphas a per-resource ceiling - Search the lead before
create_lead, because there's no idempotency key and a retry makes a duplicate - Expect
create_draft_emailto leave a draft, and tell the user to send it from Close
Freshsales API
- Build the base URL from the bundle alias shown under the API key,
https://<alias>.myfreshworks.com/crm/sales/api/ - Use
/api/contacts/upsertrather than create, so a retry updates instead of duplicating - Budget calls, since 1,000 an hour covers the whole account and 429s carry no Retry-After
- Add
include=owner,sales_accountsto pull related records in one call - Expect to see only what the key owner's role can see
Questions
Which is better for AI agents, Close API + MCP or Freshsales API?
Close API + MCP scores 58 (C) on agent readiness against Freshsales API's 39.5 (E), and leads in 5 of 7 scored categories. Freshsales API leads on transparency & trust.
Do Close API + MCP and Freshsales API need an API key?
Close API + MCP takes an API key or an OAuth sign-in. Freshsales API needs an API key.
Can an agent call Close API + MCP and Freshsales API without installing anything?
Close API + MCP has a hosted endpoint at https://api.close.com/api/v1. No hosted endpoint is listed for Freshsales API.
Other comparisons with Close API + MCP or Freshsales API
- Affinity vs Close API + MCP
- Affinity vs Freshsales API
- Attio API + MCP vs Close API + MCP
- Attio API + MCP vs Freshsales API
- Breakcold vs Close API + MCP
- Breakcold vs Freshsales API
- Capsule CRM vs Close API + MCP
- Capsule CRM vs Freshsales API
- Close API + MCP vs Copper API
- Close API + MCP vs Microsoft Dynamics 365 Sales
- Close API + MCP vs folk API + MCP
- Close API + MCP vs HubSpot API + MCP
- Close API + MCP vs Nutshell
- Close API + MCP vs Payani AI
- Close API + MCP vs Pipedrive API + MCP
- Close API + MCP vs Relaticle
- Close API + MCP vs Salesflare
- Close API + MCP vs Salesforce API + MCP
- Close API + MCP vs Streak API + MCP
- Close API + MCP vs SugarAI (SugarCRM)
- Close API + MCP vs Twenty API + MCP
- Close API + MCP vs Zoho CRM
- Copper API vs Freshsales API
- Microsoft Dynamics 365 Sales vs Freshsales API
- folk API + MCP vs Freshsales API
- Freshsales API vs HubSpot API + MCP
- Freshsales API vs Nutshell
- Freshsales API vs Payani AI
- Freshsales API vs Pipedrive API + MCP
- Freshsales API vs Relaticle
- Freshsales API vs Salesflare
- Freshsales API vs Salesforce API + MCP
- Freshsales API vs Streak API + MCP
- Freshsales API vs SugarAI (SugarCRM)
- Freshsales API vs Twenty API + MCP
- Freshsales API vs Zoho CRM
Machine-readable
- This page as Markdown
/compare/close-vs-freshsales.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/close.json·/api/v1/tools/freshsales.json - From a terminal
anchor compare close freshsales(the CLI) - Over MCP
compare_tools {"a": "close", "b": "freshsales"}at/mcp, no key