Pagerduty MCP vs Datadog MCP Server
A side-by-side look at the Pagerduty MCP and Datadog MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Pagerduty MCP for monitoring work as a local process; choose Datadog MCP Server 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 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.
Choose Datadog MCP Server 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:
DD_API_KEY, DD_APP_KEY, DD_SITE, DD_ALLOW_WRITE, DD_TOOLS, DD_DISABLE, MCP_TRANSPORT, MCP_HTTP_TOKEN. - You want tools like
query-metrics, get-metrics, get-metric-metadata.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 40/100 · Fair | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | API key required |
| Pricing | BYOK (pay the provider) | BYOK (pay the provider) |
| Required env vars | PAGERDUTY_USER_API_KEY | DD_API_KEYDD_APP_KEYDD_SITEDD_ALLOW_WRITEDD_TOOLSDD_DISABLEMCP_TRANSPORTMCP_HTTP_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 79 | 3 |
| Directory activity | 2 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 80 | 80 |
| Full listing | View Pagerduty MCP | View Datadog MCP Server |
Tools & capabilities
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
Datadog MCP Server tools 80
query-metricsget-metricsget-metric-metadatalist-active-metricslist-metric-tagsget-dashboardsget-dashboardcreate-dashboardupdate-dashboarddelete-dashboardsearch-logsaggregate-logs- +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.
Pagerduty MCP
{
"mcpServers": {
"pagerduty-mcp": {
"command": "uvx",
"args": [
"pagerduty-mcp"
],
"env": {
"PAGERDUTY_USER_API_KEY": "YOUR_PAGERDUTY_USER_API_KEY_HERE"
}
}
}
}
Datadog MCP Server
{
"mcpServers": {
"us-all-datadog-mcp-server": {
"command": "npx",
"args": [
"-y",
"@us-all/datadog-mcp"
],
"env": {
"DD_API_KEY": "YOUR_DD_API_KEY_HERE",
"DD_APP_KEY": "YOUR_DD_APP_KEY_HERE",
"DD_SITE": "YOUR_DD_SITE_HERE",
"DD_ALLOW_WRITE": "YOUR_DD_ALLOW_WRITE_HERE",
"DD_TOOLS": "YOUR_DD_TOOLS_HERE",
"DD_DISABLE": "YOUR_DD_DISABLE_HERE",
"MCP_TRANSPORT": "YOUR_MCP_TRANSPORT_HERE",
"MCP_HTTP_TOKEN": "YOUR_MCP_HTTP_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Pagerduty MCP is categorized under Monitoring and uses a local stdio subprocess. Datadog MCP Server belongs to Monitoring and uses a local stdio subprocess. Pick Pagerduty MCP for monitoring work and Datadog MCP Server 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.
Pagerduty MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Datadog MCP Server 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 pagerduty-mcp and us-all-datadog-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Pagerduty MCP has a quality signal of 40/100 (Fair) with 2 views, 0 installs and 79 GitHub stars. Datadog MCP Server has 59/100 (Good) with 2 views, 0 installs and 3 GitHub stars.