PagerDuty MCP Server for Claude

Content

PagerDuty MCP Server is PagerDuty's official Model Context Protocol server for connecting AI assistants to PagerDuty operational data. It gives Claude, Cursor, VS Code, and other MCP clients a structured way to inspect incident context, on-call schedules, services, teams, escalation policies, event orchestrations, log entries, status pages, and related incident-response resources.

Use it as an incident-response and SRE context bridge, not as an unattended automation bot. Start with the hosted remote endpoint or the local server's default read-only mode, keep the connected identity narrow, and enable write tools only for workflows where a human will review proposed operational changes before they land in PagerDuty.

Features

• Official PagerDuty MCP Server documented by PagerDuty.
• PagerDuty-hosted remote HTTP endpoint at https://mcp.pagerduty.com/mcp.
• EU hosted endpoint at https://mcp.eu.pagerduty.com/mcp.
• Local stdio server available through the official GitHub repository and uvx pagerduty-mcp.
• Docker option for running the local server as a container.
• Authentication support for PagerDuty API keys, user API tokens, and OAuth flows depending on the chosen server and client.
• Read-only default for local setup, with write tools gated behind --enable-write-tools.
• Tools for incidents, alerts, schedules, on-call assignments, services, teams, users, escalation policies, change events, log entries, incident workflows, event orchestrations, alert grouping, and status pages.
• Tool filtering guidance for local setups through mcp-proxy.
• Embedded MCP apps in the official repository for incident command, on-call management, compensation reporting, service dependency graphs, and onboarding experiments.

Use Cases

• Ask Claude to summarize active incidents, affected services, notes, alerts, and recent changes before an incident handoff.
• Check who is currently on call for a service or schedule before paging or escalating a response plan.
• Review escalation policies, responder context, and service ownership during production triage.
• Compare a service's incident history, related incidents, change events, and log entries while debugging a recurring outage.
• Draft a status-page update from incident context, then require a human to review and publish it.
• Use local tool filtering to expose only incident, on-call, or service-health tools for a focused SRE workflow.
• Inspect event orchestration rules before proposing routing changes for noisy alerts.

Installation

Claude Code remote

For the PagerDuty-hosted remote server:

claude mcp add --transport http pagerduty https://mcp.pagerduty.com/mcp

For an EU region account:

claude mcp add --transport http pagerduty https://mcp.eu.pagerduty.com/mcp

If using an API key instead of OAuth, pass the token through your client's approved secret flow. PagerDuty's remote setup examples use a token header:

PAGERDUTY_API_KEY=<PAGERDUTY_API_KEY> claude mcp add-json pagerduty '{"type":"http","url":"https://mcp.pagerduty.com/mcp","headers":{"Authorization":"Token token=${PAGERDUTY_API_KEY}"}}'

Codex local stdio

For local stdio setup, pin the package version after checking the current PagerDuty docs and package metadata:

[mcp_servers.pagerduty-mcp-server]
command = "uvx"
args = ["pagerduty-mcp==0.17.0"]

[mcp_servers.pagerduty-mcp-server.env]
PAGERDUTY_USER_API_KEY = "<PAGERDUTY_USER_API_KEY>"
PAGERDUTY_API_HOST = "https://api.pagerduty.com"

For EU accounts, set PAGERDUTY_API_HOST to https://api.eu.pagerduty.com.

Local write tools

Only add --enable-write-tools after reviewing the write surface and approval flow:

{
  "mcpServers": {
    "pagerduty-mcp": {
      "type": "stdio",
      "command": "uvx",
      "args": ["pagerduty-mcp==0.17.0", "--enable-write-tools"],
      "env": {
        "PAGERDUTY_USER_API_KEY": "<PAGERDUTY_USER_API_KEY>",
        "PAGERDUTY_API_HOST": "https://api.pagerduty.com"
      }
    }
  }
}

Tool Surface

The current PagerDuty tools reference documents 64 tools across 14 domains: 42 read-only tools and 22 write tools. Read-only tools cover incident lookup, alert lookup, service lookup, schedules, current on-call assignments, teams, users, escalation policies, event orchestrations, change events, log entries, incident workflows, alert grouping, and status pages.

Write tools are intentionally opt-in for the local server. They include incident creation and management, responder additions, incident notes, incident workflow starts, service updates, team changes, schedule overrides, event orchestration routing changes, alert grouping changes, and status-page posts or updates.

Examples

Incident handoff

Use PagerDuty MCP in read-only mode. Summarize active incidents for service <SERVICE_ID>, including severity, current assignee, notes, recent alerts, and related change events.

On-call context

List the current on-call responders for schedule <SCHEDULE_ID> and show the next escalation policy step. Do not page or reassign anyone.

Status update draft

Draft a customer-facing status-page update for incident <INCIDENT_ID> from PagerDuty context. Show the text for approval before using any write tool.

Event orchestration review

Inspect event orchestration <ORCHESTRATION_ID> and explain which rules are likely routing noisy alerts. Do not change routing rules.

Source Notes

• PagerDuty's knowledge-base page describes the PagerDuty MCP Server as an open standard that lets AI assistants such as Claude Desktop, Cursor, and VS Code interact securely with a PagerDuty account.
• PagerDuty documents two integration options: a PagerDuty-hosted service at mcp.pagerduty.com/mcp and a self-hosted open-source implementation.
• PagerDuty documents EU hosted configuration at https://mcp.eu.pagerduty.com/mcp and EU API host configuration through https://api.eu.pagerduty.com.
• The official developer docs describe remote setup with API-key and OAuth authorization, Cursor, VS Code, and Claude examples, and no local Python or uvx requirement for the hosted remote server.
• The official tools reference documents 64 tools across 14 domains, with 42 read-only tools available by default and 22 write tools requiring --enable-write-tools for local setup.
• PagerDuty's official GitHub repository describes the local MCP server, client setup, Docker setup, read-only defaults, write-tool flag, embedded MCP apps, and support through GitHub issues or the PagerDuty community forum.
• The PyPI package metadata checked at submission time showed pagerduty-mcp==0.17.0, package name io.github.PagerDuty/pagerduty-mcp, and Python requirement ~=3.12.0.

Duplicate Check

Checked current upstream/main, open PR titles, open PR changed files, source URLs, and content files for PagerDuty, PagerDuty MCP, pagerduty-mcp-server, pagerduty-mcp, mcp.pagerduty.com, mcp.eu.pagerduty.com, api.pagerduty.com, PagerDuty/pagerduty-mcp-server, and support.pagerduty.com/main/docs/pagerduty-mcp-server. No dedicated PagerDuty MCP Server entry, PagerDuty source URL duplicate, or open content PR for this server was found.

Editorial Disclosure

PagerDuty is a commercial incident-management and operations platform, but this listing is not sponsored, paid, affiliate-backed, or submitted by PagerDuty. Use PagerDuty's current docs, package metadata, account permissions, region requirements, privacy terms, and incident-management policies as the source of truth before connecting operational data to any AI client.