PagerDuty's official MCP server which provides tools to interact with your PagerDuty account.
Runs on your machine from its package; the steps are below.
At most: creates or changes data: records, files, settings.
Odel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Run
uvx pagerduty-mcp
MCP client config
{
"mcpServers": {
"pagerduty": {
"command": "uvx",
"args": [
"pagerduty-mcp"
]
}
}
}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.
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.
The full documentation lives in docs/ and is readable directly on GitHub.
Getting Started
Installation
Remote Server
Configuration
Tools Reference
Use Cases
Experimental
experimental branchCommunity
Contributing
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.
If you are interested in contributing to this project, please refer to our Contributing Guidelines and the development setup guide.