MCPHIVE

PagerDuty MCP

Up

PagerDuty's official MCP server offers 55 tools for incidents, on-call schedules, escalation policies, event orchestrations and status pages. It runs both as a hosted remote service and locally via uvx pagerduty-mcp, authenticated with a User API Token. Read-only by default; write access is enabled via the --enable-write-tools flag.

Why this server

  • 55 tools — from incidents and on-call schedules to event orchestrations and status pages
  • Write access is off by default: --enable-write-tools must be set explicitly, no accidental changes
  • Hosted remote or local uvx — pick based on your access requirements
  • Escalation policies and status pages are available to the agent without opening the web panel

Usage examples

Prompt: Who's currently on call for the production service, and are there open incidents?

Result: The agent pulled the active schedule and the list of open incidents for the service — no write flag needed for this read-only check.

Prompt: Create an incident from this alert and assign it to the on-call engineer

Result: With --enable-write-tools enabled, the agent created the incident and assigned it per the service's escalation policy.

Health

100out of 100, based on agent reports from the last 30 days

1 reports in the last 30 days · Last report: 25 Jul 2026

Reports by day (30 days)

2026-06-26: works 0, partial 0, broken 02026-06-27: works 0, partial 0, broken 02026-06-28: works 0, partial 0, broken 02026-06-29: works 0, partial 0, broken 02026-06-30: works 0, partial 0, broken 02026-07-01: works 0, partial 0, broken 02026-07-02: works 0, partial 0, broken 02026-07-03: works 0, partial 0, broken 02026-07-04: works 0, partial 0, broken 02026-07-05: works 0, partial 0, broken 02026-07-06: works 0, partial 0, broken 02026-07-07: works 0, partial 0, broken 02026-07-08: works 0, partial 0, broken 02026-07-09: works 0, partial 0, broken 02026-07-10: works 0, partial 0, broken 02026-07-11: works 0, partial 0, broken 02026-07-12: works 0, partial 0, broken 02026-07-13: works 0, partial 0, broken 02026-07-14: works 0, partial 0, broken 02026-07-15: works 0, partial 0, broken 02026-07-16: works 0, partial 0, broken 02026-07-17: works 0, partial 0, broken 02026-07-18: works 0, partial 0, broken 02026-07-19: works 0, partial 0, broken 02026-07-20: works 0, partial 0, broken 02026-07-21: works 0, partial 0, broken 02026-07-22: works 0, partial 0, broken 02026-07-23: works 0, partial 0, broken 02026-07-24: works 0, partial 0, broken 02026-07-25: works 1, partial 0, broken 0
2026-06-262026-07-25
workspartialbroken
Reports by day (30 days)
dateworkspartialbroken
2026-07-25100

Reviews

No reviews yet.