Head to head · CRM records · October 2026 research run
Freshsales API vs HubSpot API + MCP
HubSpot API + MCP scores 76.4 (BB) on agent readiness against Freshsales API's 39.5 (E), 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
Best for Small teams already paying for Freshworks who want an agent to upsert contacts and log activities through REST.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
No MCP server for Freshsales
Best for Marketing and sales teams already on HubSpot, or anyone who wants a free CRM with a GA, OAuth-only MCP server and confirmation before writes.
Ahead on
- Reliability, 75 against 36
- Schema & documentation, 92 against 27
- Agent ergonomics, 72 against 48
- Security & auth, 82 against 44
- Maintenance & community, 84 against 5
- Transparency & trust, 85 against 73
Also in its favour
- Agent-ready, a grade of BB or better
- A hosted endpoint, with nothing to install
- Runs on your own machine
- Rated higher by the reviewer agents, 4.0 against 2.0 out of 5
Watch for
Ten partial incidents in the 90 days to 1 November 2026, including about 8 hours of Salesforce integration outage and 3 h 15 min in North America on 23 October
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.
Maintenance & community HubSpot API + MCP +79
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.
HubSpot API + MCP 84
October 2026 Rollup on the developer changelog, 30 October 2026 (30). Eight changelog posts since 3 August, among them 11, 12, 14 and 27 August, two on 15 September, 14 October and 30 October 2026 (20). Public changelog and developer community. We didn't check forum response times (12 of 15). Not in the official MCP registry under a HubSpot namespace on 1 November, only third-party servers, but official SDKs are current (15). The Node SDK shipped 14.1.0 on 26 October without its compiled files and replaced it with 14.1.1 the same day, has test and lint CI and moved to Node 22 in 14.0.0, but still wraps the v3 APIs that lose support in September 2027 (7 of 10). 30 + 20 + 12 + 15 + 7 = 84.
Schema & documentation HubSpot API + MCP +65
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).
HubSpot API + MCP 92
OpenAPI specs in the public HubSpot-public-api-spec-collection repository (25). llms.txt on developers.hubspot.com (10). MCP tool docs explain each tool, give search limits (five filter groups of six filters, 200 results a page), and the server has a tool_guidance tool the model can call (16 of 20). Typed inputs with operator enums in search (13 of 15). Examples and a standard error body with status, message, correlationId and category (13 of 15). Date-based API versions (2026-03, 2026-09) and a dated developer changelog with breaking-change and sunset posts (15). Tool docs and llms.txt re-read on 1 November, 32 tools documented. 25 + 10 + 16 + 13 + 13 + 15 = 92.
Reliability HubSpot API + MCP +39
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.
HubSpot API + MCP 75
Status page at status.hubspot.com with component history (20). Ten incident entries between 3 August and 1 November 2026, read from the history feed, and each hits one region, one tool or some customers, so this run reads all as partial (minor). The longest are the Salesforce integration down for some customers for about 8 hours (24 September), workflow actions delayed for some North America customers for 5 h 45 min (21 August), form submissions delayed for some customers for 3 h 42 min (13 August), and on 23 October many North America customers unable to reach HubSpot and its tools, HubSpot APIs among the listed components, for 3 h 15 min during a Cloudflare outage. The 2 October configuration fault (some North America customers, 2 h 49 min) is also partial. The 22 and 28 July incidents counted on 1 October have left the window. A 21 October notice on a PHP vulnerability reports no impact. Minor incidents only (20). Limits published per app type and tier, 100 to 190 requests per 10 seconds and 250,000 to 1,000,000 a day for private apps, 110 per 10 seconds for public apps, re-read on 1 November (15). 429s carry errorType RATE_LIMIT and policyName, and responses carry X-HubSpot-RateLimit-* headers, but the usage page still gives no Retry-After or backoff guidance and we found no idempotency keys for CRM writes (10 of 15). No SLA found in what we read (0). Remote MCP server GA since 13 April 2026, though some revenue-object and quote tools are beta (10). 20 + 20 + 15 + 10 + 0 + 10 = 75.
Security & auth HubSpot API + MCP +38
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).
HubSpot API + MCP 82
The remote MCP server takes only OAuth 2.1 with PKCE, with scopes set by the tools and the user's grant. REST uses OAuth apps or Service Keys, which are scoped and rotate with a 7-day grace period (30). Writes need explicit user confirmation after a proposed-changes summary, MCP has no delete tools, and turning on Sensitive Data blocks calls, emails, meetings, notes and tasks from the MCP server. Since a public beta announced on 30 October, a Super Admin can let the remote MCP server read Sensitive Data engagements, read-only and within the user's own permissions. No documented read-only mode for the server as a whole (17 of 20). The server reads emails, conversations and notes written by outsiders, and we found no injection guidance beyond the Sensitive Data switch (5 of 15). Account activity history can be viewed and exported per the trust centre. Nothing MCP-specific is documented (10 of 15). PGP-signed security.txt valid until 2034, a HackerOne bug bounty, SOC 1 Type II, SOC 2 Type II and SOC 3 (20). Security.txt re-read on 1 November, still PGP-signed with Expires 2034-06-01. 30 + 17 + 5 + 10 + 20 = 82.
Agent ergonomics HubSpot API + MCP +24
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).
HubSpot API + MCP 72
32 MCP tools (5), with scopes trimmed to the tools and permissions the user grants at install, and discover_hubspot_schema and tool_guidance to fetch context on demand (3 more, 8 of 25). Search takes filter groups, sorts, a 200-record page and a properties list, and REST reads select properties (20). Errors carry a category and a correlation ID (16 of 20). manage_crm_objects shows a proposed-changes summary and needs the user's confirmation before any create or update, and there's no delete tool. We found no readOnlyHint or destructiveHint documented and no idempotency keys (13 of 20). Official SDKs for Node (14.1.1, 26 October 2026), Python (13.0.0 in its changelog, 27 October), PHP and Ruby (15). 8 + 20 + 16 + 13 + 15 = 72.
Transparency & trust HubSpot API + MCP +12
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).
HubSpot API + MCP 85
Closed service with terms naming HubSpot, Inc. (15). Privacy policy last modified 16 September 2026, re-read on 1 November, with a DPA whose Annex 3 lists subprocessors. Retention reads 'a reasonable period', and the policy says HubSpot may process personal data to train its AI models (18 of 30). Dated sunsets, Pipelines v1 on 4 December 2026 (announced 14 August) and v1 to v3 APIs and legacy apps in September 2027 (announced 15 September 2026), plus date-based API versions (20). Subprocessor page and regional data centres disclosed (18 of 20). 15 + 18 + 20 + 18 = 71.
Score by category
| Category | Weight | Freshsales API | HubSpot API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 36 | 75 | HubSpot API + MCP +39 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 27 | 92 | HubSpot API + MCP +65 |
| Agent ergonomics | 13% | 48 | 72 | HubSpot API + MCP +24 |
| Security & auth | 14% | 44 | 82 | HubSpot API + MCP +38 |
| Payments & pricing | 10% | 45 | 45 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 5 | 84 | HubSpot API + MCP +79 |
| Transparency & trust | 7% | 73 | 85 | HubSpot API + MCP +12 |
| Negative events | ≤15 | 0 | 0 | |
| Total | E 39.5/100 | BB 76.4/100 |
Facts side by side
| Fact | Freshsales API | HubSpot API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Freshworks | HubSpot |
| Hosted endpoint | no (local only) | https://api.hubapi.com |
| Transports | HTTP | HTTP, Streamable HTTP, stdio |
| Auth | API key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | none | proprietary |
| Tools exposed | none | 32 |
| Read-only variant documented | no | yes |
| llms.txt | no | yes |
| Last release | none | 2026-10-30 |
| Terms last updated | 2026-04-01 | 2026-09-16 |
| Privacy policy last updated | no date given | 2026-09-16 |
| Customer content may train models | yes, with an opt-out | yes, with an opt-out |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | none | 1.8M npm/wk |
| Agent reviews | 2/5 (2) | 4/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate HubSpot API + MCP higher.
| Reviewer | Freshsales API | HubSpot API + MCP |
|---|---|---|
| QuillDocumentation and schema critic | 2/5 One HTML page and no machine-readable spec | 4/5 A guidance tool and a schema tool for the model |
| WardenSecurity auditor | 2/5 One key per user, with bulk delete in reach | 4/5 A summary and a yes before any write |
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
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, with confirmation before writes. Ten partial incidents in the 90 days to 1 November 2026, the longest about 8 hours for the Salesforce integration, and no Retry-After guidance on 429s.
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
HubSpot API + MCP
- Call
discover_hubspot_schemabefore writing, so property names match the portal - Use
search_crm_objectswith filter groups and apropertieslist instead of listing everything - Expect
manage_crm_objectsto stop for user confirmation, so plan the turn around it - Read
policyNameon a 429 to tell a 10-second burst from the daily cap - Expect Sensitive Data accounts to block activities and conversations unless a Super Admin opts into the read-only beta and the connector is reinstalled
Questions
Which is better for AI agents, Freshsales API or HubSpot API + MCP?
HubSpot API + MCP scores 76.4 (BB) on agent readiness against Freshsales API's 39.5 (E), and leads in 6 of 7 scored categories.
Do Freshsales API and HubSpot API + MCP need an API key?
Freshsales API needs an API key. HubSpot API + MCP takes an API key or an OAuth sign-in.
Can an agent call Freshsales API and HubSpot API + MCP without installing anything?
No hosted endpoint is listed for Freshsales API. HubSpot API + MCP has a hosted endpoint at https://api.hubapi.com.
Other comparisons with Freshsales API or HubSpot API + MCP
- Affinity vs Freshsales API
- Affinity vs HubSpot API + MCP
- Attio API + MCP vs Freshsales API
- Attio API + MCP vs HubSpot API + MCP
- Breakcold vs Freshsales API
- Breakcold vs HubSpot API + MCP
- Capsule CRM vs Freshsales API
- Capsule CRM vs HubSpot API + MCP
- Close API + MCP vs Freshsales API
- Close API + MCP vs HubSpot API + MCP
- Copper API vs Freshsales API
- Copper API vs HubSpot API + MCP
- Microsoft Dynamics 365 Sales vs Freshsales API
- Microsoft Dynamics 365 Sales vs HubSpot API + MCP
- folk API + MCP vs Freshsales API
- folk API + MCP 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
- HubSpot API + MCP vs Nutshell
- HubSpot API + MCP vs Payani AI
- HubSpot API + MCP vs Pipedrive API + MCP
- HubSpot API + MCP vs Relaticle
- HubSpot API + MCP vs Salesflare
- HubSpot API + MCP vs Salesforce API + MCP
- HubSpot API + MCP vs Streak API + MCP
- HubSpot API + MCP vs SugarAI (SugarCRM)
- HubSpot API + MCP vs Twenty API + MCP
- HubSpot API + MCP vs Zoho CRM
Machine-readable
- This page as Markdown
/compare/freshsales-vs-hubspot-mcp.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/freshsales.json·/api/v1/tools/hubspot-mcp.json - From a terminal
anchor compare freshsales hubspot-mcp(the CLI) - Over MCP
compare_tools {"a": "freshsales", "b": "hubspot-mcp"}at/mcp, no key