MCP Gateway · Claude Cowork
Connect Salesforce Platform to Claude Cowork
Territory planning, account handovers and pipeline reviews all mean reading many Salesforce records and writing something careful from them. Cowork can run that as a longer task against CRM data on Salesforce's hosted endpoints. Agent hooks send each prompt to Speakeasy before the step runs, and Cowork's OTLP export ties sessions to people.
- Category
- Sales & CRM
- Authentication
- OAuth
- Claude Cowork
- Cowork tab in Claude Desktop
Behind the MCP Gateway
Run Salesforce Platform MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Salesforce Platform call inspected and logged.
Before you start
What Salesforce Platform needs first
A Salesforce System Administrator does the Salesforce Platform side of the setup.
- You need System Administrator credentials for an API-enabled production or sandbox org.
- Salesforce documents Hosted MCP Servers for Enterprise Edition and above.
- Scratch orgs are not covered.
- Installing Speakeasy's app still needs Speakeasy support to finish OAuth.
In Salesforce Platform
- Open Setup and confirm Hosted MCP Servers are available.
- Either install Speakeasy's Salesforce app, or create an External Client App.
- For your own app, enable OAuth with the Speakeasy callback and the mcp_api and refresh_token scopes.
- Copy the Consumer Key.
- Enable the chosen MCP server under API Catalog > MCP Servers.
Set up
Add Salesforce Platform to Claude Cowork in 4 steps
- 01
Add Salesforce Platform from the catalog
An admin finds Salesforce Platform in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.
Salesforce Platform uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.
Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.
- 02
Choose who can use Salesforce Platform
Give teams the
mcp:connectscope on the Salesforce Platform server through team access or a role. Claude Cowork connects to the Salesforce Platform server's own URL, and the server's authorization decides who can connect and which tools they can call. - 03
Connect Claude Cowork
Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.
New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.
Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.
In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.
Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.
In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.
- 04
Sign in and use Salesforce Platform from Claude Cowork
The first time Claude Cowork connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
Salesforce Platform needs its own OAuth grant, so each person connects it once. Until they do, Salesforce Platform calls fail while the rest of the gateway keeps working.
From then on, Salesforce Platform's tools appear in Claude Cowork, limited to what the person's access allows, and every call lands in the gateway's tool logs.
Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.
Use cases
What Claude Cowork users do with Salesforce Platform
Rebalance sales territories
Cowork reads every account and open opportunity by region, compares workload across reps, and drafts a proposed territory split with the reasoning for each move.
Prepare an account handover pack
When a rep leaves, Cowork gathers each account's contacts, open opportunities and recent activity from Salesforce and writes a handover note per account.
Review stale opportunities for owners
Find opportunities with no activity for months, read each one's history, and write a list for every owner of the deals that look lost and the ones worth another call.
Control
What Speakeasy can see and stop in Claude Cowork
The gateway covers every client the same way. The rest depends on what Claude Cowork exposes to Speakeasy.
Tool logs
Gateway
Every Salesforce Platform call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Salesforce Platform tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Salesforce Platform can reject a tool request before it reaches the server, or withhold a result from Claude Cowork. MCP-scoped policies are enabled per organization.
Prompt blocking
Claude Cowork
Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.
Session telemetry
Claude Cowork
Cowork's OTLP export ties sessions to people and feeds observability.
Anthropic inference hooks
Claude Cowork
On Claude Enterprise, prompts can be checked before inference (beta).
- Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
- Personal Claude accounts can't be governed in Cowork.
Questions
Frequently asked questions
What does a Salesforce admin need before Cowork can connect?
Can Cowork's Salesforce steps be blocked?
How do Claude Cowork users get Salesforce Platform?
Are Salesforce Platform calls from Claude Cowork logged?
Connect more