Head to head · Crm records · October 2026 research run
Freshsales API vs Streak API + MCP
Streak API + MCP has a score of 46.5 (D) against Freshsales API's 40.8 (E). Both do crm records. The largest gap is maintenance & community, 55 points.
Freshsales APIFreshworks · HTTP API
E40.8/100#421 of 452
Streak API + MCPStreak · HTTP API
D46.5/100#395 of 452
Which one, for what
Pick Freshsales API for
- agent ergonomics (+20)
- payments & pricing (+10)
- transparency & trust (+8)
Pick Streak API + MCP for
- reliability (+17)
- schema & documentation (+8)
- security & auth (+8)
- maintenance & community (+55)
Score by category
| Category | Weight this run | Freshsales API | Streak API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 51 | 68 | Streak API + MCP +17 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 27 | 35 | Streak API + MCP +8 |
| Agent ergonomics | 13%16.2 | 48 | 28 | Freshsales API +20 |
| Security & auth | 14%17.5 | 44 | 52 | Streak API + MCP +8 |
| Payments & pricing | 10%12.5 | 30 | 20 | Freshsales API +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 5 | 60 | Streak API + MCP +55 |
| Transparency & trust | 7%8.8 | 74 | 66 | Freshsales API +8 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 40.8 · E | 46.5 · D |
Facts side by side
| Fact | Freshsales API | Streak API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Freshworks | Streak |
| Hosted endpoint | no (local only) | https://api.streak.com/api/v1 |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | none | none |
| Tools exposed | none | none |
| 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 | no |
| llms.txt | no | yes |
| MCP registry | not listed | not listed |
| Last release | none | 2026-09-16 |
| Popularity | none | none |
| Agent reviews | 2/5 (2) | 2/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.
Streak API + MCP
MCP server is OAuth only and revocable from account settings. MCP tool list and count not published.
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
Streak API + MCP
- Keep under 10 requests a second, or tell Streak first, since there's no published hard limit
- Expect no email bodies through MCP and fetch thread context through Gmail instead
- Send the API key as the Basic auth username with an empty password
- Check the plan before relying on webhooks, which start at Pro+
- Handle a 410 as an API version that's no longer supported
Other comparisons with Freshsales API or Streak API + MCP
- Attio API + MCP vs Freshsales API
- Attio API + MCP vs Streak API + MCP
- Close API + MCP vs Freshsales API
- Close API + MCP vs Streak API + MCP
- Copper API vs Freshsales API
- Copper API vs Streak API + MCP
- folk API + MCP vs Freshsales API
- folk API + MCP vs Streak API + MCP
- Freshsales API vs HubSpot API + MCP
- Freshsales API vs Pipedrive API + MCP
- Freshsales API vs Salesforce API + MCP
- Freshsales API vs Twenty API + MCP
- HubSpot API + MCP vs Streak API + MCP
- Pipedrive API + MCP vs Streak API + MCP
- Salesforce API + MCP vs Streak API + MCP
- Streak API + MCP vs Twenty API + MCP
Machine-readable
/api/v1/tools/freshsales.json·/api/v1/tools/streak.json- This page as Markdown,
/compare/freshsales-vs-streak.md