PagerDuty · Codex
Add the PagerDuty MCP server to Codex
Look up incidents, services, schedules and on-call, and act on incidents.
1. Add the server
Run in your terminal
# ~/.codex/config.toml [mcp_servers.pagerduty] command = "uvx" args = ["pagerduty-mcp", "--enable-write-tools"]
Scopes, env vars, OAuth and limits: Codex MCP config guide
2. Sign in
Run codex mcp login <name> to complete OAuth for a remote server. PagerDuty runs locally; set any credentials PagerDuty asks for before starting Codex.
3. Try it
Ask Codex for something PagerDuty can do. Look up incidents, services, schedules and on-call, and act on incidents. Approve the first tool call and check the result before allowing write actions automatically.
- · Each server is a [mcp_servers.<name>] table in config.toml.
- · Use enabled_tools or disabled_tools to keep the tool list short.
FAQ
- How do I add the PagerDuty MCP server to Codex?
- Run: # ~/.codex/config.toml …. Run codex mcp login <name> to complete OAuth for a remote server.
- Is this the official PagerDuty MCP server?
- Yes. It is published by PagerDuty as io.github.PagerDuty/pagerduty-mcp in the official MCP registry.
- Does the PagerDuty MCP server need an API key?
- It runs locally from a package. See PagerDuty's docs for any credentials it needs.
Links
PagerDuty in other clients
More observability & incidents for Codex
Built an MCP server? Get it listed everywhere →
Shipping an Android app? Google Play needs 12 testers for 14 days first. Get them with Tester Exchange →
Reviewed Oct 21, 2026. Command generated from the registry record and checked against Codex's documented syntax.