MCP Server vs Pagerduty MCP
A side-by-side look at the MCP Server and Pagerduty MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Server for monitoring work as a local process; choose Pagerduty MCP for monitoring as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Server when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
DEVHELM_API_TOKEN. - You want tools like
list_monitors, get_monitor, create_monitor.
Choose Pagerduty MCP when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
PAGERDUTY_USER_API_KEY. - You want tools like
create_alert_grouping_setting, delete_alert_grouping_setting, get_alert_grouping_setting.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 57/100 · Good | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | DEVHELM_API_TOKEN | PAGERDUTY_USER_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 79 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 129 | 80 |
| Full listing | View MCP Server | View Pagerduty MCP |
Tools & capabilities
MCP Server tools 129
list_monitorsList all uptime monitors in the workspace.get_monitorGet a single monitor by ID, including its full configuration.create_monitorCreate a new uptime monitor. Required: name and type (HTTP, DNS, TCP, ICMP, HEARTBEAT, MCP_SERVER, BROWSER, MULTI_STEP_API). ``config`` is required for probe types (HTTP, DNS, TCP, ICMP, HEARTBEAT, MCP_SERVER). Browser and multi-step monitors use a type default when ``config`` is omitted. ``frequencySeconds`` is optional (10–86400). Omit it to use the plan minimum. ``managedBy`` is set automatically to ``MCP`` server-side; callers cannot override it. Use the SDK or CLI directly if you need a different attribution.update_monitorUpdate an existing monitor's configuration.delete_monitorDelete a monitor permanently.pause_monitorPause a monitor (stops checking until resumed).resume_monitorResume a paused monitor.test_monitorTrigger an ad-hoc test run for a monitor and return the result.list_monitor_resultsList recent check results for a monitor (cursor-paginated).list_monitor_versionsList version history for a monitor.list_incidentsList all incidents in the workspace.get_incidentGet a single incident by ID with full details.- +117 more on the listing page
Pagerduty MCP tools 80
create_alert_grouping_settingCreates a new alert grouping settingdelete_alert_grouping_settingDeletes an alert grouping settingget_alert_grouping_settingRetrieves a specific alert grouping settinglist_alert_grouping_settingsLists alert grouping settings with filteringupdate_alert_grouping_settingUpdates an existing alert grouping settingget_incident_metrics_allRetrieves aggregated incident metrics across all servicesget_incident_metrics_by_serviceRetrieves incident metrics grouped by serviceget_incident_metrics_by_teamRetrieves incident metrics grouped by teamget_responder_load_metricsRetrieves responder load metricsget_responder_metricsRetrieves responder performance metricsget_business_service_dependenciesRetrieves dependencies for a specific business serviceget_technical_service_dependenciesRetrieves technical service dependencies for a business service- +68 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MCP Server
{
"mcpServers": {
"mcp-server-113": {
"command": "uvx",
"args": [
"devhelm-mcp-server"
],
"env": {
"DEVHELM_API_TOKEN": "YOUR_DEVHELM_API_TOKEN_HERE"
}
}
}
}
Pagerduty MCP
{
"mcpServers": {
"pagerduty-mcp": {
"command": "uvx",
"args": [
"pagerduty-mcp"
],
"env": {
"PAGERDUTY_USER_API_KEY": "YOUR_PAGERDUTY_USER_API_KEY_HERE"
}
}
}
}
Frequently asked questions
MCP Server is categorized under Monitoring and uses a local stdio subprocess. Pagerduty MCP belongs to Monitoring and uses a local stdio subprocess. Pick MCP Server for monitoring work and Pagerduty MCP for monitoring.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
MCP Server has no declared pricing — check the project's own site. Pagerduty MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mcp-server-113 and pagerduty-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Server has a quality signal of 57/100 (Good) with 1 views, 0 installs and 1 GitHub stars. Pagerduty MCP has 40/100 (Fair) with 2 views, 0 installs and 79 GitHub stars.