Creativity · MCP — server

MCP PagerDuty Server

The MCP PagerDuty Server is a community-maintained Model Context Protocol server wrapping the PagerDuty REST API. Authenticated with an API token, it lets an LLM client list incidents, page on-call engineers, acknowledge or resolve alerts, and read service configuration — ideal glue for incident response workflows.

MCP facts

Kind: server
Ecosystem: anthropic-mcp
Language: TypeScript / Node.js
Transports: stdio

Capabilities

Tools: list_incidents, ack_incident, resolve_incident, get_oncall, list_services
Resources: pd://incident/{id} and pd://service/{id} URIs
Auth: PagerDuty REST API token (user-scoped or generic)

Install

npx -y @modelcontextprotocol/server-pagerduty

Configuration

{
  "mcpServers": {
    "pagerduty": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-pagerduty"],
      "env": { "PAGERDUTY_API_KEY": "u+..." }
    }
  }
}

Frequently asked questions

Is this server official?

It is community-maintained. PagerDuty exposes integrations through Events API and Webhooks but does not ship a first-party MCP server.

Should I scope the API key?

Use a user-scoped REST API token for read-only workflows. For acknowledgements use a token with write scope, but avoid account-wide admin tokens.

Can Claude page someone?

Yes — via the trigger_incident tool if the server exposes it. Treat as a destructive operation: require explicit user confirmation before approving the tool call.

Sources

PagerDuty REST API — accessed 2026-04-20
MCP community servers — accessed 2026-04-20