PagerDuty MCP Server

✓ verified

Read incidents, services, and on-call schedules from PagerDuty.

Don't have ToolPiper? We'll take you to the download.

Open repository →

Publisher

PagerDuty

License

Apache-2.0

Transport

Local subprocess

Tools

5

What this server does

PagerDuty's MCP server lets the assistant answer the questions you ask during an incident: what is firing, who is on call, which service owns it, and what the recent history looks like. It is read-only by default, so it cannot acknowledge or resolve incidents unless you explicitly launch it with write tools enabled. Pair it with a Sentry or Grafana server and the model can correlate an alert with its underlying error and dashboards.

Tools included

  • list_incidents

    List incidents with optional status and service filters.

  • get_incident

    Read details of a single incident.

  • list_services

    List configured services.

  • list_oncalls

    Show who is currently on call.

  • list_schedules

    List on-call schedules.

The authoritative list comes from the server's tools/list at runtime. This catalog entry may lag the upstream until the next ToolPiper release.

Install in ToolPiper

ToolPiper handles the JSON configuration. Click Install, fill in any required tokens, and the server is ready in your chat.

Don't have ToolPiper? We'll take you to the download.

Install in another client

Install in another MCP client (Claude Desktop, Cursor, Continue, Cline)

Add this to ~/Library/Application Support/Claude/claude_desktop_config.json.

{
  "mcpServers": {
    "pagerduty": {
      "command": "uvx",
      "args": [
        "pagerduty-mcp"
      ]
    }
  }
}

Example prompts

  • "What incidents are currently open and which services do they affect?"

  • "Who is on call for the payments service right now?"

  • "Summarize the incidents from the last 24 hours by service."

Security notes

The user API token can read everything your PagerDuty user can see, which includes incident details and contact info. It is read-only unless the server is started with --enable-write-tools, so by default an attacker with the token cannot change on-call or resolve incidents. Treat the token like a password and rotate it from User Settings if it leaks.

Related tools