HubSpot MCP vs Salesforce MCP: which official server fits your AI agents

There is no single "Salesforce MCP"

Search for HubSpot MCP and you find one product: a hosted server that HubSpot made generally available to all HubSpot accounts on 13 April 2026. Search for Salesforce MCP and you find a family. Salesforce publishes a hosted MCP server for Marketing Cloud Engagement (MCE), a set of Hosted MCP Servers for Salesforce orgs, and developer-side tooling such as the Salesforce DX MCP Server. Each one reaches different data and is set up differently.

That makes a straight head-to-head misleading. HubSpot's server spans CRM and marketing in one place because HubSpot keeps both in one platform. On the Salesforce side, the closest match depends on the job. Campaign operations in Marketing Cloud point to the MCE server. Agent work on accounts, contacts, opportunities, and cases points to Hosted MCP Servers.

If you are still deciding which platform should hold your customer records, start with a broader guide to how HubSpot and Salesforce compare as CRMs. This dispatch assumes the CRM decision is already made, or that you run both, and asks a narrower question: which official MCP server should your AI agents connect to, and what will it let them do?

Botfinder catalogs two of these servers: HubSpot MCP and Salesforce Marketing Cloud Engagement MCP. Salesforce Hosted MCP Servers are covered below from Salesforce's own documentation; they do not have a Botfinder catalog profile yet.

HubSpot: one hosted endpoint for CRM and marketing work

HubSpot's remote MCP server lives at https://mcp.hubspot.com. Any MCP client that supports OAuth with PKCE can connect, and PKCE is mandatory. Builders create a connector under Development > MCP Connectors in their HubSpot account to get a client ID, secret, and redirect URLs. Most business users never see that step: HubSpot's Claude, ChatGPT, Microsoft Copilot, and Gemini connectors are built on this server, so teams already using one of those assistants can connect without custom setup.

The scope is wide. On the read side, HubSpot documents access to contacts, companies, deals, tickets, leads, custom objects and segments; calls, emails, meetings, notes and tasks; conversations across live chat, team email, WhatsApp, SMS, Facebook Messenger and custom channels; blog posts, landing pages, site pages, campaigns and marketing events; marketing email drafts, send statistics and engagement; social posts and performance; and AEO brand metrics. Commerce objects such as quotes, invoices, orders and subscriptions are marked beta.

It writes, too. The server can create and edit CRM records and activities, create and publish landing pages, website pages and blog posts, manage campaigns and marketing email drafts, create static segments, custom properties and pipelines, and draft or schedule social posts. The documented tool list ran to 36 tools when we checked it on 11 November 2026, including search_crm_objects, manage_crm_objects, query_crm_data, get_marketing_email_analytics, and manage_campaign_objects.

Several limits matter in practice. Every action is bounded by the signed-in user's HubSpot permissions. Scopes are set by the tools available at install time, so existing users must re-install the connector to pick up new scopes. If the account has Sensitive Data turned on, activity and conversation data is blocked through MCP, even though standard CRM APIs are unaffected. Search runs on HubSpot's CRM search API, which has no vector search.

• Subscription gating: the AEO tools need Marketing Hub Professional or Enterprise, beta quote tools need Revenue Hub Professional or Enterprise, and custom pipelines are unavailable on free-tools accounts.
• Client gating: manage_website_page, manage_blog_post, and render_asset work only in select clients (Claude, ChatGPT, and Gemini).
• Connector limits: HubSpot's Claude and ChatGPT connector guides cap bulk creates or updates at 10 records at a time, support no deletes, and keep all activity subject to HubSpot's API usage limits. The Gemini connector is read-only and English-only.
• Not the developer server: HubSpot's separate local Developer MCP server helps coding agents build apps and CMS assets on HubSpot's developer platform. It is a build tool, not a way for business agents to work with live CRM data.

Salesforce Marketing Cloud Engagement MCP: built for campaign operations

Salesforce announced general availability of its MCP server for Marketing Cloud Engagement on 2 June 2026, describing it as a first-party, hosted server that wraps existing MCE APIs as tools. It is not a CRM server. It works inside Marketing Cloud: data extensions, journeys, Automation Studio, Content Builder, email, SMS and push, contacts, campaigns, and tracking.

Setup is an admin task. In MCE Setup you create an installed package, add an API Integration component as a Public App, choose permission scopes, and note the client ID and tenant ID. Then you point your assistant at either the US or the EU server URL and sign in through OAuth. Salesforce says the choice of region affects only latency and that the servers store none of the data they access. Its setup guide names Claude Code and Gemini CLI as example clients, and the Claude Code example uses an HTTP transport.

Permissions are a combination of two layers: the scopes on the installed package and the signed-in user's own Marketing Cloud permissions. If either layer lacks access, the agent does too. That gives admins a clean way to issue a read-only package for analysis and a separate, narrower write package for a specific workflow.

Salesforce's Winter '27 developer guide, published 5 October 2026, added 40 tools. The new set creates and runs Automation Studio activities, manages campaigns and Content Builder folders, bulk-upserts data, queries data extensions, erases contacts, and retrieves email tracking events. The tool reference now groups tools into Automations, Campaigns, Contacts, Content, Data Extensions, Email, Journeys, Push, SMS, Tracking, and Utilities.

• Good fits from Salesforce's own examples: find the journey with the highest unsubscribe rate last week, spot over-targeted contacts across journeys, replace an outdated privacy-policy link everywhere, or write and test SQL against data extension schemas.
• Tools carry annotations where they apply: read-only, destructive, asynchronous, or open-world. Asynchronous tools need a second status call, which can consume more tokens.
• Destructive tools include sfmc_delete_contacts, sfmc_clear_data_extension_data, and sfmc_delete_journey. Salesforce's guidance is to ask the assistant for a dry run or to show the code it plans to execute first.

Salesforce Hosted MCP Servers: the CRM-side counterpart

If your team wants an agent to read pipeline, update opportunities, or log follow-up tasks in Salesforce, the MCE server will not help. That job belongs to Salesforce Hosted MCP Servers, which connect MCP clients such as Claude, ChatGPT, Cursor, or a custom agent to a Salesforce org with per-user OAuth 2.0 and PKCE. Salesforce's connection guides include a ChatGPT setup that runs through ChatGPT's developer mode.

Salesforce offers standard servers that admins switch on and cannot modify, plus custom servers they assemble. The standard SObject servers come in four scopes: SObject All (create, read, update, delete, query, and search), SObject Reads, SObject Mutations (create and update, no delete), and SObject Deletes. Other standard servers cover Salesforce CMS content, Data 360, Tableau Next, and several beta servers. Custom servers can expose Flows, Apex invocable actions, @AuraEnabled methods, Apex REST endpoints, Named Queries, API Catalog endpoints, and Prompt Builder templates.

Every tool call runs as the authenticated user, with field-level security, object permissions, and sharing rules enforced. Standard servers are off by default. Deletes through SObject tools go to the Recycle Bin and can be recovered in the Salesforce UI for up to 15 days, but there is no undelete tool over MCP. Winter '27 also lets admins expose Agentforce agents as MCP tools on a custom server.

This is the closest Salesforce equivalent to HubSpot's remote server for CRM records. It is also the most expensive to reason about, because of how Salesforce bills it.

Side by side: the three official servers

The table compares documented behavior as of 11 November 2026. All three change often, so confirm current tools in each vendor's reference before you design a workflow around a specific capability.

Write access: where each vendor puts the brakes

HubSpot puts confirmation inside the tools. manage_crm_objects shows a summary of proposed changes and needs explicit confirmation before any create or update. Segment writes, campaign changes, landing page and website page publishing, and AEO recommendation actions all require confirmation. New blog posts start as drafts, and publishing needs another confirmation. HubSpot's documentation does not state a confirmation step for custom pipelines, custom properties, or marketing email drafts, so treat those as unguarded and decide in your client whether they need approval. HubSpot's connector guides also recommend setting write tools to "Needs Approval" rather than "Always allow".

Salesforce MCE puts the responsibility on scopes and the operator. Destructive operations are labeled so the agent can read the warning, but Salesforce states plainly that the agent can still choose to run them if it has permission. Its GA announcement also flags reputational harm from an unintended send. In MCE, the riskiest actions are not only deletes. sfmc_send_transactional_email, sfmc_run_automation, and journey publishing reach real customers.

Hosted MCP Servers let admins limit risk by choosing which server to enable. A team that only needs reporting can enable SObject Reads and never expose mutation or delete tools. Salesforce describes SObject All as the option for full access when you trust users to prompt appropriately, with the permission model as a safety net.

• Start every pilot read-only: a HubSpot user with view-only permissions, an MCE package with read scopes, or the SObject Reads server.
• Separate send, publish, and delete rights from analysis work. In MCE that means a separate installed package; in Salesforce orgs, a separate server.
• Keep the client's approval setting on for write tools, even where the server already asks for confirmation.
• Log record IDs and journey or automation keys for anything the agent changes, so you can verify and reverse.

Costs: where the meter runs

None of these vendors publishes a simple per-call price for MCP. What they do publish is where costs land, and the three are very different.

HubSpot does not list a separate MCP charge in the developer documentation. What the agent can reach depends on your HubSpot subscription: AEO tools need Marketing Hub Professional or Enterprise, for example. The built-in assistant connectors add the assistant's own requirements. HubSpot's Claude connector needs a paid Anthropic plan, and its Gemini connector needs an eligible paid Google Workspace plan.

Salesforce states that the MCE MCP server has no additional cost. Your AI assistant's token usage is billed by the AI provider under your contract with them, and the Marketing Cloud API calls issued by the MCP server count toward your edition's annual API limit. Bulk agent work against data extensions can use up that allowance faster than a human operator would.

Hosted MCP Servers are, in Salesforce's words, "intended only for customers with Flex Credits", and you may be billed for server usage. Salesforce's AIforce Help article (published 17 September 2026) explains the model: once an agent is registered, every successful call it makes over MCP or direct API is metered as a Headless Platform Interaction in Digital Wallet. The multiplier for that usage type is listed as TBA, agentic usage is not metered yet, and Salesforce promises 30 days' notice before metering begins. Sandboxes, scratch orgs, and Developer Edition orgs are not metered.

The same article says use of any Salesforce MCP server requires agent registration within three months of notice from Salesforce. MCE's documentation still describes the server as free of additional Salesforce cost. If you run Marketing Cloud agents at scale, ask your account executive how those two statements apply to your contract.

Which one fits your team

Choose by system of record first and by job second. Most teams will end up with one primary server, and teams running HubSpot alongside Marketing Cloud may reasonably run two.

A two-week pilot that tells you something

Whichever server you pick, a short, controlled pilot beats a feature checklist. Give it one owner, one workflow, and a clear definition of a useful result.

• Week one: connect with read-only access, run five real questions your team asks every week, and check every answer against the source system.
• Record which tools the agent called. HubSpot's get_user_details shows what the connection can reach; in MCE, review the scopes on the installed package.
• Week two: allow one narrow write path, such as updating a single deal property in HubSpot or upserting rows into one test data extension in MCE, with approval on.
• Track API consumption alongside time saved, especially in Marketing Cloud, where calls draw down the annual limit.
• Review our MCP security checklist before you widen access.

The bottom line

HubSpot offers the simpler MCP story: one official server, one URL, and assistant connectors that let business users start without engineering help. Its breadth is a strength for HubSpot-centric revenue and marketing teams, and its in-tool confirmations make early write workflows easier to govern.

Salesforce offers more precision and more moving parts. The Marketing Cloud Engagement MCP is a capable, no-additional-cost server for campaign operators, limited mainly by API allowances and how carefully you scope its package. Hosted MCP Servers bring CRM-record access with fine-grained server choices, but tie usage to Flex Credits and a metering model Salesforce has not priced yet. Know which Salesforce server you mean before you compare it with anything.