PagerDuty MCP: Documentation
Updated:
Connection
- Hosted remote:
https://mcp.pagerduty.com/mcp. - Local:
uvx pagerduty-mcp(stdio; HTTP/SSE modes are also available), write access enabled via the--enable-write-toolsflag.
Auth: a User API Token from your PagerDuty profile (Settings → User Settings → API Access).
Tools
55 tools across areas: incidents (create, assign, resolve), on-call schedules (oncalls), escalation policies, event orchestrations (alert routing) and status pages. Without --enable-write-tools, only read operations are available.
Agent flow
"Who's on call for the production service, and are there open incidents?", "create an incident from this alert and assign it to whoever's on call", "show the escalation policy for the Payments service".
Limits
Write access (creating and changing incidents) requires the explicit --enable-write-tools flag — without it the server only reads data. Permissions depend on the role of the user whose API token is used.
Pricing
The MCP server is free; access to PagerDuty data follows your plan (Free/Professional/Business/Digital Operations).