MCP Gateway · Codex
Connect PagerDuty to Codex
Codex is useful for PagerDuty work that is closer to configuration than to firefighting. It can match deploys to the incidents that followed, add a routing rule to an event orchestration, and register a new service with an escalation policy. Agent hooks send each prompt and PagerDuty tool call to Speakeasy before Codex runs it.
- Category
- Infrastructure
- Tools
- 64
- Authentication
- API key
- Codex
- CLI and ChatGPT desktop app
Behind the MCP Gateway
Run PagerDuty MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every PagerDuty call inspected and logged.
Set up
Add PagerDuty to Codex in 4 steps
- 01
Add PagerDuty from the catalog
An admin finds PagerDuty 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.
PagerDuty authenticates with an API key. Enter it under Upstream headers in the install dialog, or later on the server's Settings tab. The key is stored on the server, sent with every upstream request, and never reaches anyone's client configuration.
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 PagerDuty
Give teams the
mcp:connectscope on the PagerDuty server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds PagerDuty 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 PagerDuty from Codex
The first time Codex connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
From then on, PagerDuty'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 PagerDuty
Match a deploy to an incident
Codex lists the change events for a service around the time an incident opened, so you can tell whether a recent deploy is the likely cause.
Add an event routing rule
When a new alert source needs to reach a different service, Codex reads the event orchestration's router and appends a rule to the end of it.
get_event_orchestration_routerappend_event_orchestration_router_rule
Register a new service
For a new microservice, Codex finds the right escalation policy and creates the PagerDuty service that will receive its alerts.
Tools
64 tools
Each PagerDuty tool can be allowed or denied per team and role at the MCP Gateway before Codex sees it.
list_alert_grouping_settings
List all alert grouping settings with optional filtering.
get_alert_grouping_setting
Get details for a specific alert grouping setting.
list_alerts_from_incident
List alerts for a specific incident.
get_alert_from_incident
Get a specific alert from an incident.
list_change_events
List all change events with optional filtering.
get_change_event
Get details about a specific change event.
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 PagerDuty call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the PagerDuty tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to PagerDuty 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
Do Codex cloud tasks that touch PagerDuty go through Speakeasy's checks?
Is PagerDuty data inspected before it reaches Codex?
How do Codex users get PagerDuty?
Are PagerDuty calls from Codex logged?
Connect more