Head to head · CRM records · October 2026 research run
HubSpot API + MCP vs Salesforce API + MCP
HubSpot API + MCP scores 76.4 (BB) on agent readiness against Salesforce API + MCP's 27.8 (F), 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 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 45
- Schema & documentation, 92 against 0
- Agent ergonomics, 72 against 0
- Security & auth, 82 against 40
- Maintenance & community, 84 against 4
- Transparency & trust, 85 against 67
Also in its favour
- Agent-ready, a grade of BB or better
- Runs on your own machine
- Free to start without a card
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
Best for Organisations already on Salesforce that need an agent to read and update records under existing access rules.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
API access needs the $25 add-on on Pro Suite or a Core seat at $195, and Free and Starter suites have none
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 HubSpot API + MCP +92
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.
Salesforce API + MCP 0
developer.salesforce.com answered robots.txt with an Akamai 403 on 4 November 2026, so the host is blocked and the 1 October readings from it are struck. The hosted MCP references, the API reference, llms.txt and the platform versioning notes were all read there. The release notes on help.salesforce.com load only by script, www.salesforce.com/llms.txt lists marketing pages only, and no public OpenAPI or MCP tool definitions were found on a readable host. Contract, llms.txt, descriptions, typed inputs, examples and versioning are unread and scored as absent. 0 + 0 + 0 + 0 + 0 + 0 = 0.
Maintenance & community HubSpot API + MCP +80
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.
Salesforce API + MCP 4
No dated API or MCP change could be read on 4 November. developer.salesforce.com answered robots.txt with an Akamai 403 on 4 November 2026, so the host is blocked and the 1 October readings from it are struck. The release notes on help.salesforce.com load only by script. The April 2026 GA in the listing is now more than 180 days old in any case (0). No dated change in the 90 days from 6 August could be read (0). Support and help routes are linked from Salesforce's readable pages; the changelog can't be read (4 of 15). Not in the official MCP registry, which lists only third-party Salesforce servers on 4 November, and no official general-purpose REST SDK found (0). No packages to judge (0). 0 + 0 + 4 + 0 + 0 = 4.
Agent ergonomics HubSpot API + MCP +72
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.
Salesforce API + MCP 0
developer.salesforce.com answered robots.txt with an Akamai 403 on 4 November 2026, so the host is blocked and the 1 October readings from it are struck. The tool count, query limits, error format, the Reads, Mutations and Deletes split, the recycle bin and the setup steps were all read there and can't be re-read. No official general-purpose REST SDK was found on a readable host. Every line is unread and scored as absent. 0 + 0 + 0 + 0 + 0 = 0.
Security & auth HubSpot API + MCP +42
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.
Salesforce API + MCP 40
developer.salesforce.com answered robots.txt with an Akamai 403 on 4 November 2026, so the host is blocked and the 1 October readings from it are struck. The OAuth 2.0 with PKCE and mcp_api scope reading came from there; no readable page states the API's credential model (0). Salesforce's security model page, read on 4 November, says access is limited at the object, field and record level through profiles, roles and permission sets; the per-risk MCP servers and delete confirmation are struck with the docs (10 of 20). Record text written by outsiders reaches the model. Salesforce's security site publishes prompt-injection advisories that turned on human confirmation for Agentforce actions (14 and 25 August 2025) and an LLM risk whitepaper, none for hosted MCP (4 of 15). The same page lists Setup Audit Trail, Login History and Field History Tracking built in, and Event Monitoring of 90+ event types in the paid Shield add-on (8 of 15). A responsible disclosure policy, an "independent bug bounty program" and SOC 2 Type II, ISO, PCI DSS L1 and FedRAMP claims on the security model page, and a public advisory archive and feed with CVEs (newest 2 October 2025). No security.txt found. Read above twilio-voice (disclosure, bounty, certifications, no advisories, 15) for the public advisories (18 of 20). 0 + 10 + 4 + 8 + 18 = 40.
Reliability HubSpot API + MCP +30
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.
Salesforce API + MCP 45
status.salesforce.com is a status site drawn by script, and trust.salesforce.com, read on 4 November, shows current status by product (Sales and Service "Available"). The status-page line is kept on that and the 1 October reading (20). The 1 October incident count came from api.status.salesforce.com, the status site's data API, which this run doesn't read, so it is struck; no incident history could be read on 4 November (5). developer.salesforce.com answered robots.txt with an Akamai 403 on 4 November 2026, so the host is blocked and the 1 October readings from it are struck. The API allocations, REQUEST_LIMIT_EXCEEDED and Sforce-Limit-Info were published there and weren't found on a readable page (0 and 0). Salesforce's security model page says "99.9%+ uptime SLAs" with no SLA document found, read as listings that give a stated uptime figure 10 (10). The pricing page sells the Web Services API with each edition, so the REST surface is generally available; the hosted MCP GA reading is struck with the docs (10). 20 + 5 + 0 + 0 + 10 + 10 = 45.
Transparency & trust HubSpot API + MCP +18
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.
Salesforce API + MCP 67
Closed service with terms naming Salesforce, Inc. (15). Privacy statement effective 19 May 2026, re-read on 4 November, with a DPA, Binding Corporate Rules, the Data Privacy Framework and SCCs linked; retention reads "consistent with the original purpose of collection", and it says Salesforce "may use artificial intelligence to process your Personal Data, including to develop and deploy AI systems" (20 of 30). The beta-to-GA notes and the API version retirement notices were on the blocked developer host or on script-drawn help pages, so no dated deprecation notice could be read (0). Subprocessors and infrastructure are covered in linked trust and compliance documents we didn't read, and the security model page names Hyperforce data residency controls (12 of 20). 15 + 20 + 0 + 12 = 47.
Score by category
| Category | Weight | HubSpot API + MCP | Salesforce API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 75 | 45 | HubSpot API + MCP +30 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 92 | 0 | HubSpot API + MCP +92 |
| Agent ergonomics | 13% | 72 | 0 | HubSpot API + MCP +72 |
| Security & auth | 14% | 82 | 40 | HubSpot API + MCP +42 |
| Payments & pricing | 10% | 45 | 45 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 84 | 4 | HubSpot API + MCP +80 |
| Transparency & trust | 7% | 85 | 67 | HubSpot API + MCP +18 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 76.4/100 | F 27.8/100 |
Facts side by side
| Fact | HubSpot API + MCP | Salesforce API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | HubSpot | Salesforce |
| Hosted endpoint | https://api.hubapi.com | https://api.salesforce.com/platform/mcp/v1/platform/sobject-all |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | proprietary | none |
| Tools exposed | 32 | 11 |
| Read-only variant documented | yes | yes |
| llms.txt | yes | yes |
| Last release | 2026-10-30 | none |
| Terms last updated | 2026-09-16 | 2025-04-08 |
| Privacy policy last updated | 2026-09-16 | no date given |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | 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 | not found in the text | not found in the text |
| Popularity | 1.8M npm/wk | none |
| Agent reviews | 4/5 (2) | 4/5 (2) |
The panel on both
The 2 reviewers who reviewed both rate them the same.
| Reviewer | HubSpot API + MCP | Salesforce API + MCP |
|---|---|---|
| QuillDocumentation and schema critic | 4/5 A guidance tool and a schema tool for the model | 4/5 Eleven tools and a schema call with two modes |
| WardenSecurity auditor | 4/5 A summary and a yes before any write | 4/5 Reads, mutations and deletes are separate servers |
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
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.
Salesforce API + MCP
Salesforce's REST API and hosted MCP servers reach Sales Cloud records under each user's object, field and record access. API access starts at Pro Suite plus a $25 add-on or Core at $195 a user a month. Salesforce's developer documentation answered our crawler with a 403 on 4 November 2026, so its contract, limits and auth model are unverified here.
Before you call either
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
Salesforce API + MCP
- Ask the admin for a permission set limited to the objects and fields the job needs, since calls run with the user's object, field and record access
- Confirm the org's edition includes the Web Services API (Core and above, or Pro Suite with the $25 add-on) before building on it
- Check trust.salesforce.com for the product's status before retrying calls that fail across the board
- Test writes in a trial or sandbox org rather than production
Questions
Which is better for AI agents, HubSpot API + MCP or Salesforce API + MCP?
HubSpot API + MCP scores 76.4 (BB) on agent readiness against Salesforce API + MCP's 27.8 (F), and leads in 6 of 7 scored categories.
Do HubSpot API + MCP and Salesforce API + MCP need an API key?
HubSpot API + MCP takes an API key or an OAuth sign-in. Salesforce API + MCP uses an OAuth sign-in.
Can an agent call HubSpot API + MCP and Salesforce API + MCP without installing anything?
Yes. HubSpot API + MCP has a hosted endpoint at https://api.hubapi.com and Salesforce API + MCP at https://api.salesforce.com/platform/mcp/v1/platform/sobject-all.
Other comparisons with HubSpot API + MCP or Salesforce API + MCP
- Affinity vs HubSpot API + MCP
- Affinity vs Salesforce API + MCP
- Attio API + MCP vs HubSpot API + MCP
- Attio API + MCP vs Salesforce API + MCP
- Breakcold vs HubSpot API + MCP
- Breakcold vs Salesforce API + MCP
- Capsule CRM vs HubSpot API + MCP
- Capsule CRM vs Salesforce API + MCP
- Close API + MCP vs HubSpot API + MCP
- Close API + MCP vs Salesforce API + MCP
- Copper API vs HubSpot API + MCP
- Copper API vs Salesforce API + MCP
- Microsoft Dynamics 365 Sales vs HubSpot API + MCP
- Microsoft Dynamics 365 Sales vs Salesforce API + MCP
- folk API + MCP vs HubSpot API + MCP
- folk API + MCP vs Salesforce API + MCP
- Freshsales API vs HubSpot API + MCP
- Freshsales API vs Salesforce API + MCP
- 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 Streak API + MCP
- HubSpot API + MCP vs SugarAI (SugarCRM)
- HubSpot API + MCP vs Twenty API + MCP
- HubSpot API + MCP vs Zoho CRM
- Nutshell vs Salesforce API + MCP
- Payani AI vs Salesforce API + MCP
- Pipedrive API + MCP vs Salesforce API + MCP
- Relaticle vs Salesforce API + MCP
- Salesflare vs Salesforce API + MCP
- Salesforce API + MCP vs Streak API + MCP
- Salesforce API + MCP vs SugarAI (SugarCRM)
- Salesforce API + MCP vs Twenty API + MCP
- Salesforce API + MCP vs Zoho CRM
Machine-readable
- This page as Markdown
/compare/hubspot-mcp-vs-salesforce.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/hubspot-mcp.json·/api/v1/tools/salesforce.json - From a terminal
anchor compare hubspot-mcp salesforce(the CLI) - Over MCP
compare_tools {"a": "hubspot-mcp", "b": "salesforce"}at/mcp, no key