PagerDuty MCP Server
Base URL: https://api.pagerduty.com
| Category | Infrastructure |
| Tools | 342 |
| Auth | API Key, OAuth2 |
API Info
- Contact: PagerDuty Support (support@pagerduty.com) — http://www.pagerduty.com/support
Install
Quick Start (recommended)
OAUTH2_CLIENT_ID=YOUR_OAUTH2_CLIENT_ID \
OAUTH2_CLIENT_SECRET=YOUR_OAUTH2_CLIENT_SECRET \
OAUTH2_SCOPES=YOUR_OAUTH2_SCOPES \
API_KEY=YOUR_API_KEY \
uvx mcparmory-pagerduty
With pip
pip install mcparmory-pagerduty
OAUTH2_CLIENT_ID=YOUR_OAUTH2_CLIENT_ID \
OAUTH2_CLIENT_SECRET=YOUR_OAUTH2_CLIENT_SECRET \
OAUTH2_SCOPES=YOUR_OAUTH2_SCOPES \
API_KEY=YOUR_API_KEY \
mcparmory-pagerduty
MCP Client Configuration
Add to your MCP client config (e.g. Claude Desktop, Cursor, Codex):
{
"mcpServers": {
"pagerduty": {
"command": "uvx",
"args": ["mcparmory-pagerduty"],
"env": {
"OAUTH2_CLIENT_ID": "YOUR_OAUTH2_CLIENT_ID",
"OAUTH2_CLIENT_SECRET": "YOUR_OAUTH2_CLIENT_SECRET",
"OAUTH2_SCOPES": "YOUR_OAUTH2_SCOPES",
"API_KEY": "YOUR_API_KEY"
}
}
}
}
Set OAUTH2_SCOPES to a comma-separated list of scopes your app requires (e.g. OAUTH2_SCOPES=scope_a,scope_b). Some OAuth2 providers may also use additional scope env vars such as OAUTH2_USER_SCOPES; open .env to see all generated scope buckets and descriptions.
Credentials
Set the following environment variables (via MCP client env config, shell export, or .env file):
OAUTH2_CLIENT_ID— OAuth2 client IDOAUTH2_CLIENT_SECRET— OAuth2 client secretOAUTH2_SCOPES— OAuth2 scopes (comma-separated)API_KEY— API Key Authentication (Authorization)
Do not commit credentials to version control.
OAuth2
Add this redirect URI to your OAuth provider's allowed redirect URIs:
http://localhost:9400/callback
If you change OAUTH2_CALLBACK_PORT in .env, update the redirect URI to match.
On first use, a browser window opens automatically for OAuth authorization. Grant access when prompted — tokens are saved to tokens/oauth2_tokens.json and refreshed automatically.
Re-authorization: Delete tokens/oauth2_tokens.json and restart the server.
Run Locally
First, configure your credentials in .env (see Credentials above).
pip install -r requirements.txt
python server.py
Connect MCP Client
Edit .mcp.json and replace <SERVER_DIR> with the absolute path to this directory, then add to your MCP client configuration.
Example (if server is at /home/user/mcp-servers/pagerduty):
{
"mcpServers": {
"pagerduty": {
"command": "python",
"args": ["/home/user/mcp-servers/pagerduty/server.py"]
}
}
}
Docker
Pre-built image (recommended)
docker run -p 8000:8000 -p 9400:9400 -v ./tokens:/app/tokens \
-e OAUTH2_CLIENT_ID=YOUR_OAUTH2_CLIENT_ID \
-e OAUTH2_CLIENT_SECRET=YOUR_OAUTH2_CLIENT_SECRET \
-e OAUTH2_SCOPES=YOUR_OAUTH2_SCOPES \
-e API_KEY=YOUR_API_KEY \
ghcr.io/mcparmory/pagerduty:latest
Build from source
First, configure your credentials in .env (see Credentials above).
docker build -t pagerduty .
mkdir -p tokens
docker run -p 8000:8000 -p 9400:9400 -v ./tokens:/app/tokens --env-file .env pagerduty
Before running, make sure ports 8000, 9400 are free. If you changed the callback port in .env, update the -p port mapping and your OAuth provider's redirect URI to match.
On first run, the server prints an authorization URL — check docker logs for the URL. Open it in your browser to complete OAuth consent. Tokens are persisted to ./tokens/ via the volume mount so re-authorization is not needed on subsequent runs.
MCP client config (Docker)
For Docker, use SSE transport in your MCP client config:
{
"mcpServers": {
"pagerduty": {
"type": "sse",
"url": "http://localhost:8000/sse"
}
}
}
Files
.env- Credentials and server configuration.mcp.json- MCP client config templateDockerfile- Container buildLICENSE- MIT license for this generated coderequirements.txt- Python dependenciesREADME.md- This fileserver.py- MCP server entry point_auth.py- Authentication handlers_models.py- Request/response models_validators.py- Input validation
Note: Files starting with . are hidden by default on macOS/Linux. Use ls -a in terminal or enable "Show hidden files" in your file manager to see .env and .mcp.json.
Generated by MCP Blacksmith · Quickstart docs · Report a bug
Release files for mcparmory-pagerduty 1.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcparmory_pagerduty-1.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Release files / mcparmory_pagerduty-1.0.2-py3-none-any.whl
| Download URL | mcparmory_pagerduty-1.0.2-py3-none-any.whl |
|---|---|
| Size | 211.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
13c3736bb3ae84dac00b16bc08975aa6527479848a477b65ece93aa8440e58e2
|
|
BLAKE2b-256 checksum How to use checksums |
ffd6faef25f796f352a3935a595a6f1fc06b5b49fcafdd3bce65c2340be54063
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|