Skip to content
PagerDuty MCP

PagerDuty MCP

by PagerDuty
Released
Repository Docs
Developer Tools

Summary

PagerDuty's official MCP server with 80+ tools for incidents, schedules, services and escalation policies — read-only by default, with write actions behind an explicit flag.

Features

  • 80+ tools across incidents, schedules, services and escalation policies
  • Read-only by default; writes require --enable-write-tools
  • On-call lookup and schedule override management
  • Event orchestration inspection and rule updates
  • Incident metrics and responder-load analytics
  • stdio, streamable HTTP and SSE transports
  • US and EU API hosts; hosted variant at mcp.pagerduty.com

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it, filling in the environment variables with your own values.
  3. Restart the agent — the "PagerDuty MCP" tools will be available.
{
  "mcpServers": {
    "pagerduty-mcp": {
      "command": "uvx",
      "args": [
        "pagerduty-mcp"
      ],
      "env": {
        "PAGERDUTY_USER_API_KEY": "your-user-api-token"
      }
    }
  }
}

Description

During an incident the operational context you need is scattered across PagerDuty: who is on call for the affected service, what the escalation policy does next, whether this has fired before, which orchestration rule routed it here. PagerDuty's official MCP server puts all of it in front of an agent, and — importantly — makes it read it before it can change anything.

Tool surface (80+ tools):

  • Incidents — create, retrieve, list and filter; change status, urgency and assignment; add notes and pull in additional responders.
  • Schedules and on-call — list schedules, resolve who is on call right now, create and manage overrides.
  • Services — full create, read, update and list.
  • Event orchestrations — inspect routing configuration and update rules, which is where "why did this page the wrong team" usually gets answered.
  • Escalation policies, teams and users — complete CRUD.
  • Analytics — incident metrics and responder-load data, useful for on-call fairness reviews.
  • Webhooks and integrations — subscription management.

The safety default is the design decision worth noting. Only read-only tools are enabled unless you start the server with --enable-write-tools. An agent connected with defaults can investigate an incident thoroughly and cannot acknowledge, reassign or resolve anything. Turning on writes is a deliberate, visible act in your client configuration.

The server also ships interactive React UIs for incident management, on-call scheduling, compensation reporting, service dependencies and account onboarding, for clients that can render them.

Install: it is a Python package run through uvx pagerduty-mcp. Authentication uses a PagerDuty User API Token — created under User Settings → API Access → Create API User Token — passed as PAGERDUTY_USER_API_KEY. EU-region accounts must also set PAGERDUTY_API_HOST to https://api.eu.pagerduty.com; the default is the US host. Transports supported are stdio (default), streamable HTTP and SSE, and PagerDuty additionally offers a hosted variant at mcp.pagerduty.com/mcp.

Because the token is a user token, the agent inherits exactly that user's permissions — scope the account accordingly.

Related MCP Servers

MCP: Rootly

by Rootly

Rootly's official MCP server for incident management and on-call — declare and update incidents, page the right responder, and pull timelines and retrospectives into an agent session.

Cloud & Infrastructure
Browse all MCP servers →