PagerDuty's local MCP (Model Context Protocol) server which provides tools to interact with your PagerDuty account, allowing you to manage incidents, services, schedules, and more directly from your MCP-enabled client.
-
asdf-vm installed.
-
uv installed globally.
-
A PagerDuty User API Token. To obtain a PagerDuty User API Token, follow these steps:
- Navigate to User Settings. Click on your user profile icon, then select My Profile and then User Settings.
- In your user settings, locate the API Access section.
- Click the Create API User Token button and follow the prompts to generate a new token.
- Copy the generated token and store it securely. You will need this token to configure the MCP server.
Use of the PagerDuty User API Token is subject to the PagerDuty Developer Agreement.
You can configure this MCP server directly within Visual Studio Code's settings.json
file, allowing VS Code to manage the server lifecycle.
-
Open VS Code settings (File > Preferences > Settings, or
Cmd+,
on Mac, orCtrl+,
on Windows/Linux). -
Search for "mcp" and ensure "Mcp: Enabled" is checked under Features > Chat.
-
Click "Edit in settings.json" under "Mcp > Discovery: Servers".
-
Add the following configuration:
{ "mcp": { "inputs": [ { "type": "promptString", "id": "pagerduty-api-key", "description": "PagerDuty API Key", "password": true } ], "servers": { "pagerduty-mcp": { "type": "stdio", "command": "uvx", "args": [ "pagerduty-mcp", "--enable-write-tools" // This flag enables write operations on the MCP Server enabling you to creating incidents, schedule overrides and much more ], "env": { "PAGERDUTY_USER_API_KEY": "${input:pagerduty-api-key}", "PAGERDUTY_API_HOST": "https://api.pagerduty.com" // If your PagerDuty account is located in EU update your API host to https://api.eu.pagerduty.com } } } } }
- Ensure MCP is enabled in VS Code settings (Features > Chat > "Mcp: Enabled").
- Configure the server as described above.
- Open the Chat view in VS Code (
View
>Chat
). - Make sure
Agent
mode is selected. In the Chat view, you can enable or disable specific tools by clicking the π οΈ icon. - Enter a command such as
Show me the latest incident
to interact with your PagerDuty account through the MCP server. - You can start, stop, and manage your MCP servers using the command palette (
Cmd+Shift+P
/Ctrl+Shift+P
) and searching forMCP: List Servers
. Ensure the server is running before sending commands. You can also try to restart the server if you encounter any issues.
You can configure this MCP server to work with Claude Desktop by adding it to Claude's configuration file.
-
Locate your Claude Desktop configuration file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json
- Windows:
%APPDATA%\Claude\claude_desktop_config.json
- macOS:
-
Create or edit the configuration file and add the following configuration:
{ "mcpServers": { "pagerduty-mcp": { "command": "uvx", "args": [ "pagerduty-mcp", "--enable-write-tools" ], "env": { "PAGERDUTY_USER_API_KEY": "your-pagerduty-api-key-here", "PAGERDUTY_API_HOST": "https://api.pagerduty.com" } } } }
-
Replace the placeholder values:
- Replace
/path/to/your/mcp-server-directory
with the full path to the directory where you cloned the MCP server (e.g.,/Users/yourname/code/pagerduty-mcp
) - Replace
your-pagerduty-api-key-here
with your actual PagerDuty User API Token - If your PagerDuty account is located in the EU, update the API host to
https://api.eu.pagerduty.com
- Replace
-
Restart Claude Desktop completely for the changes to take effect.
-
Test the integration by starting a conversation with Claude and asking something like "Show me my latest PagerDuty incidents" to verify the MCP server is working.
Security Note: Unlike VS Code's secure input prompts, Claude Desktop requires you to store your API key directly in the configuration file. Ensure this file has appropriate permissions (readable only by your user account) and consider the security implications of storing credentials in plain text.
-
Clone the repository
-
Install
asdf
pluginsasdf plugin add python asdf plugin add nodejs https://github.com/asdf-vm/asdf-nodejs.git asdf plugin add uv
-
Install tool versions using
asdf
:asdf install
-
Create a virtual environment and install dependencies using
uv
(now thatasdf
has set the correct Python anduv
versions):uv sync
-
Ensure
uv
is available globally.The MCP server can be run from different places so you need
uv
to be available globally. To do so, follow the official documentation.Tip: You may need to restart your terminal and/or VS Code for the changes to take effect.
-
Run it locally
To run your cloned PagerDuty MCP Server you need to update your configuration to use
uv
instead ofuvx
."pagerduty-mcp": { "type": "stdio", "command": "uv", "args": [ "run", "--directory", "/path/to/your/mcp-server-directory", // Replace with the full path to the directory where you cloned the MCP server, e.g. "/Users/yourname/code/mcp-server", "python", "-m", "pagerduty_mcp", "--enable-write-tools" // This flag enables write operations on the MCP Server enabling you to creating incidents, schedule overrides and much more ], "env": { "PAGERDUTY_USER_API_KEY": "${input:pagerduty-api-key}", "PAGERDUTY_API_HOST": "https://api.pagerduty.com" // If your PagerDuty account is located in EU update your API host to https://api.eu.pagerduty.com } }
This section describes the tools provided by the PagerDuty MCP server. They are categorized based on whether they only read data or can modify data in your PagerDuty account.
Important: By default, the MCP server only exposes read-only tools. To enable tools that can modify your PagerDuty account (write-mode tools), you must explicitly start the server with the
--enable-write-tools
flag. This helps prevent accidental changes to your PagerDuty data.
Tool | Area | Description | Read-only |
---|---|---|---|
list_escalation_policies | Escalation Policy | Lists escalation policies | β |
get_escalation_policy | Escalation Policy | Retrieves a specific escalation policy | β |
add_note_to_incident | Incidents | Adds note to an incident | β |
add_responders | Incidents | Adds responders to an incident | β |
create_incident | Incidents | Creates a new incident | β |
get_incident | Incidents | Retrieves a specific incident | β |
list_incidents | Incidents | Lists incidents | β |
manage_incidents | Incidents | Updates status, urgency, assignment, or escalation level | β |
add_team_member | Teams | Adds a user to a team with a specific role | β |
create_team | Teams | Creates a new team | β |
delete_team | Teams | Deletes a team | β |
get_team | Teams | Retrieves a specific team | β |
list_team_members | Teams | Lists members of a team | β |
list_teams | Teams | Lists teams | β |
remove_team_member | Teams | Removes a user from a team | β |
update_team | Teams | Updates an existing team | β |
get_user_data | Users | Gets the current user's data | β |
list_users | Users | Lists users in the PagerDuty account | β |
list_oncalls | On-call | Lists on-call schedules | β |
create_schedule_override | Schedules | Creates an override for a schedule | β |
get_schedule | Schedules | Retrieves a specific schedule | β |
list_schedule_users | Schedules | Lists users in a schedule | β |
list_schedules | Schedules | Lists schedules | β |
create_service | Services | Creates a new service | β |
get_service | Services | Retrieves a specific service | β |
list_services | Services | Lists services | β |
update_service | Services | Updates an existing service | β |
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.