{
"mcpServers": {
"pagerduty-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A server that exposes PagerDuty API functionality to LLMs. This server is designed to be used programmatically, with structured inputs and outputs.
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
MIT. View license →
Is it maintained?
Last commit 273 days ago. 7 stars.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Dynamic problem-solving through sequential thought chains
A Model Context Protocol server for searching and analyzing arXiv papers
An open-source AI agent that brings the power of Gemini directly into your terminal.
The official Python SDK for Model Context Protocol servers and clients
MCP Security Weekly
Get CVE alerts and security updates for Pagerduty Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A server that exposes PagerDuty API functionality to LLMs. This server is designed to be used programmatically, with structured inputs and outputs.
The PagerDuty MCP Server provides a set of tools for interacting with the PagerDuty API. These tools are designed to be used by LLMs to perform various operations on PagerDuty resources such as incidents, services, teams, and users.
cd pagerduty-mcp-server
brew install uv
uv sync
The PagerDuty MCP Server requires a PagerDuty API token. You can provide this in two ways:
Option 1: Environment Variable
export PAGERDUTY_API_TOKEN=your_api_token_here
Option 2: .env File (Recommended)
Create a .env file in the project root:
echo "PAGERDUTY_API_TOKEN=your_api_token_here" > .env
The server will automatically load environment variables from the .env file if present.
In Goose:
pagerduty-mcp-server).uvx pagerduty-mcp-server
pagerduty:
args:
- pagerduty-mcp-server
bundled: null
cmd: uvx
description: ''
enabled: true
env_keys:
- PAGERDUTY_API_TOKEN
envs: {}
name: pagerduty
timeout: 300
type: stdio
{
"mcpServers": {
"pagerduty-mcp-server": {
"command": "uvx",
"args": ["pagerduty-mcp-server"],
"env": {
"PAGERDUTY_API_TOKEN": <PAGERDUTY_API_TOKEN>
}
}
}
}
uv run path/to/repo/pagerduty-mcp-server/.venv/bin/pagerduty-mcp-server
All API responses follow a consistent format:
{
"metadata": {
"count": <int>, // Number of results
"description": "<str>" // A short summary of the results
},
<resource_type>: [ // Always pluralized for consistency, even if one result is returned
{
...
},
...
],
"error": { // Only present if there's an error
"message": "<str>", // Human-readable error description
"code": "<str>" // Machine-readable error code
}
}
When an error occurs, the response will include an error object with the following structure:
{
"metadata": {
"count": 0,
"description": "Error occurred while processing request"
},
"error": {
"message": "Invalid user ID provided",
"code": "INVALID_USER_ID"
}
}
Common error scenarios include: