PagerDuty MCP Server
Connect AI agents to PagerDuty incidents, on-call schedules, and escalations over MCP.
Updated
What is PagerDuty MCP?
The PagerDuty MCP server is a Model Context Protocol server that lets AI assistants and agents securely interact with your PagerDuty account — retrieving incident data, managing services, and reading or updating on-call schedules on your behalf.
PagerDuty offers it in two forms. The PagerDuty-hosted remote server lives at https://mcp.pagerduty.com/mcp (EU accounts use https://mcp.eu.pagerduty.com/mcp) and authenticates with OAuth, so there's no local install — you connect your MCP client and log in to PagerDuty. There's also an open-source self-hosted build you can run locally via uvx or Docker using a PagerDuty User API token.
The server exposes roughly 55 tools across 14 domains — incidents, services, on-call schedules, teams, escalation policies, event orchestrations, status pages, and more. It runs in read-only mode by default; write actions (such as creating or resolving incidents and editing schedules) must be explicitly enabled, which keeps an agent's access conservative until you opt in.
Tools the PagerDuty MCP server exposes
| Tool | What it does |
|---|---|
| list_incidents | List incidents in your PagerDuty account with filters. |
| get_incident | Retrieve details for a specific incident. |
| create_incident | Create a new incident (write mode). |
| manage_incidents | Acknowledge, resolve, or update incident state (write mode). |
| add_note_to_incident | Add a note to an incident (write mode). |
| list_oncalls | List who is currently on call across schedules. |
| list_schedules | List on-call schedules. |
| create_schedule_override | Create a temporary on-call override for a schedule (write mode). |
| list_services | List PagerDuty services. |
| list_event_orchestrations | List event orchestrations that route and group events. |
Connect the PagerDuty MCP server
Claude Code (hosted, OAuth)
- 1
Add the remote server
Run: claude mcp add --transport http pagerduty https://mcp.pagerduty.com/mcp (use https://mcp.eu.pagerduty.com/mcp for EU accounts).
- 2
Authenticate with OAuth
Start Claude Code and trigger the PagerDuty server; complete the browser OAuth login to your PagerDuty account when prompted.
- 3
Use it (read-only by default)
Ask Claude about incidents or on-call schedules. The server is read-only unless write tools are enabled.
Prefer self-hosting? Run the open-source build with uvx pagerduty-mcp and a PAGERDUTY_USER_API_KEY env var instead.
Cursor (hosted, OAuth)
- 1
Open MCP settings
In Cursor, go to Settings > MCP and add a new server.
- 2
Add the remote URL
Add an HTTP/SSE server pointing to https://mcp.pagerduty.com/mcp (EU: https://mcp.eu.pagerduty.com/mcp).
- 3
Complete OAuth login
Cursor opens the PagerDuty OAuth flow; sign in to authorize. Tools then appear in the agent.
No local install needed for the hosted server. For self-hosting, configure uvx pagerduty-mcp with PAGERDUTY_USER_API_KEY.
Security & permissions
The hosted PagerDuty MCP server uses OAuth: you authorize the connection against your PagerDuty account, so the agent acts within your PagerDuty permissions rather than via a shared static key. The self-hosted build instead uses a PagerDuty User API token (PAGERDUTY_USER_API_KEY). In both modes the server is read-only by default — write-capable tools (creating/resolving incidents, editing schedules, etc.) are only available when explicitly enabled (e.g. the --enable-write-tools flag on the self-hosted build). The agent's reach is bounded by the connected user's PagerDuty role and permissions, so scope that user appropriately.
Using PagerDuty MCP with Gamut
In a Gamut workflow, a Model Context Protocol agent can use the PagerDuty MCP server as a connected tool inside an automated, event- or schedule-triggered run — Gamut manages the OAuth connection so the agent can read incidents, on-call schedules, and service status without you handling tokens. For example, on an incident webhook or a recurring schedule, an agent can pull the active incident, summarize its alerts and current on-call responder, and (when write tools are enabled) acknowledge, add a note, or resolve it. Keep the connection read-only unless a workflow specifically needs to modify PagerDuty.
Frequently asked questions
What is the PagerDuty MCP server?
It's a Model Context Protocol server from PagerDuty that lets AI assistants and agents securely interact with your PagerDuty account — reading incidents, services, and on-call schedules, and (when write tools are enabled) acting on them. It comes as a PagerDuty-hosted OAuth server and an open-source self-hosted build.
Is the PagerDuty MCP server free?
Yes. The PagerDuty MCP server is open source and free to use; you just need a PagerDuty account. Support is community-based via GitHub and the PagerDuty community forum.
How do I connect the PagerDuty MCP server to Claude or Cursor?
Point your MCP client at the hosted remote server https://mcp.pagerduty.com/mcp (EU: https://mcp.eu.pagerduty.com/mcp) and complete the OAuth login. In Claude Code, add it with claude mcp add --transport http; in Cursor, add it as an HTTP server under Settings > MCP. No local install is required for the hosted option.
Is the PagerDuty MCP server hosted or self-hosted?
Both. PagerDuty provides a managed hosted server at mcp.pagerduty.com/mcp that authenticates with OAuth, and an open-source self-hosted build you can run locally with uvx or Docker using a PagerDuty User API token.