PagerDuty MCP

PagerDuty + AI - for Claude, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, and any agent that speaks MCP

Unofficial. Community-built Claude Code Skill and MCP server for the PagerDuty

API. Not affiliated with, endorsed by, or sponsored by PagerDuty, Inc.

▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.

Operate PagerDuty from your AI agent. Works with the AI you already use - ChatGPT (desktop app), Claude Desktop, Codex, Claude Code, Claude Cowork, and GitHub Copilot - plus Gemini CLI. Free, open source, runs on your laptop. Built for MSP owners. No code required.

Works with your agent

The six agents MSP owners actually use (self-serve, works today):

The ChatGPT desktop app runs pagerduty-mcp locally and shares MCP configuration with Codex (OpenAI). ChatGPT on the web needs a remote server, which msp-skills does not support yet. If your team works there, a hosted gateway is the better pick; check that your AI app is on the gateway's setup list.

Also for the Microsoft and Google stacks

Big install base, but an honest heads-up: Gemini CLI runs the local binary you just installed, while Microsoft 365 Copilot and the Gemini app need a remote server, which msp-skills does not support yet.

Skill-native agents (also covered): Hermes and OpenClaw read this skill's SKILL.md directly *and* speak MCP - see their install sections below. Also works with Cursor, Windsurf, Cline, Continue.dev, and Zed via MCP. Full per-tool wire-up: [docs/which-agent.md](../../docs/which-agent.md).

Run more than one agent? Install across all 51+ supported agents in one command: npx skills add Servosity/msp-skills@latest (requires Node.js, then run the per-skill installer for the CLI/MCP binaries). See docs/which-agent.md.

Install in 60 seconds

Fastest for Claude Desktop - one-click .mcpb

Claude Desktop bundle: the .mcpb launches on macOS (Intel and Apple Silicon), Windows x64 and Linux x64. Every tool shells out to the companion pagerduty-cli. Releases cut from 2026-09-18 on ship that CLI inside the bundle; older bundles contain only the MCP server, so if yours lacks the companion, run the Path A or Path B installer below first (or set PAGERDUTY_CLI_PATH to an existing binary). Details: #331.

Download PagerDuty MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every PagerDuty release on the releases page.)

Prefer the Claude Code plugin? Add the marketplace once, then install - works immediately, no directory listing required:

/plugin marketplace add Servosity/msp-skills

/plugin install pagerduty@msp-skills

Path A - paste one prompt into your AI agent (recommended)

Copy this into Claude Code, Codex CLI, or Claude Cowork:

Install the PagerDuty Skill and MCP server from Servosity/msp-skills in this agent workspace. If this workspace uses a POSIX shell (macOS, Linux, WSL, or Bash), run bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/pagerduty/install.sh). If it uses Windows PowerShell, run iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/pagerduty/install.ps1 | iex. Then authenticate per the README and run pagerduty-cli --help to explore.

The same prompt works in any agent that can run shell.

Path B - run the installer yourself

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/pagerduty/install.ps1 | iex

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/pagerduty/install.sh)

The installer drops both pagerduty-cli (the CLI) and pagerduty-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.

Verify:

pagerduty-cli --version

Upgrade to the latest version

The installer always fetches the current release - re-run it to upgrade:

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/pagerduty/install.sh)

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/pagerduty/install.ps1 | iex

Claude Desktop .mcpb users: download the latest .mcpb (top of this section) and re-select it in Settings > Extensions. Claude Code plugin users: /plugin update pagerduty@msp-skills.

Add to Claude Desktop, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, or another MCP client

After the installer runs, see [mcp-install.md](./mcp-install.md) and [docs/which-agent.md](../../docs/which-agent.md) for the per-agent wire-up - one section per agent, including the GitHub Copilot servers key and the ChatGPT desktop app. Claude Desktop's Settings > Extensions panel is the simplest path; the MCP config block (for users who prefer editing JSON) is documented in mcp-install.md.

Install for Hermes

From the Hermes CLI:

hermes skills install servosity/msp-skills/skills/pagerduty --force

Inside a Hermes chat session:

/skills install servosity/msp-skills/skills/pagerduty --force

Hermes speaks MCP natively, so it can also use the pagerduty-mcp server directly - same install path, same env vars.

Install for OpenClaw

Tell your OpenClaw agent (copy this):

Install the pagerduty skill from https://github.com/servosity/msp-skills/tree/main/skills/pagerduty. The skill defines how its required CLI (pagerduty-cli) can be installed via the openclaw: frontmatter block.

OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.

Authenticate

See mcp-install.md for the credentials pagerduty-cli needs.

What this skill does

Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.

What makes this different

Most PagerDuty integrations and MCP servers proxy each question into a live API call. That's fine for one record. It gets slow and costly at scale, when you're asking "what was our MTTR by service across the whole quarter" or "who carried the most off-hours pages last month" - the cross-incident analytics PagerDuty otherwise gates behind its paid Analytics tier.

This skill syncs PagerDuty into a local SQLite mirror with full-text search. Aggregate questions become one local SQL join: instant, offline, and the AI sees the answer, not the raw data. Commands like insights mttr, insights responders, and audit coverage compute that math locally from the incidents, log entries, services, escalation policies, and schedules any REST API key can read - no Analytics add-on, no live call per question.

The pain this closes

On-call is where good teams quietly bleed out. Catchpoint's 2025 SRE survey found nearly 70% of responders say on-call stress drives burnout and attrition, and a 2025 Splunk study tied 73% of outages to alerts that got ignored - because the average engineer fields ~50 pages a week and only a handful matter. Meanwhile the numbers leadership wants at the QBR (MTTA, MTTR, who's carrying the load) sit behind PagerDuty's paid Analytics tier or a hand-stitched CSV, and the gap in next week's on-call schedule stays invisible until an incident finds it.

This skill turns those into one-line answers:

• pagerduty-cli pulse - what's open right now, bucketed by service and sorted by SLA risk.
• pagerduty-cli insights mttr --by service --since 30d - MTTA/MTTR per service, computed offline, no Analytics add-on.
• pagerduty-cli insights responders --since 30d - who's carrying the pages and the off-hours share, the burnout signal.
• pagerduty-cli audit coverage --severity high - services whose escalation chain is broken or a single point of failure.
• pagerduty-cli audit schedule-gaps --days 14 - future windows where a schedule has nobody on call, before the incident finds the hole.

See pain-point.md for the longer narrative.

Frequently asked questions

Does this work with ChatGPT?

Yes, in the ChatGPT desktop app. It runs MCP servers locally (STDIO), the way pagerduty-mcp runs, and shares MCP configuration with Codex (OpenAI): add pagerduty-mcp under Settings > MCP servers as a STDIO server, or add it once to Codex's ~/.codex/config.toml. ChatGPT on the web is not supported by msp-skills yet: it needs a remote server. If your team works there, a [ho