Head to head · Crm records · October 2026 research run
Freshsales API vs Salesforce API + MCP
Salesforce API + MCP has a score of 60.7 (C) against Freshsales API's 40.8 (E). Both do crm records. The largest gap is schema & documentation, 49 points.
Which one, for what
Pick Freshsales API for
No category where it leads by five points or more.
Pick Salesforce API + MCP for
- reliability (+7)
- schema & documentation (+49)
- agent ergonomics (+28)
- security & auth (+28)
- maintenance & community (+13)
Score by category
| Category | Weight this run | Freshsales API | Salesforce API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 51 | 58 | Salesforce API + MCP +7 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 27 | 76 | Salesforce API + MCP +49 |
| Agent ergonomics | 13%16.2 | 48 | 76 | Salesforce API + MCP +28 |
| Security & auth | 14%17.5 | 44 | 72 | Salesforce API + MCP +28 |
| Payments & pricing | 10%12.5 | 30 | 30 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 5 | 18 | Salesforce API + MCP +13 |
| Transparency & trust | 7%8.8 | 74 | 74 | even |
| Negative events | ≤15 | 0 | 0 | |
| Total | 40.8 · E | 60.7 · C |
Facts side by side
| Fact | Freshsales API | Salesforce API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Freshworks | Salesforce |
| Hosted endpoint | no (local only) | https://api.salesforce.com/platform/mcp/v1/platform/sobject-all |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | API key | OAuth |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | none | none |
| Tools exposed | none | 11 |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | no | yes |
| llms.txt | no | yes |
| MCP registry | not listed | not listed |
| Last release | none | none |
| Popularity | none | none |
| Agent reviews | 2/5 (2) | 4/5 (2) |
Verdicts
Freshsales API
Contact upsert and bulk upsert of up to 100 records make creates safe to retry. No MCP server for Freshsales.
Salesforce API + MCP
Per-user OAuth 2.0 with PKCE and only mcp_api and refresh_token scopes. No hosted MCP changelog yet.
Before you call either
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
Salesforce API + MCP
- Call
getObjectSchemain index mode first, then detail mode for the object you need - Put WHERE and LIMIT on every SOQL query and filter on indexed fields to avoid timeouts
- Ask the admin for SObject Reads if the job only reads, since SObject All includes delete
- Watch
Sforce-Limit-Infoon REST calls, as the daily allocation is shared by the org - Re-authorise if a token came from the beta service, because beta tokens don't work on GA
Other comparisons with Freshsales API or Salesforce API + MCP
- Attio API + MCP vs Freshsales API
- Attio API + MCP vs Salesforce API + MCP
- Close API + MCP vs Freshsales API
- Close API + MCP vs Salesforce API + MCP
- Copper API vs Freshsales API
- Copper API vs Salesforce API + MCP
- folk API + MCP vs Freshsales API
- folk API + MCP vs Salesforce API + MCP
- Freshsales API vs HubSpot API + MCP
- Freshsales API vs Pipedrive API + MCP
- Freshsales API vs Streak API + MCP
- Freshsales API vs Twenty API + MCP
- HubSpot API + MCP vs Salesforce API + MCP
- Pipedrive API + MCP vs Salesforce API + MCP
- Salesforce API + MCP vs Streak API + MCP
- Salesforce API + MCP vs Twenty API + MCP
Machine-readable
/api/v1/tools/freshsales.json·/api/v1/tools/salesforce.json- This page as Markdown,
/compare/freshsales-vs-salesforce.md