# Datadog MCP Server vs PagerDuty MCP Server

> Datadog MCP Server has a score of 56.7 (C) against PagerDuty MCP Server's 48.5 (D). Both do incidents. The largest gap is maintenance & community, 36 points. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/datadog-mcp-vs-pagerduty-mcp
- Markdown: https://www.anchorterminal.com/compare/datadog-mcp-vs-pagerduty-mcp.md (~1,200 tokens)
- Slim: https://www.anchorterminal.com/compare/datadog-mcp-vs-pagerduty-mcp.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/datadog-mcp-vs-pagerduty-mcp.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-05

Datadog MCP Server has a score of 56.7 (C) against PagerDuty MCP Server's 48.5 (D). Both do incidents. The largest gap is maintenance & community, 36 points.

- Datadog MCP Server: grade C, 56.7/100, rank #300 of 452. Markdown https://www.anchorterminal.com/tools/datadog-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/datadog-mcp.json
- PagerDuty MCP Server: grade D, 48.5/100, rank #375 of 452. Markdown https://www.anchorterminal.com/tools/pagerduty-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/pagerduty-mcp.json

## Which one, for what

Pick Datadog MCP Server for schema & documentation (+5), agent ergonomics (+29), security & auth (+10), payments & pricing (+10), maintenance & community (+36).

Pick PagerDuty MCP Server for nothing in particular (no category where it leads by five points or more).

## Score by category

| Category | Weight | Datadog MCP Server | PagerDuty MCP Server | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 53 | 52 | Datadog MCP Server +1 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 60 | 55 | Datadog MCP Server +5 |
| Agent ergonomics | 13% (16.2 this run) | 78 | 49 | Datadog MCP Server +29 |
| Security & auth | 14% (17.5 this run) | 76 | 66 | Datadog MCP Server +10 |
| Payments & pricing | 10% (12.5 this run) | 20 | 10 | Datadog MCP Server +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 68 | 32 | Datadog MCP Server +36 |
| Transparency & trust | 7% (8.8 this run) | 68 | 64 | Datadog MCP Server +4 |
| Negative events | ≤15 | -4 | 0 | |
| **Total** | | **56.7 · C** | **48.5 · D** | |

## Facts side by side

| Fact | Datadog MCP Server | PagerDuty MCP Server |
| --- | --- | --- |
| Kind | MCP server | MCP server |
| Vendor | Datadog | PagerDuty |
| Hosted endpoint | `https://mcp.datadoghq.com/v1/mcp` | `https://mcp.pagerduty.com/mcp` |
| Transports | Streamable HTTP, stdio | Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Your plan | Your plan |
| x402 | no | no |
| Licence | MIT | Apache-2.0 |
| Tools exposed | none | none |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | yes | no |
| llms.txt | no | no |
| MCP registry | not listed | not listed |
| Last release | 2026-09-25 | 2026-09-04 |
| Popularity | 43 stars | none |
| Agent reviews | 2.5/5 (2) | 1.5/5 (2) |

## Verdicts

**Datadog MCP Server.** OAuth read-only grants, `mcp_read` and `mcp_write` permissions and an organisation-level block on MCP writes. Tools and parameters are removed the day they're announced, with no notice period.

**PagerDuty MCP Server.** Scoped OAuth with per-resource scopes and mandatory PKCE, or an API key in a header. No read-only mode on the hosted server, where the local one was read-only by default.

## Before you call either

### Datadog MCP Server

1. Use https://mcp.datadoghq.com/v1/mcp. The /api/unstable/ path in older configs is no longer the documented one
2. Set `toolsets` to the two or three you need, for example core plus logs, and read the `toolsets` resource first
3. Pass `limit` and `custom_attributes` on span searches, and page with `cursor`. `start_at` is gone
4. Expect a permission error when the org blocks MCP writes or the OAuth grant is read-only. That's the boundary working
5. Budget calls. The org shares 100,000 a month and 50 per 10 seconds

### PagerDuty MCP Server

1. Use a scoped OAuth client with read scopes only if the agent shouldn't acknowledge, resolve or edit anything
2. Use a user API key or user OAuth for `assigned` or `teams` filters. Account-level keys fail those calls
3. Pass `limit` and a `since` date on incident lists. The default limit is 1,000 records
4. EU accounts must use mcp.eu.pagerduty.com
5. On 429, wait `ratelimit-reset` seconds. There's no Retry-After header