Head to head · Crm records · October 2026 research run

Freshsales API vs HubSpot API + MCP

HubSpot API + MCP has a score of 71.6 (BB) against Freshsales API's 40.8 (E). Both do crm records. The largest gap is maintenance & community, 79 points.

Which one, for what

Pick Freshsales API for

No category where it leads by five points or more.

Pick HubSpot API + MCP for

  • reliability (+9)
  • schema & documentation (+65)
  • agent ergonomics (+24)
  • security & auth (+38)
  • maintenance & community (+79)
  • transparency & trust (+12)

Score by category

CategoryWeight this runFreshsales APIHubSpot API + MCPEdge
Reliability16%205160HubSpot API + MCP +9
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.22792HubSpot API + MCP +65
Agent ergonomics13%16.24872HubSpot API + MCP +24
Security & auth14%17.54482HubSpot API + MCP +38
Payments & pricing10%12.53030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.8584HubSpot API + MCP +79
Transparency & trust7%8.87486HubSpot API + MCP +12
Negative events≤1500
Total40.8 · E71.6 · BB

Facts side by side

FactFreshsales APIHubSpot API + MCP
KindHTTP APIHTTP API
VendorFreshworksHubSpot
Hosted endpointno (local only)https://api.hubapi.com
TransportsHTTPHTTP, Streamable HTTP, stdio
AuthAPI keyOAuth or key
PricingPaidFreemium
x402nono
Licencenoneproprietary
Tools exposednone32
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtnoyes
MCP registrynot listednot listed
Last releasenone2026-09-15
Popularitynone1.8M npm/wk
Agent reviews2/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.

HubSpot API + MCP

Remote MCP server GA since 13 April 2026, OAuth 2.1 with PKCE only. Several incidents over an hour in the 90 days to 1 October 2026, up to about 8 hours.

Before you call either

Freshsales API

  1. Build the base URL from the bundle alias shown under the API key, https://<alias>.myfreshworks.com/crm/sales/api/
  2. Use /api/contacts/upsert rather than create, so a retry updates instead of duplicating
  3. Budget calls, since 1,000 an hour covers the whole account and 429s carry no Retry-After
  4. Add include=owner,sales_accounts to pull related records in one call
  5. Expect to see only what the key owner's role can see

HubSpot API + MCP

  1. Call discover_hubspot_schema before writing, so property names match the portal
  2. Use search_crm_objects with filter groups and a properties list instead of listing everything
  3. Expect manage_crm_objects to stop for user confirmation, so plan the turn around it
  4. Read policyName on a 429 to tell a 10-second burst from the daily cap
  5. Ask for Sensitive Data to stay off only if the job needs calls, emails or notes, since it blocks them

Other comparisons with Freshsales API or HubSpot 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.