MCP Gateway · Codex
Connect Amplitude to Codex
Flags and experiments decide what users see, and cleaning them up is code work. With Amplitude behind the Speakeasy MCP Gateway, Codex can read an experiment's results before you delete the losing branch, adjust a flag's testers and deployments, and find which users hit an event. An [otel] block in Codex's config sends telemetry to Speakeasy so each call is attributed.
- Category
- Data & analytics
- Tools
- 44
- Authentication
- OAuth
- Codex
- CLI and ChatGPT desktop app
Behind the MCP Gateway
Run Amplitude MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Amplitude call inspected and logged.
Before you start
What Amplitude needs first
An Amplitude organization admin does the Amplitude side of the setup.
- There is nothing to create in Amplitude. Users sign in with their own accounts and keep their existing permissions.
- US and EU organizations use different server URLs, and the two are not interchangeable.
- Custom roles need Use MCP (read) enabled, or MCP calls fail for that role.
In Amplitude
- Find your data region from the Amplitude hostname and record the matching server URL.
- In Settings, Content Access > MCP, confirm the MCP server is allowed.
- For custom roles, enable Use MCP (read), and Use MCP (write) only if needed.
Set up
Add Amplitude to Codex in 4 steps
- 01
Add Amplitude from the catalog
An admin finds Amplitude 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.
Amplitude 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 Amplitude
Give teams the
mcp:connectscope on the Amplitude server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Amplitude 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 Amplitude from Codex
The first time Codex connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
Amplitude needs its own OAuth grant, so each person connects it once. Until they do, Amplitude calls fail while the rest of the gateway keeps working.
From then on, Amplitude'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 Amplitude
Read results before removing a variant
Before Codex deletes the code for an experiment's losing variant, it queries the experiment analysis and links to it in the pull request, so reviewers can check the data themselves.
Add QA testers to a flag
Ask Codex to add your QA accounts as testers on a feature flag, or attach the flag to another deployment, without switching to the Amplitude UI between commits.
Find users who hit an event
When an error event spikes, Codex confirms the exact event name, pulls the users who performed it along with their session replays, and uses them to narrow down the failing path.
Tools
44 tools
Each Amplitude tool can be allowed or denied per team and role at the MCP Gateway before Codex sees it.
get_charts
Retrieve full chart objects by their IDs using the chart service directly
save_chart_edits
Save temporary chart edits as permanent charts
get_cohorts
Get detailed information about specific cohorts by their IDs.
create_cohort
Create a new cohort with the provided definition and configuration.
get_context
Get information about the current user, organization, and list of accessible projects.
get_project_context
Get project-specific settings and configuration for a specific project.
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 Amplitude call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Amplitude tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Amplitude 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
Are Codex cloud tasks covered for Amplitude calls?
Does it matter whether our Amplitude organization is in the US or EU?
How do Codex users get Amplitude?
Are Amplitude calls from Codex logged?
Connect more