PagerDuty

Investigate incidents, manage on-call coverage, administer services and teams, and run incident-response workflows through PagerDuty’s hosted MCP server, without installing a local server.

See the official PagerDuty MCP documentation for setup, authentication, and regional endpoint details.

PagerDuty region: Enter mcp.pagerduty.com for accounts hosted in the United States or mcp.eu.pagerduty.com for accounts hosted in Europe.

Features

• Incident response: Investigate alerts, notes, related incidents, and change events; create, update, and resolve incidents.
• On-call operations: View schedules and on-call assignments, manage overrides, and coordinate handoffs.
• Service administration: Manage services, teams, escalation policies, event orchestrations, alert grouping, and status pages.
• Operational intelligence: Analyze incident and responder metrics, business-service dependencies, log entries, and change events.

What you’ll need to connect

• PagerDuty account: Choose the region where your PagerDuty account is hosted.
• PagerDuty API key: Create a PagerDuty User API token in My Profile > User Settings > API Access, then enter it when prompted.

The server authenticates requests with your PagerDuty API key. Use a User API token so the server can act with your PagerDuty permissions; some filters require user-level authentication.

Store your API key securely and rotate it if it is exposed.

⚠️ Upgrade notice

If you’re upgrading this server, note that this replaces the Obot-hosted PagerDuty server with PagerDuty’s official hosted MCP server.

• Reconnect required: Select the PagerDuty US or EU hosted endpoint and provide a PagerDuty User API token.
• Configuration change: The previous API-host setting is replaced by a hosted-server region selection.
• Tool changes: Tool names, parameters, and the available incident-response and administration operations change.