PagerDuty MCP server

Last verified: 2026-09

Incidents and on-call.

Community Cloud & infra Needs a secret Claude Desktop, Cursor, Windsurf, Claude Code

What it does

PagerDuty's official MCP (hosted at mcp.pagerduty.com/mcp or local). Incidents, services, schedules, event orchestrations. The CrowdStrike URL we had listed was the wrong repo.

It sits in Cloud & infra: Most of these are admin APIs.

Good for

List open incidents without resolving them.
See who is on-call on a schedule.
Prefer hosted mcp.pagerduty.com/mcp plus OAuth over a laptop key.
Do not resolve a paging incident from a 'test' chat.

Tools

incidents / services / schedules / on-call — Read and update paging state. Exact names are in the official README.

Config (Claude Desktop / Cursor / Windsurf)

Paste the JSON below. Same mcpServers shape. Replace placeholder paths and secrets. Windows paths look like C:\\Users\\you\\project, not /path/to. Host-side steps →

Claude Desktop

OS	Config file
macOS	`~/Library/Application Support/Claude/claude_desktop_config.json`
Windows	`%APPDATA%\Claude\claude_desktop_config.json` (usually `C:\Users\<you>\AppData\Roaming\Claude\`)
Linux	`~/.config/Claude/claude_desktop_config.json`

Cursor

Scope	macOS / Linux	Windows
This project	`.cursor/mcp.json` in the repo root
This user	`~/.cursor/mcp.json`	`%USERPROFILE%\.cursor\mcp.json`

Windsurf

OS	Config file
macOS / Linux	`~/.codeium/windsurf/mcp_config.json`
Windows	`%USERPROFILE%\.codeium\windsurf\mcp_config.json`

{
  "mcpServers": {
    "pagerduty": {
      "command": "npx",
      "args": [
        "-y",
        "pagerduty-mcp-server"
      ],
      "env": {
        "PAGERDUTY_API_KEY": "..."
      }
    }
  }
}

Windsurf remote MCP: use serverUrl instead of url if the block below is HTTP.

One-liner: npx -y pagerduty-mcp-server

Secrets it wants: PAGERDUTY_API_KEY

Source repo →

How to get started

Prefer the hosted server and OAuth, or a user API key on the local server.
List incidents first. Do not resolve a paging incident from a laptop test.
EU: mcp.eu.pagerduty.com/mcp.

Access risk

Ack/resolve/reassign changes who wakes up. A key is the PagerDuty user.

When to skip it

Skip it if you only needed Slack, or if Datadog already pages and you do not sit in PagerDuty.

Instead: Datadog, Slack, Grafana.

Cloud & infraDatadogMetrics, logs, and monitors. OfficialSlackRead channels and post messages. Cloud & infraGrafanaDashboards and datasources.

Vs alternatives

Server	Official?	Needs a secret?	Best for
PagerDuty	No	Yes	Incidents and on-call.
Datadog	No	Yes	Metrics, logs, and monitors.
Slack	Yes	Yes	Read channels and post messages.
Grafana	No	Yes	Dashboards and datasources.

More in Cloud & infra

OfficialAWS Knowledge BaseQuery an Amazon Bedrock knowledge base. Cloud & infraAWSCall AWS APIs with the default credential chain. Cloud & infraAzureAzure Resource Manager via MCP. Cloud & infraCloudflareWorkers, KV, R2, and DNS via Cloudflare.

All 15 in this category →

FAQ

We had the wrong GitHub URL?

Yes. The live official repo is PagerDuty/pagerduty-mcp-server. Hosted: mcp.pagerduty.com/mcp (EU: mcp.eu.pagerduty.com/mcp).

Ack/resolve?

That changes who wakes up. A key is the PagerDuty user. Read first.

PagerDuty or Slack?

PagerDuty is paging. Slack is chat. A Slack write token is not an on-call tool.

Hosted or local?

Hosted + OAuth is less laptop-secret. Local uses a user API key.