Salesforce MCP server: connect AI agents to Salesforce from the EU

Salesforce, based in San Francisco, makes the CRM used by many large European companies for sales, service and marketing. Each company works in its own Salesforce org, with custom objects, fields and permissions.

Salesforce Hosted MCP Servers are run by Salesforce for your org. Rather than one server, there are several standard servers with defined scopes: SObject All, SObject Reads, SObject Mutations and SObject Deletes for record data, plus servers for Data 360, CRM Analytics and other areas. They are disabled by default. An admin enables the ones the organisation wants, which makes it simple to offer read-only access first.

An account agent can prepare for a quarterly review by reading the account, open opportunities, recent cases and contacts, and summarising risks and next steps. After a meeting, it can update the opportunity stage and next step once a person confirms.

Service teams can have an agent read a new case, find similar resolved cases and suggest an answer. Sales operations can ask "which opportunities over 50,000 euros have not been updated in 30 days?" and get a list with owners and links.

A Salesforce admin enables the hosted MCP servers the organisation wants and configures the connected app or external client app the agent uses. Choosing SObject Reads alone is a sensible first step.

Add the Salesforce connector on inference.eu, choose the server, and each user signs in to Salesforce through OAuth. The agent then acts as that user. Tokens are stored encrypted in the EU and used only by the agents you allow. Admins can revoke OAuth tokens and turn servers off in Salesforce Setup at any time.

Records are fetched from Salesforce's own hosted MCP servers, so data stays with Salesforce, a US company, as it does for your other Salesforce integrations. Orgs running on Hyperforce in an EU region keep their data stored there.

On inference.eu, the model that reads and writes your CRM data runs in EU data centres, and your Salesforce credentials are stored encrypted in the EU. Because Salesforce applies field-level security and sharing to every call, sensitive fields hidden from a user stay hidden from the agent acting for them.

CRM updates trigger flows, assignment rules and notifications, and deletes remove records other teams depend on. Splitting reads, mutations and deletes into separate servers lets you choose exactly what an agent may do.

On inference.eu you can let queries run on their own and require a person's approval before an agent creates or updates a record. The approval shows the object, record and fields that will change. For most agents, leave the SObject Deletes server off entirely; if you need it, require approval for every delete.