MCP Gateway · Codex
Connect Salesforce Platform to Codex
Codex can take on Salesforce integration tickets end to end, checking CRM data as it changes the code that reads and writes it. It reaches Salesforce's hosted endpoints through the Speakeasy MCP Gateway, where agent hooks allow or deny each prompt and tool call, and budgets can block Codex traffic once a spend limit is reached.
- Category
- Sales & CRM
- Authentication
- OAuth
- Codex
- CLI and ChatGPT desktop app
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 Codex 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. The organization gateway works out each person's servers from their live access, so granting access adds Salesforce Platform to their gateway on the next call, and removing it takes it away. - 03
Connect Codex
Add the gateway as an MCP server, then log in.
Run the first command with your organization gateway URL.
Run the second command to sign in.
codex mcp add 'speakeasy' \ --url 'https://<organization host>/mcp/gateway/<organization slug>' codex mcp login 'speakeasy' - 04
Sign in and use Salesforce Platform from Codex
The first time Codex 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 Codex, limited to what the person's access allows, and every call lands in the gateway's tool logs.
To roll it out to a team, a ChatGPT workspace admin imports the plugin marketplace under Admin > Plugins and sets an installation policy per role. Imported plugins reach nobody until a policy is set.
Use cases
What Codex users do with Salesforce Platform
Confirm field names before a change
Before Codex edits code that maps your data to Salesforce, it reads sample CRM records so the field names and values in the change match what the org holds.
Reproduce a customer data bug
Give Codex the record a customer complained about. It reads the CRM data, works out which code path wrote it, and proposes a fix with a regression test.
Check a platform action after deploy
After shipping a change, have Codex invoke the platform action your service calls and confirm it still behaves as expected in the sandbox org.
Control
What Speakeasy can see and stop in Codex
The gateway covers every client the same way. The rest depends on what Codex 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 Codex. MCP-scoped policies are enabled per organization.
Prompt and tool-call blocking
Codex
Agent hooks send each prompt and tool call to Speakeasy, which allows or denies it before Codex runs it.
User attribution
Codex
An [otel] block in ~/.codex/config.toml sends telemetry to Speakeasy. Export is off by default.
Budgets
Codex
Spend limits can block Codex traffic once a budget is reached.
Device agent and MDM
Codex
The device agent keeps Codex's configuration in sync on managed laptops.
- Codex cloud tasks and GitHub code review run off the device. Neither the plugin nor OpenTelemetry covers them; OpenAI's Compliance Logs record them after the fact.
- The workspace rollout needs a ChatGPT Business, Enterprise or Edu admin.
Questions
Frequently asked questions
Who sets up Salesforce before Codex can use it?
Does Speakeasy see Salesforce calls from Codex cloud tasks?
How do Codex users get Salesforce Platform?
Are Salesforce Platform calls from Codex logged?
Connect more