Incident triage, responders and status updates handled against live PagerDuty data.
On-call engineers get an incident's context in one place, including alerts, notes, recent changes and similar past incidents, and can bring in responders or post a status update without switching tools.
What it is
A remote MCP server PagerDuty hosts at mcp.pagerduty.com/mcp, with a separate address for EU accounts. Nothing is installed on your machine. It replaces PagerDuty's older self-hosted server, which is now deprecated and archived.
What you get
- Incidents listed and opened, with their alerts, notes, related and past incidents, and recent change events
- Incidents created and updated, notes added, responders brought in, and incident workflows started
- On-call schedules and who is on call now, plus schedule changes and overrides
- Services, teams, escalation policies and users looked up; services and teams created or changed
- Event orchestration routing and alert grouping rules read and changed
- Status page posts and updates read and published
- Your account's activity log read
Requirements
A PagerDuty account with Advanced Permissions. You connect with a PagerDuty User API key, or with an OAuth client you create in PagerDuty first. EU accounts use mcp.eu.pagerduty.com, and some filters, such as incidents assigned to you, need a user-level key. You cannot switch individual tools off on the hosted server; to limit what succeeds, connect with a scoped OAuth client.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen