PagerDuty MCP Server
PagerDuty incident management, on-call schedules, and reporting inside your IDE.
Data last scanned yesterday · Reviewed 2 months ago
Overview
This server integrates PagerDuty workflows directly into MCP-enabled IDEs using Python. It provides interactive React-based interfaces to manage the full incident lifecycle, perform schedule overrides, and visualize service dependencies without leaving the development environment. Beyond basic incident handling, the server includes specialized reporting tools for tracking on-call metrics, compliance, and equity. An onboarding wizard is also provided to assist with configuring teams, escalation policies, and AIOps settings.
Our verdict
This server carries a high-risk score of 28/100, primarily because it lacks any authentication method, meaning anyone with access to the configuration can execute actions against your account. It also forces full write access without a read-only mode, which poses a significant security risk for production environments. Given its community-maintained status and lack of editorial review, it should be restricted to isolated test environments rather than production PagerDuty accounts.
- Native IDE integration with React-based UIs
- Zero direct dependencies minimize supply-chain exposure
- Provides comprehensive on-call compensation and equity reports
- No authentication mechanism implemented
- Forces full write access with no read-only mode
- Community-maintained rather than official vendor support
Tools
| Tool | Description | Risk |
|---|---|---|
| create_alert_grouping_setting | Creates a new alert grouping setting | medium |
| delete_alert_grouping_setting | Deletes an alert grouping setting | high |
| get_alert_grouping_setting | Retrieves a specific alert grouping setting | low |
| list_alert_grouping_settings | Lists alert grouping settings with filtering | low |
| update_alert_grouping_setting | Updates an existing alert grouping setting | medium |
| get_incident_metrics_all | Retrieves aggregated incident metrics across all services | low |
| get_incident_metrics_by_service | Retrieves incident metrics grouped by service | low |
| get_incident_metrics_by_team | Retrieves incident metrics grouped by team | low |
| get_responder_load_metrics | Retrieves responder load metrics | low |
| get_responder_metrics | Retrieves responder performance metrics | low |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| ChatGPT | ||||
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf |
Frequently asked questions
›What prerequisites are required to run this MCP server?
You must have asdf-vm and uv installed on your system. You also need a PagerDuty User API Token obtained from your PagerDuty user settings.
›How do I enable write operations such as creating incidents or schedule overrides?
You must include the --enable-write-tools flag in your server command arguments within your client configuration.
›Does this server support PagerDuty accounts located in the EU?
Yes, if your account is in the EU, you should set the PAGERDUTY_API_HOST environment variable to https://api.eu.pagerduty.com in your configuration.
›How can I interact with the PagerDuty embedded apps like the Incident Command Center?
Once configured, you can launch specific tools like the Incident Command Center, On-Call Manager, or Onboarding Wizard by asking your AI assistant (e.g., Claude in VS Code) to show or open them.
Alternatives
Badge
Maintain this server? Add the live badge to your README.