AUTOMATIONSWITCH
OfficialMonitoring

PagerDuty MCP

by PagerDuty

Official PagerDuty MCP server for incident management, on-call schedules, services, escalation policies, and event API integration. 66 GitHub stars and 5 commits on main in the last 30 days. Apache-2.0.

66·8 tools·Released FEB 2026·Apache-2.0
pip install pagerduty-mcp-server
Share:

Official PagerDuty MCP server for incident management, on-call schedules, services, escalation policies, and event API integration. 66 GitHub stars and 5 commits on main in the last 30 days. Apache-2.0.

Reviewed by M. Nouriel · MAY 2026

INSTALL THIS SERVER

Requires authenticationPAGERDUTY_API_KEY environment variable. Token from PagerDuty Account Settings > API Access Keys.
{ "mcpServers": { "pagerduty": { "command": "python", "args": [ "-m", "pagerduty_mcp_server" ], "env": { "PAGERDUTY_API_KEY": "<your-pagerduty-api-key>" } } } }
PrereqRequires PAGERDUTY_API_KEY from PagerDuty Account Settings > API Access Keys. PyPI: `pagerduty-mcp-server`. Use a read-only key for diagnostic agents. Path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS).
{ "mcpServers": { "pagerduty": { "command": "python", "args": [ "-m", "pagerduty_mcp_server" ], "env": { "PAGERDUTY_API_KEY": "<your-pagerduty-api-key>" } } } }
{ "mcpServers": { "pagerduty": { "command": "python", "args": [ "-m", "pagerduty_mcp_server" ], "env": { "PAGERDUTY_API_KEY": "<your-pagerduty-api-key>" } } } }
{ "mcpServers": { "pagerduty": { "command": "python", "args": [ "-m", "pagerduty_mcp_server" ], "env": { "PAGERDUTY_API_KEY": "<your-pagerduty-api-key>" } } } }
{ "mcpServers": { "pagerduty": { "command": "python", "args": [ "-m", "pagerduty_mcp_server" ], "env": { "PAGERDUTY_API_KEY": "<your-pagerduty-api-key>" } } } }

8 TOOLS AVAILABLE

list_incidents
List incidents with filters (status, urgency, service)
Read
get_incident
Get incident details
Read
acknowledge_incident
Acknowledge an open incident
Write
resolve_incident
Resolve an incident
Write
list_oncall_schedules
List on-call schedules
Read
get_oncall_now
Get the current on-call user for a service
Read

OUR ASSESSMENT

Strengths
  • Official PagerDuty maintenance.
  • 66 GitHub stars and Apache-2.0 licence.
  • 5 commits on main in the last 30 days.
  • Tool surface covers incident lifecycle (list, get, acknowledge, resolve), on-call schedules, services, and Event API for triggering alerts.
  • Local MCP only (per official description): runs on the operator host, no remote MCP exposure.
Weaknesses
  • 66 GitHub stars; adoption is early.
  • PagerDuty API key grants account-wide read or write depending on key type.
  • Event API trigger surface can create real incidents; scope agent flows accordingly.
Security Notes

The MCP carries a PagerDuty API key with account-scoped access. Use a read-only key for diagnostic agents; reserve write keys for incident-response flows where the agent acknowledges or resolves issues. Avoid using a key that can trigger Event API alerts in test environments where false alerts would page real on-call engineers.

Best For

SRE and on-call teams using PagerDuty who want agents to triage incidents and check who is on call from inside the editor; incident response workflows where the agent acknowledges or resolves issues during investigation; ops automation that triggers PagerDuty alerts as part of a longer task.

TECHNICAL DETAILS

Language
python
Transport
stdio
Clients
Claude DesktopClaude CodeCursorVS CodeWindsurf
License
Apache-2.0
npm
pagerduty-mcp-server
Last Release
pagerduty-mcp-server (PyPI latest)MAY 3, 2026
First Released
FEB 1, 2026

ADOPTION METRICS

// GitHub Stars
66

// Reading this66 stars on the PagerDuty/pagerduty-mcp-server repo. 5 commits on main in the last 30 days. Official PagerDuty maintenance carries the editorial weight.

// Popularity Rank
#4
Globally · #4 in Monitoring

// Reading thisPairs with Datadog, Grafana, Prometheus in the monitoring category for incident triage and on-call lookup.

SOURCES & VERIFICATION

We don't take any single directory's word for it. Before scoring, we cross-reference 4 public MCP sources, install the server ourselves against the clients we cover, and record when we last re-verified.

01
Discovered
Manual submission
First indexed MAY 3, 2026
02
Cross-referenced
4 directories
PulseMCP, MCP.so, Glama, Official MCP Registry
03
Verified against
Claude Desktop, Cursor
Installed and tested across clients
04
Last re-checked
MAY 3, 2026
Weekly re-verification
// How other directories see it

The same server, 4 different lenses. We reconcile these signals into our editorial score, which is why our number sometimes diverges from a directory-aggregate star count.

SourceTheir ratingTheir star countTheir downloadsLast synced
AutomationSwitch This page4.1editorial66MAY 3, 2026
PulseMCP— unratedunavailableunavailableMAY 3, 2026
MCP.so— unratedunavailableunavailableMAY 3, 2026
Glama— unratedunavailableunavailableMAY 3, 2026
Official MCP Registry— unratedunavailableunavailableMAY 3, 2026

// Counts are directory-reported; we don't adjust them. Discrepancies usually come from different snapshot times or star-caching.

// Get in touch

DISCUSS YOUR
MCP REQUIREMENTS.

Evaluating a server, scoping an internal deployment, or working out whether MCP is the right fit at all. Start the conversation and we will point you at the right piece of the ecosystem.

Discuss Your MCP Requirements →