mcpField
P
pagerduty-mcp

pagerduty-mcp

Local
github.com/PagerDutyCloud & Infra79Updated 8w ago
Repository

About pagerduty-mcp

PagerDuty's official MCP server is a local server that lets MCP clients manage incidents, services, schedules and event orchestrations in a PagerDuty account. The repository is deprecated and read-only, and development has moved to PagerDuty's hosted remote MCP server.

Key features

  1. 01Manage incidents, services, schedules and escalation policies
  2. 02Query teams, users and on-call information
  3. 03Tools for event orchestrations and change events
  4. 04Read-only tools by default, write tools opt-in
  5. 05Run through uvx or Docker

Use cases

  1. 01Querying open incidents from an MCP client
  2. 02Checking who is on call for a given service
  3. 03Gathering incident and on-call details for a shift handoff

MCP support

This project is an MCP server that exposes tools for operating a PagerDuty account to MCP clients. Only read-only tools are available by default, and the --enable-write-tools flag is needed to allow changes.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "pagerduty-pagerduty": {
      "command": "uvx",
      "args": [
        "pagerduty-mcp"
      ],
      "env": {
        "PAGERDUTY_USER_API_KEY": "<PAGERDUTY_USER_API_KEY>",
        "PAGERDUTY_API_HOST": "<PAGERDUTY_API_HOST>"
      }
    }
  }
}
Run commanduvx pagerduty-mcp
Environment variables to set
PAGERDUTY_USER_API_KEYSecretPagerDuty User API Token - obtain from User Settings > API Access in your PagerDuty account
PAGERDUTY_API_HOSTPagerDuty API host URL (default: https://api.pagerduty.com, EU: https://api.eu.pagerduty.com)

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
pypipagerduty-mcp0.2.1

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

PagerDuty's official MCP Server

Important

This repository is deprecated and now read-only. Development has moved to PagerDuty's hosted Remote MCP Server — see the docs there for setup instructions.

PagerDuty's local MCP (Model Context Protocol) server which provides tools to interact with your PagerDuty account, allowing you to manage incidents, services, schedules, event orchestrations, and more directly from your MCP-enabled client.

Quick start

You need uv and a PagerDuty User API Token — see Prerequisites and Authentication.

PAGERDUTY_USER_API_KEY="your-token" uvx pagerduty-mcp

By default only read-only tools are exposed. Add --enable-write-tools to allow tools that modify your PagerDuty account. Then point your MCP client at the server — Cursor, VS Code, Claude Desktop, or Docker.

Prefer no local install? PagerDuty hosts a Remote MCP Server with OAuth support.

Contents

The full documentation lives in docs/ and is readable directly on GitHub.

Getting Started

Installation

Remote Server

Configuration

Tools Reference

Use Cases

Experimental

Community

Contributing

Support

PagerDuty's MCP server is an open-source project, and as such, we offer only community-based support. If assistance is required, please open an issue in GitHub or PagerDuty's community forum.

Contributing

If you are interested in contributing to this project, please refer to our Contributing Guidelines and the development setup guide.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.