01 · Enable
The server is off until someone turns it on
MCP servers are disabled by default. An assistant with a correct login still sees nothing until an admin enables the server and registers the client app.
For sales teams on Salesforce
A Salesforce MCP server that reads opportunities as the user, and does not delete them
A Salesforce MCP server uses Hosted MCP, generally available since the April 2026 release. An admin enables it. The user signs in with authorization code and PKCE. Sharing rules and field security still apply. Pexon does not add a service account, and the signed tool list does not delete records.
Checked 6 October 2026
Salesforce at a glance: interfaces, access and what exists for AI
| What we found | |
|---|---|
| Interfaces | Salesforce Hosted MCP (MCP over HTTPS, docs public) · Salesforce REST API (REST/JSON, docs public) |
| Authentication | Hosted MCP allows the authorization-code flow with PKCE only. There is no client-credentials flow and no service account. Dynamic client registration is off: an admin creates the External Client App. Every tool call runs as that user, and API logs mark the client category SALESFORCE_HOSTED_MCP. |
| Vendor MCP server | Vendor server, GA. Salesforce Hosted MCP Servers are generally available. The developer blog of April 2026 says they were a pilot, then a beta in October, then GA. Servers are off until an admin enables them. |
| Vendor AI assistant | Agentforce is Salesforce's own agent product, called through a separate Agent API. That API can use client credentials. Hosted MCP cannot. The two are not the same login. |
| Other connectors | None found. |
Salesforce, Inc. (US). Sales teams whose CRM is Salesforce, including DACH companies that run a horizontal CRM rather than a German specialist. The DACH overview of 14 May 2026 names Salesforce as one of those generalists. No market share is repeated here.
Why Salesforce is hard for agents
Where a Salesforce connection needs engineering, not configuration
02 · No robot
There is no headless MCP login
Client credentials work for the Agent API and do not work for Hosted MCP. A nightly job that asks the pipeline has to be a person, or it is not MCP.
03 · Scope
mcp_api is not a REST key
The MCP scope does not unlock the existing REST APIs. A tool that needs a resource the MCP server does not expose is a separate, reviewed API call.
04 · Write
sObject tools can create and delete
The hosted server can read, create, update and delete records the user may already change. A sales question does not need delete. The signed list does not include it.
What we build
A first Salesforce tool list, written as the manifest your IT team signs
Built on what Salesforce, Inc. documents: accounts, contacts, opportunities, tasks, events, flows and Apex exposed on purpose. Backends named below are documented resources; "confirmed in blueprint" means the vendor documentation sits behind a login and the resource is checked against your release first.
# salesforce-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
list_my_opportunities: # owner, stage, close date -> open opportunities the user may see
backend: Hosted MCP sObject read, Opportunity
mode: read
get_account: # account -> owner and related contacts
backend: Account and Contact, sharing rules applied
mode: read
list_tasks: # opportunity -> open tasks
backend: Task, read
mode: read
get_opportunity: # opportunity -> stage, amount, close date
backend: Opportunity read
mode: read
draft_task: # opportunity, subject, date -> a task a person saves
backend: not created by the agent
mode: propose
audit: every call logged with user, tool, arguments and the Salesforce responseThe manifest is the contract. A question that needs an operation not on it gets a new line and a review, not a wider permission.
One interface per row
How the Salesforce interfaces differ
01
Salesforce Hosted MCP
MCP over HTTPS. Documentation is public. generally available. Enable a server in Setup, then an External Client App with the mcp_api and refresh_token scopes. Standard servers expose sObject operations. Custom servers can expose flows, Apex and named queries
02
Salesforce REST API
REST/JSON. Documentation is public. the same objects the user can already open. Field-level security and sharing apply. MCP uses its own scope and does not grant the REST APIs
Salesforce holds the records. An assistant without a governed way in answers from whatever someone pasted into the chat. The connector is the governed way in: named operations, the person's own permissions, every call logged.
What the connector answers, and what it will not do
Questions it answers
- Which of my opportunities are open past their close date?
- Who is the account owner, and which contacts sit on that account?
- What tasks are open on this opportunity?
What it will not do
- Create, edit or delete an opportunity, contact or task. The signed list is read-only.
- Run as a service account. Hosted MCP has no such login.
- Call a flow or Apex action that was not explicitly exposed on the MCP server.
When this is the wrong page
If Claude or ChatGPT should use the hosted server Salesforce already runs, enable it and stop. A connector is right when the tool list must exclude writes, or when the question also needs a system Salesforce does not hold.
Start with the Readiness Blueprint.
Two weeks, €4,900 fixed price. Week one agrees the tool list with your Salesforce owners and checks every backend against your release and licence. Week two tests whether a person's own Salesforce permissions reach through the connector. You keep the manifest and a costed build plan, whoever builds it. All prices are net and exclude VAT.
What we need from you: a named Salesforce administrator, a test or sandbox system we may call, and one business owner who can say which questions the assistant should answer first. The first production connector is usually a use-case pilot from €15,000; it runs in your environment, and the code is yours.
Related
- Connectors for 100 source systems — the dated catalogue this page belongs to
- CAS genesisWorld connector — CRM, CAS Software AG
- cobra CRM connector — CRM, cobra computer's brainware GmbH
- HubSpot connector — CRM, HubSpot, Inc.
- Claude MCP server development — how we build an MCP server for any internal system
Questions Salesforce teams ask before the first tool call
Does Salesforce ship its own MCP server?
Salesforce Hosted MCP Servers are generally available. The developer blog of April 2026 says they were a pilot, then a beta in October, then GA. Servers are off until an admin enables them. This page describes what we add around that fact: a signed tool list and a test that the asking user only sees their own records.
Can the assistant change a deal or send a mail?
Not on the list we sign. The blueprint starts read-only. A draft the person saves in the CRM is the only write, and only after that is agreed.
Will two sellers see the same pipeline?
Only where the CRM would already show both of them the same records. Calls run as the person who asked. The blueprint tests that with two users before anything is called production.
What does a Salesforce connector cost?
The two-week Readiness Blueprint is fixed at €4,900: the tool list, a check against your tenant, and a test that permissions survive the round trip. A production connector is usually a use-case pilot from €15,000. Prices are net, excluding VAT.
Next step
Not a sales call. An architecture call.
Thirty minutes with the engineer who would build the connector, with your Salesforce administrator in the room if you like.