MCP Gateway · OpenCode
Connect Salesforce Platform to OpenCode
Salesforce developers and admins who script from the terminal can use OpenCode to query CRM data and invoke platform actions without switching to Setup. The OpenCode plugin sends each prompt and tool call to Speakeasy, which allows or denies it before it runs, so a write to a production org can be refused.
- Category
- Sales & CRM
- Authentication
- OAuth
- OpenCode
- Terminal
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 OpenCode 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. OpenCode 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 OpenCode
Add the server to OpenCode's own mcp config block as a remote server.
Copy the server's URL from its hosted install page in Speakeasy.
Add it to the
mcpblock of your OpenCode config withtypeset toremote.Restart OpenCode and sign in when prompted.
{ "mcp": { "<server slug>": { "type": "remote", "url": "<URL from the hosted install page>" } } } - 04
Sign in and use Salesforce Platform from OpenCode
The first time OpenCode 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 OpenCode, limited to what the person's access allows, and every call lands in the gateway's tool logs.
OpenCode doesn't receive MCP servers from plugins. The observability package is installed separately, from a ZIP or with speakeasy-hooks install --provider=opencode, and the device agent can maintain it.
Use cases
What OpenCode users do with Salesforce Platform
Check data before a migration script
Before running a data migration, ask OpenCode to read a sample of the affected CRM records and confirm the script's assumptions about their fields hold.
Spot-check records after a bulk load
After a bulk import, OpenCode reads a handful of the new records and compares them with the source file, so you catch mapping errors early.
Run a platform action from the shell
Invoke a Salesforce platform action from OpenCode to rerun a failed automation for one record, without clicking through the Salesforce interface.
Control
What Speakeasy can see and stop in OpenCode
The gateway covers every client the same way. The rest depends on what OpenCode 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 OpenCode. MCP-scoped policies are enabled per organization.
Prompt and tool-call blocking
OpenCode
The OpenCode plugin sends each prompt and tool call to Speakeasy, which allows or denies it before it runs.
Usage telemetry
OpenCode
Token and cost totals flow through the plugin, reported per turn.
Device agent
OpenCode
The device agent installs and maintains the observability package.
- OpenCode has no OpenTelemetry exporter, so session data comes through the plugin.
- Tool output is blocked at the gateway rather than in OpenCode's hooks.
Questions
Frequently asked questions
Does installing Speakeasy's Salesforce app finish the connection?
Where does OpenCode get the Salesforce server URL?
How do OpenCode users get Salesforce Platform?
Are Salesforce Platform calls from OpenCode logged?
Connect more