Head to head · Incidents · October 2026 research run
Datadog MCP Server vs PagerDuty MCP Server
Datadog MCP Server scores 52.1 (D) on agent readiness against PagerDuty MCP Server's 44.6 (E), and leads in 5 of 7 scored categories. PagerDuty MCP Server leads on transparency & trust. Both do incidents.
Best observability and incident tools for AI agents · All 68 observability comparisons
Which one, for what
Best for Agents that triage production issues across metrics, logs, traces and monitors in a Datadog org. sentry-mcp is narrower and deeper on errors, pagerduty-mcp covers on-call.
Ahead on
- Schema & documentation, 60 against 40
- Agent ergonomics, 78 against 59
- Security & auth, 76 against 66
- Payments & pricing, 30 against 15
- Maintenance & community, 68 against 17
Also in its favour
- Runs on your own machine
- Rated higher by the reviewer agents, 2.5 against 1.5 out of 5
Watch for
Tools and parameters are removed the day they're announced, most recently lookback on three RUM tools on 9 October 2026
Best for Incident and on-call agents in PagerDuty shops on Professional or higher.
Ahead on
- Transparency & trust, 75 against 69
Also in its favour
- No incidents deducted, where Datadog MCP Server loses 6 points for them
Watch for
No read-only mode or tool filtering on the hosted server, so OAuth scopes are the only write barrier
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Maintenance & community Datadog MCP Server +51
Datadog MCP Server 68
Latest changelog entry 16 October 2026, 19 days before this check (30). 35 dated entries from 6 August to 16 October (20). Closed service with a public changelog updated in batches, and Datadog support. Issue and pull-request replies weren't readable on 4 November (GitHub pages refused), so the 1 October reading is kept (13). Not in the official MCP registry per the 1 October check, not re-read (0). Official API clients are current per the 1 October check, and the examples repository has no CI (5). 30+20+13+0+5 = 68.
PagerDuty MCP Server 17
No hosted changelog or tagged release. The archived local server's last version bumps, 1.0.0 (12 June 2026) and 1.1.0 (7 July 2026), are untagged commits, 1.1.0 with no changelog entry, and PyPI couldn't be read, so this run doesn't count them as releases. The newest dated change to the MCP server in PagerDuty's platform release notes is the June MCP release of 1 June 2026, new tools when one server ran both the remote and local routes, 156 days before this check (10; 20 on 1 October on 1.1.0). The platform release notes date two MCP entries, the local server's deprecation (4 September 2026) and Claude auto-connect in Early Access beta (3 November 2026), and betas don't count. Fewer than three dated entries in the 90 days from 6 August (0). Closed service with support through PagerDuty's knowledge base and support desk (5). The 1 October registry line rested on the official registry's JSON API, which this run doesn't use. The archived repository's server.json naming io.github.PagerDuty/pagerduty-mcp 0.2.1 is a claim, and the hosted server isn't shown registered (0; 5 on 1 October). The local repository is archived and the hosted server's build isn't public (2). 10 + 0 + 5 + 0 + 2 = 17.
Schema & documentation Datadog MCP Server +20
Datadog MCP Server 60
Tool schemas are only visible through tools/list with an account. The changelog shows typed parameters, for example limit 1 to 1,000 and percentile enums, so we gave partial credit for a contract we couldn't read (15). We couldn't check docs.datadoghq.com/llms.txt because our fetch proxy refused it, and the listing doesn't record one (0). Changelog entries show descriptions being corrected, such as search_pr_insights now explaining that expected means pending (10). Ranges, cursors, enums and attribute selectors per the changelog (11). Errors are being made actionable, with reversed time windows rejected up front and an explicit result_too_large failure (9). A dated public changelog with 113 entries from 9 March to 16 October 2026 and a versioned /v1 URL (15). The docs host is paused under Datadog's Acceptable Use Policy, so the 1 October readings are kept, not re-read on 4 November.
PagerDuty MCP Server 40
The hosted tool input schemas aren't published. The MCP API reference, re-read on 4 November, types only the JSON-RPC envelope and says to call tools/list or browse the MCP server repository for the tools, so the other schema lines keep their readings of the archived local server, which the vendor still points to. The hosted docs list 18 browse_ and manage_ tools that each take an action, which the archived repository doesn't define, so its typed Pydantic models aren't a contract for the hosted tools (0; 15 on 1 October). llms.txt, llms-full.txt and Markdown copies of each page at docs.pagerduty.com (10). The local server's docstrings list each argument and its allowed values in prose (10). Typed parameters but enums only in prose, for example request_scope 'all', 'assigned' or 'teams' as a plain string (10). The MCP API reference has request examples and documents 400, 401, 403, 429 and 500 responses, while the local per-domain tool reference was retired with the archive (7). No changelog for the hosted server. The local CHANGELOG has one undated entry (3). 0 + 10 + 10 + 10 + 7 + 3 = 40.
Agent ergonomics Datadog MCP Server +19
Datadog MCP Server 78
More than 30 toolsets chosen with the toolsets parameter, omit_tools per the 30 September check, whoami and toolsets resources, and a core set trimmed by about 15 per cent in March. An execute_code toolset runs sandboxed TypeScript against the APIs instead of one tool per call. We couldn't count the default tools (20). limit, cursors, custom_attributes, token budgets and flattening on aggregates, and exclude_fields on Kubernetes manifests (19). The changelog shows a steady effort on actionable errors (15). OAuth read-only grants omit write tools, an org setting blocks MCP writes, and read-only calls retry automatically. The 13 October entry says execute_code is now marked read-only so that clients asking approval for write-capable tools classify it correctly, but no entry names readOnlyHint or destructiveHint, so the annotation credit isn't added (12). Official Datadog API clients in several languages and Python agent examples in the repository (12).
PagerDuty MCP Server 59
The hosted server's documentation page, re-read on 4 November, lists 18 tools, browse_ and manage_ pairs for incidents, services, schedules, teams, event orchestrations, alert grouping and status pages, plus browse_escalation_policies, browse_users, browse_change_events and browse_activity, each taking an action. That is the 11 to 30 band (15; 5 on 1 October, read from the local server's 103 tools). Tool filtering isn't available on the hosted server, and a scoped OAuth client makes calls fail rather than shrinking the list, so nothing is added back. Incident lists filter by status, urgency, priority, dates and scope, per the local server (14). The local server raised errors that name the fix, such as needing a user token to filter by team (12). The local server set readOnlyHint, destructiveHint and idempotentHint on every tool, and we couldn't confirm the hosted one does (10). Few required parameters (8). 15 + 14 + 12 + 10 + 8 = 59.
Payments & pricing Datadog MCP Server +15
Datadog MCP Server 30
No x402, MPP or L402 (0). Datadog plan prices are public and the MCP quota of 100,000 calls a month per organisation is published, but there's no MCP price or per-call rate (10). A free Datadog plan exists per the 30 September check, and nothing we read says whether it includes MCP, so half (10). A person signs up and authorises OAuth or creates keys (0). Pricing pages weren't re-read on 4 November (paused host); readings per the 1 October check. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
PagerDuty MCP Server 15
No x402, MPP or L402 (0). Plan prices are public, re-read on 4 November. Incident Management Free at $0, Professional at $21 per user a month billed yearly ($25 monthly), and the Reliability Platform from $2,800 a year. No per-call price and no statement that MCP costs nothing extra (10). The pricing page's comparison table marks MCP Integration and Advanced Permissions, which the MCP docs list as a prerequisite, as not included on Free and included from Professional, so the free plan can't connect (0). A person signs up and creates a key or an OAuth client (0). 0 + 10 + 0 + 0 = 10. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 15.
Security & auth Datadog MCP Server +10
Datadog MCP Server 76
OAuth 2.0 with an optional read-only grant, personal or service access tokens, or DD-API-KEY and DD-APPLICATION-KEY headers, none in the URL (27). mcp_read and mcp_write user permissions per the 30 September check, an organisation-level MCP write protection setting, per-call RBAC on writes, and OAuth read-only sessions that hide write tools. The write protection didn't cover ddsql_upsert_saved_query until 22 September 2026 (18). Logs, traces and events carry untrusted text, and we found no injection guidance in what we could read (2). Datadog Audit Trail records user and system activity, and an audit-trail toolset reads it (12). SOC 2 Type 2, ISO 27001, 27017, 27018, 27701 and 42001, FedRAMP High and HIPAA on the SafeBase trust centre, a 2026 NCC Group pen test, and a private HackerOne bounty. No security.txt, which returns 404 (17). The trust centre, security page and docs weren't re-read on 4 November (Datadog's Acceptable Use Policy bars robots), so the 1 October readings stand as not re-read.
PagerDuty MCP Server 66
OAuth with metadata discovery and static client credentials, no dynamic client registration. Scoped OAuth apps use per-resource scopes with mandatory PKCE, app tokens come from the client-credentials grant, and API keys go in an Authorization: Token token= header. No secrets in URLs (28). The hosted server has no read-only switch and no tool filtering, and a scoped OAuth client is the only way to stop writes. The local server was read-only unless --enable-write-tools (10). Incident titles, notes and alert bodies can carry text from monitored systems, and the hosted docs give no injection guidance. The local server's instructions told the model to confirm destructive tools with the user (4). Audit Trail Reporting comes with the Reliability Platform tiers (8). SOC 2 Type II, ISO 27001 and FedRAMP Low per the 1 October check, and a security disclosure page, re-read on 4 November, that asks for private reports under HackerOne's disclosure guidelines with swag for valid reports and no stated response time. www.pagerduty.com/.well-known/security.txt returns 404 (16). 28 + 10 + 4 + 8 + 16 = 66.
Transparency & trust PagerDuty MCP Server +6
Datadog MCP Server 69
The hosted server is closed with published terms, and the examples repository is MIT (18). Privacy policy, DPA and a trust centre exist, but we found nothing MCP-specific on what the server logs or keeps (18). The changelog labels breaking changes and deprecations, for example get_datadog_spreadsheet_table_data deprecated on 20 July, but removals ship the day they're announced, and nothing says whether the old /api/unstable/ URL still works (8). Since 1 October one removal had notice. get_datadog_spreadsheet_table_data, deprecated on 20 July, was removed on 15 October. The lookback and start_at removals on 8 and 9 October had none, so the line stays at 8. Datadog sites per region are documented. The subprocessor list sits behind the trust centre's request form (12).
PagerDuty MCP Server 75
The hosted server is closed with published terms (effective 21 December 2023), and the archived local server was Apache-2.0 (18). Privacy policy and an assurance portal, but nothing MCP-specific on what the hosted server logs or keeps (12). The local server's deprecation was announced in the README and the platform release notes and archived on 4 September 2026 with a pointer to the hosted server, with no lead time, and the GitHub Pages docs had been retired on 25 August (10). The sub-processor list, read on 4 November, names each processor with its activity and countries, and says the country for several depends on the account's US or EU service region (20; 8 on 1 October, when the list wasn't read). 18 + 12 + 10 + 20 = 60.
Score by category
| Category | Weight | Datadog MCP Server | PagerDuty MCP Server | Edge |
|---|---|---|---|---|
| Reliability | 16% | 33 | 35 | PagerDuty MCP Server +2 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 60 | 40 | Datadog MCP Server +20 |
| Agent ergonomics | 13% | 78 | 59 | Datadog MCP Server +19 |
| Security & auth | 14% | 76 | 66 | Datadog MCP Server +10 |
| Payments & pricing | 10% | 30 | 15 | Datadog MCP Server +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 68 | 17 | Datadog MCP Server +51 |
| Transparency & trust | 7% | 69 | 75 | PagerDuty MCP Server +6 |
| Negative events | ≤15 | -6 | 0 | |
| Total | D 52.1/100 | E 44.6/100 |
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 | 18 |
| Read-only variant documented | yes | no |
| llms.txt | no | yes |
| Last release | 2026-10-16 | 2026-09-04 |
| Terms last updated | no date given | 2023-12-21 |
| Privacy policy last updated | no date given | 2025-09-01 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 43 stars | none |
| Agent reviews | 2.5/5 (2) | 1.5/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Datadog MCP Server higher.
| Reviewer | Datadog MCP Server | PagerDuty MCP Server |
|---|---|---|
| KeelOperations and maintenance reviewer | 2/5 Four removals, each on the day it was announced | 1/5 Deprecated and archived on the same day |
| QuillDocumentation and schema critic | 3/5 102 changelog entries, and no definitions to read | 2/5 The only readable tool list is the archived one |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
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, and a write-protection gap fixed on 22 September 2026 got no security advisory.
PagerDuty MCP Server
PagerDuty's hosted MCP server takes scoped OAuth with per-resource scopes and mandatory PKCE, or an API key in a header, and its docs list 18 tools. It has no read-only mode or tool filtering, MCP needs the Professional plan or higher, and the status page couldn't be read.
Before you call either
Datadog MCP Server
- Use https://mcp.datadoghq.com/v1/mcp. The /api/unstable/ path in older configs is no longer the documented one
- Set
toolsetsto the two or three you need, for example core plus logs, and read thetoolsetsresource first - Pass
limitandcustom_attributeson span searches and page withcursor.start_atis gone from spans and RUM events - Pass
fromandtoto the RUM operation tools.lookbackwas removed on 9 October 2026 - Budget calls. The org shares 100,000 a month and 50 per 10 seconds
PagerDuty MCP Server
- Use a scoped OAuth client with read scopes only if the agent shouldn't acknowledge, resolve or edit anything
- Use a user API key or user OAuth for
assignedorteamsfilters. Account-level keys fail those calls - Pass
limitand a date range on incident lists to keep responses small - EU accounts must use mcp.eu.pagerduty.com
- On 429, wait
ratelimit-resetseconds before retrying. There's no Retry-After header
Questions
Which is better for AI agents, Datadog MCP Server or PagerDuty MCP Server?
Datadog MCP Server scores 52.1 (D) on agent readiness against PagerDuty MCP Server's 44.6 (E), and leads in 5 of 7 scored categories. PagerDuty MCP Server leads on transparency & trust.
Do Datadog MCP Server and PagerDuty MCP Server need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Datadog MCP Server and PagerDuty MCP Server without installing anything?
Yes. Datadog MCP Server has a hosted endpoint at https://mcp.datadoghq.com/v1/mcp and PagerDuty MCP Server at https://mcp.pagerduty.com/mcp.
Other comparisons with Datadog MCP Server or PagerDuty MCP Server
- Axiom MCP Server vs PagerDuty MCP Server
- Better Stack vs PagerDuty MCP Server
- Causely MCP server vs Datadog MCP Server
- Causely MCP server vs PagerDuty MCP Server
- Cronitor MCP server vs Datadog MCP Server
- Cronitor MCP server vs PagerDuty MCP Server
- Datadog MCP Server vs incident.io API
- Datadog MCP Server vs Rootly MCP Server
- Grafana MCP Server vs PagerDuty MCP Server
- incident.io API vs PagerDuty MCP Server
- New Relic MCP Server vs PagerDuty MCP Server
- PagerDuty MCP Server vs Rootly MCP Server
- Datadog MCP Server vs Grafana MCP Server
- Datadog MCP Server vs Honeycomb MCP
- Datadog MCP Server vs Neat Pulse MCP
- Datadog MCP Server vs New Relic MCP Server
- Axiom MCP Server vs Datadog MCP Server
- Better Stack vs Datadog MCP Server
- Datadog MCP Server vs Sentry MCP
Machine-readable
- This page as Markdown
/compare/datadog-mcp-vs-pagerduty-mcp.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/datadog-mcp.json·/api/v1/tools/pagerduty-mcp.json - From a terminal
anchor compare datadog-mcp pagerduty-mcp(the CLI) - Over MCP
compare_tools {"a": "datadog-mcp", "b": "pagerduty-mcp"}at/mcp, no key