MCP.so
Sign In

PagerDuty MCP Server

@wpfleger96

Basic information

Category

AI & Agents

License

MIT

Transports

stdio

Author

wpfleger96

About PagerDuty MCP Server

MCP server exposing PagerDuty incidents, services, schedules, and on-calls to AI agents — read, acknowledge, resolve, with OAuth and API key auth

PagerDuty MCP Server config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "pagerduty-mcp-server": {
      "command": "uv",
      "args": [
        "sync"
      ]
    }
  }
}

PagerDuty MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is PagerDuty MCP Server?

It is a server that exposes PagerDuty API functionality to LLMs, designed for programmatic use with structured inputs and outputs. It allows LLMs to perform operations on PagerDuty resources such as incidents, services, teams, and users.

How to use PagerDuty MCP Server?

Install via uvx pagerduty-mcp-server and configure authentication using a PagerDuty API token, OAuth 2.0 PKCE, or the X-PagerDuty-Token HTTP header. Use with Claude/Cursor by adding the MCP configuration, or run as a standalone server with uv run pagerduty-mcp-server.

Key features of PagerDuty MCP Server

  • Exposes PagerDuty API tools for LLMs
  • Read and write operations on incidents, services, teams, users
  • Optional include parameter to reduce token usage
  • Consistent response format with metadata and optional error
  • Automatic pagination and rate limit handling
  • Supports API token, OAuth, and per-request token authentication

Use cases of PagerDuty MCP Server

  • Query and manage incidents assigned to you
  • Check upcoming on-call schedules for your team
  • Retrieve details about services, teams, and users
  • Acknowledge or resolve incidents and add notes
  • Filter results by user context to reduce irrelevant data

Frequently asked questions

1

What authentication methods are supported?

Three methods: the `X-PagerDuty-Token` HTTP header (per-request), the `PAGERDUTY_API_TOKEN` environment variable, and OAuth 2.0 PKCE for local interactive use. OAuth is opt-in and requires a client ID.

2

How does the `include` parameter work?

Most read tools accept an optional `include` parameter – a list of field names to return. When specified, only those fields are included in each response object, reducing token usage.

3

What is the response format for errors?

When an error occurs, the response includes an `error` object with `message` and `code` fields. The error object is only present on errors; otherwise, responses contain metadata and a resource list.

Comments

More AI & Agents MCP servers