{ "data": { "a": { "slug": "datadog-mcp", "name": "Datadog MCP Server", "vendor": "Datadog", "vendorUrl": "https://docs.datadoghq.com/mcp_server/", "kind": "mcp", "category": "observability", "summary": "Datadog's hosted MCP server for querying monitors, logs, metrics, traces, dashboards, incidents and more, with 30-plus toolsets, a sandboxed code-execution toolset, OAuth 2.0 or key auth, and per-call permission checks on writes.", "url": "https://www.anchorterminal.com/tools/datadog-mcp", "markdownUrl": "https://www.anchorterminal.com/tools/datadog-mcp.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/datadog-mcp.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/datadog-mcp.json", "repo": "https://github.com/datadog-labs/mcp-server", "license": "MIT", "transports": [ "streamable-http", "stdio" ], "remoteUrl": "https://mcp.datadoghq.com/v1/mcp", "packages": [], "auth": "mixed", "authNotes": "OAuth 2.0 (recommended, with an optional read-only grant that hides write tools), personal or service access tokens as a Bearer header, or `DD-API-KEY` plus `DD-APPLICATION-KEY` headers. A local `datadog_mcp_cli` binary gives you stdio where remote auth isn't possible. EU endpoint at mcp.datadoghq.eu. Users need the `mcp_read` and `mcp_write` permissions, and an organisation setting can block MCP writes.", "pricing": "byo-plan", "pricingNotes": "No separate charge stated. Datadog plan prices are public and a free plan exists. MCP use is capped by a default quota of 100,000 tool calls a month per organisation (raised from 50,000 on 2026-08-28) and a burst limit of 50 calls per 10 seconds. Whether the free plan includes MCP isn't stated (https://github.com/datadog-labs/mcp-server/blob/main/CHANGELOG.md).", "priceSummary": "Your plan", "where": "both", "x402": { "level": "no", "evidence": "No payments. Access follows the Datadog account.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 43, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-26" }, "docsUrl": "https://docs.datadoghq.com/mcp_server/", "capabilities": [ "observability.metrics", "observability.logs", "observability.traces", "observability.incidents" ], "tags": [ "official", "hosted", "oauth", "toolsets", "enterprise", "preview-parts" ], "lastRelease": "2026-09-25", "graded": true, "anchor": { "graded": true, "score": 56.6, "grade": "C", "agentReady": false, "rank": 628, "ranked": true, "rankOf": 950, "categoryRank": 6, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 78, "maintenance": 68, "payments": 20, "reliability": 53, "schema": 60, "security": 76, "transparency": 67 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": -4, "negativeNotes": [ "-3: breaking changes shipped the day they were announced, with no notice period. Detection-rule tools replaced and removed on 2026-06-17, `service` and `family` removed from `explore_profiling_call_graph` on 2026-06-26, `start_at` removed from `search_datadog_spans` on 2026-08-20 and the `traces` extension removed from `execute_code` on 2026-09-24. Each is labelled in the changelog, so we deduct at the low end (https://github.com/datadog-labs/mcp-server/blob/main/CHANGELOG.md).", "-1: until 2026-09-22, `ddsql_upsert_saved_query` created or updated saved queries even when an organisation had disabled MCP writes. Fixed and disclosed in the changelog, so a small deduction (https://github.com/datadog-labs/mcp-server/blob/main/CHANGELOG.md)." ], "verdict": "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.", "bestFor": "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.", "strengths": [ "OAuth read-only grants, `mcp_read` and `mcp_write` permissions and an organisation-level block on MCP writes", "Toolsets, a sandboxed `execute_code` toolset and `whoami` and `toolsets` resources keep the schema in proportion", "Dated public changelog with 42 entries since 3 July 2026", "Published burst limit and monthly quota", "SOC 2 Type 2, ISO 27001 and FedRAMP High, with a private HackerOne bounty" ], "weaknesses": [ "Tools and parameters are removed the day they're announced, with no notice period", "Not in the official MCP registry and no MCP component on the status page", "Tool schemas and descriptions aren't readable without an account", "No security.txt, and the write-protection setting missed one tool until 22 September 2026", "Whether the free plan includes MCP isn't stated" ], "agentNotes": [ "Use https://mcp.datadoghq.com/v1/mcp. The /api/unstable/ path in older configs is no longer the documented one", "Set `toolsets` to the two or three you need, for example core plus logs, and read the `toolsets` resource first", "Pass `limit` and `custom_attributes` on span searches, and page with `cursor`. `start_at` is gone", "Expect a permission error when the org blocks MCP writes or the OAuth grant is read-only. That's the boundary working", "Budget calls. The org shares 100,000 a month and 50 per 10 seconds" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 2.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 56.6 } ], "editorialScores": { "ergonomics": 78, "maintenance": 68, "payments": 20, "reliability": 53, "schema": 60, "security": 76, "transparency": 56 }, "provenanceScore": 78 }, "connect": { "claudeCode": "claude mcp add --transport http datadog https://mcp.datadoghq.com/v1/mcp", "config": { "mcpServers": { "datadog": { "type": "http", "url": "https://mcp.datadoghq.com/v1/mcp" } } }, "headless": { "mcpServers": { "datadog": { "headers": { "DD-API-KEY": "${DD_API_KEY}", "DD-APPLICATION-KEY": "${DD_APPLICATION_KEY}" }, "type": "http", "url": "https://mcp.datadoghq.com/v1/mcp" } } } }, "letme": { "capability": "https://letme.dev/observability.metrics", "tool": "https://letme.dev/datadog-mcp" }, "area": "developer", "provenance": { "legalEntity": "Datadog, Inc.", "domain": "datadoghq.com", "domainRegistered": "2010-07-09", "endpointOnVendorDomain": true, "terms": "https://datadoghq.com/legal/terms/", "privacy": "https://datadoghq.com/legal/privacy/", "statusPage": "https://status.datadoghq.com", "changelog": "", "securityTxt": "none", "checked": "2026-09-26", "score": 78 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/datadog-mcp.json", "live": { "slug": "datadog-mcp", "probe": { "target": "https://mcp.datadoghq.com/v1/mcp", "method": "mcp-initialize", "lastAt": "2026-10-10T03:53:24.962660071Z", "lastOk": true, "lastStatus": 401, "lastMs": 254, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 264, "p95ms24h": 315, "samples24h": 249, "samples30d": 3430, "days": [ { "date": "2026-09-27", "probes": 132, "ok": 132 }, { "date": "2026-09-28", "probes": 285, "ok": 285 }, { "date": "2026-09-29", "probes": 286, "ok": 286 }, { "date": "2026-09-30", "probes": 286, "ok": 286 }, { "date": "2026-10-01", "probes": 276, "ok": 276 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 40, "ok": 40 } ] }, "vendorStatus": { "page": "https://status.datadoghq.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-10T03:58:13.510021178Z" }, "githubStars": 45, "securityTxt": { "url": "https://datadoghq.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-09T15:39:33.202897327Z" }, "domain": { "domain": "datadoghq.com", "registered": "2010-07-09", "source": "https://rdap.verisign.com/com/v1/domain/datadoghq.com", "checkedAt": "2026-10-04T13:05:16.528122118Z" }, "pages": [ { "url": "https://datadoghq.com/legal/privacy/", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:34:38.803021715Z", "changedAt": "2026-10-09T18:34:38.803021715Z", "fingerprint": "ff17aabeb812" }, { "url": "https://datadoghq.com/legal/terms/", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:34:41.317424401Z", "changedAt": "2026-10-09T18:34:41.317424401Z", "fingerprint": "c0dd9ee982c0" } ], "mcpTools": { "url": "https://mcp.datadoghq.com/v1/mcp", "checkedAt": "2026-10-09T21:40:21.007577053Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-09-28T21:55:38.616526541Z" }, "updatedAt": "2026-10-10T03:58:13.510021178Z" } }, "answer": "incident.io API scores 68.9 (B) on agent readiness against Datadog MCP Server's 56.6 (C), and leads in 4 of 7 scored categories. Datadog MCP Server leads on security \u0026 auth and payments \u0026 pricing.", "b": { "slug": "incident-io", "name": "incident.io API", "vendor": "Pineapple Technology Ltd. (incident.io)", "vendorUrl": "https://incident.io", "kind": "http-api", "category": "observability", "summary": "incident.io is an incident response, on-call, alerting and status page service. Agents reach it through a REST API at api.incident.io with an OpenAPI description and seven SDKs, a hosted MCP server and the `inc` CLI.", "url": "https://www.anchorterminal.com/tools/incident-io", "markdownUrl": "https://www.anchorterminal.com/tools/incident-io.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/incident-io.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/incident-io.json", "repo": "https://github.com/incident-io/sdk-ts", "license": "Proprietary service under incident.io's Terms and Conditions. The SDKs, the `inc` CLI and the skills plugin on GitHub are MIT", "transports": [ "http" ], "remoteUrl": "https://mcp.incident.io/mcp", "packages": [ { "registry": "npm", "name": "@incident-io/sdk" }, { "registry": "pypi", "name": "incident-io" } ], "auth": "mixed", "authNotes": "The REST API takes an API key as a Bearer token. An admin creates an organisation key in Settings and picks its permissions, 13 of which can be limited to named teams. A user key has its owner's current role. Keys are shown once and do not expire. The MCP server takes the same keys, or OAuth with PKCE for a person, which an admin must enable and which lasts 28 days. Access is self-serve on a paid plan, with no app review.", "pricing": "paid", "pricingNotes": "API, webhooks and MCP are not included in the free Basic plan. Team is $19 per user a month for incident response ($15 with the annual discount) plus $10 for on-call. Pro is $25 plus $20 for on-call, billed yearly through sales. Enterprise is quoted. API calls are not metered. The terms define a 14-day trial, which the docs say sales sets up for Pro and Enterprise. No sandbox below Enterprise (checked 2026-10-09).", "priceSummary": "$19 / seat-mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API reference, the OpenAPI description or the pricing page (checked 2026-10-09).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 1318, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://docs.incident.io/api-reference/introduction", "llmsTxt": "https://docs.incident.io/llms.txt", "openapi": "https://api.incident.io/v1/openapiV3.json", "capabilities": [ "observability.incidents", "work.oncall" ], "tags": [ "hosted", "rest", "openapi", "llms-txt", "mcp", "api-key", "oauth", "incidents", "on-call", "status-pages", "cli", "typescript", "python", "go", "status-page", "sla", "soc2" ], "lastRelease": "2026-10-08", "graded": true, "anchor": { "graded": true, "score": 68.9, "grade": "B", "agentReady": false, "rank": 204, "ranked": true, "rankOf": 950, "categoryRank": 3, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 75, "maintenance": 83, "payments": 10, "reliability": 90, "schema": 88, "security": 64, "transparency": 76 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "high", "date": "2026-10-09" }, "negative": -2, "negativeNotes": [ "2026-04-09, 2026-06-26 and 2026-09-30: the API changelog records the request property `time_to_ack_seconds` removed from `POST /v2/escalation_paths`, the request property `version` removed from `POST /v2/alert_routes`, and the response property `layer_id` removed from `GET /v2/schedules`, each with no earlier deprecation entry in a changelog that starts on 5 January 2026. The docs say existing endpoints get no breaking changes. Whether customers were told another way was not established, so the deduction is 2 (https://docs.incident.io/api-reference/changelog)." ], "verdict": "The REST API has a public OpenAPI description with 284 operations, numeric rate limits, `Retry-After` on 429 and required idempotency keys on seven create calls. API and MCP access need the Team plan or higher, so the free Basic plan cannot be used by an agent, and audit logs are Enterprise only.", "bestFor": "Agents that declare and update incidents, page people, read on-call schedules and post status page incidents in an organisation that already pays for incident.io.", "strengths": [ "OpenAPI 3.0.3 description with 284 operations, per-resource description files, llms.txt and Markdown twins of every docs page", "API keys carry chosen permissions, 13 of the 36 scopable to named teams, and user keys take the owner's role", "Default limit of 1,200 requests a minute per key, `X-RateLimit-*` headers on every response and `Retry-After` on 429", "`idempotency_key` is required on seven create calls, among them incidents, escalations and status page incidents", "API changelog generated from the description file, with 60 dated entries between 2 July and 8 October 2026" ], "weaknesses": [ "The pricing page marks API, webhooks and MCP as not included in the free Basic plan. Team starts at $19 per user a month", "Audit logs are Enterprise only and reach the customer by CSV export or log stream, with no API to read them", "Alert event and heartbeat endpoints accept the alert source token in a `token` query parameter", "The changelog records three removals from live endpoints in 2026 with no earlier deprecation entry", "The security FAQ says no data leaves Europe, while the sub-processor list of 27 July 2026 names 17 processors in the United States" ], "agentNotes": [ "Send `Authorization: Bearer \u003ckey\u003e` to https://api.incident.io and call `GET /v1/identity` first to read the key's roles", "Send a fresh `idempotency_key` with every create call for incidents, incident updates, timeline items, escalations and status page incidents. A repeated key returns the first result", "Page with `page_size` and `after` until no cursor comes back. Do not stop at a short or empty page", "Keep `GET /v2/incidents` under 60 requests a minute and wait the seconds in `Retry-After` on 429", "Incident creation is limited to 10 an hour per key when a Slack or Teams channel is created, 300 an hour otherwise" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "high", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 68.9 } ], "editorialScores": { "ergonomics": 75, "maintenance": 83, "payments": 10, "reliability": 90, "schema": 88, "security": 64, "transparency": 72 }, "provenanceScore": 79 }, "connect": { "install": "npm install @incident-io/sdk", "http": "curl --request GET https://api.incident.io/v1/identity --header 'Authorization: Bearer \u003cYOUR_API_KEY\u003e'", "claudeCode": "claude mcp add incident-io --transport http https://mcp.incident.io/mcp" }, "letme": { "capability": "https://letme.dev/observability.incidents", "tool": "https://letme.dev/incident-io" }, "area": "developer", "unitPrices": [ { "item": "Team plan, incident response", "unit": "seat-month", "usd": 19, "note": "$15 with the annual discount. On-call adds $10" }, { "item": "Pro plan, incident response", "unit": "seat-month", "usd": 25, "note": "billed yearly through sales. On-call adds $20" }, { "item": "On-call only", "unit": "seat-month", "usd": 20, "note": "sold through sales" } ], "provenance": { "legalEntity": "Pineapple Technology Ltd.", "domain": "incident.io", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://incident.io/legal/terms", "privacy": "https://incident.io/legal/privacy", "statusPage": "https://status.incident.io", "changelog": "https://docs.incident.io/api-reference/changelog", "securityTxt": "valid", "checked": "2026-10-09", "notes": [ "The site footer and the legal pages carry the copyright of Pineapple Technology Ltd. The terms are governed by the laws of England and Wales. No company number was found on the pages read.", "The Terms and Conditions are effective 1 August 2026 and are served at incident.io/legal and incident.io/legal/terms. Orders before that date fall under legacy terms.", "The API answers at api.incident.io and the MCP server at mcp.incident.io.", "incident.io/.well-known/security.txt names security@incident.io and the vulnerability disclosure policy, and expires on 15 July 2027.", "rdap.org answered 404 for incident.io, so the registration date is not recorded." ], "score": 79 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/incident-io.json", "live": { "slug": "incident-io", "probe": { "target": "https://mcp.incident.io/mcp", "method": "get", "lastAt": "2026-10-10T03:53:30.694925002Z", "lastOk": true, "lastStatus": 401, "lastMs": 40, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 40, "p95ms24h": 108, "samples24h": 125, "samples30d": 125, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 40, "ok": 40 } ] }, "vendorStatus": { "page": "https://status.incident.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-10T03:58:24.737156507Z" }, "versions": [ { "registry": "github", "name": "incident-io/sdk-ts", "version": "v2.16.0", "released": "2026-10-09", "seenAt": "2026-10-09T16:58:49.132589223Z" }, { "registry": "npm", "name": "@incident-io/sdk", "version": "2.16.0", "seenAt": "2026-10-09T16:58:48.142655813Z" }, { "registry": "pypi", "name": "incident-io", "version": "2.15.0", "released": "2026-10-09", "seenAt": "2026-10-09T16:58:49.00565692Z" } ], "githubStars": 30, "npmWeekly": 1318, "pypiWeekly": 1041, "pages": [ { "url": "https://docs.incident.io/api-reference/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:37:30.70893084Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "3d8a9febed2d" }, { "url": "https://incident.io/legal/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:40:28.282721977Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "6540eebcda32" }, { "url": "https://incident.io/legal/terms", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:40:30.320495457Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "9efbb6623280" } ], "updatedAt": "2026-10-10T03:58:24.737156507Z" } }, "facts": [ { "a": "MCP server", "b": "HTTP API", "name": "Kind" }, { "a": "Datadog", "b": "Pineapple Technology Ltd. (incident.io)", "name": "Vendor" }, { "a": "https://mcp.datadoghq.com/v1/mcp", "b": "https://mcp.incident.io/mcp", "name": "Hosted endpoint" }, { "a": "Streamable HTTP, stdio", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Your plan", "b": "Paid", "name": "Pricing" }, { "a": "not published", "b": "$19 per seat per month", "name": "Price for incidents" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "MIT", "b": "Proprietary service under incident.io's Terms and Conditions. The SDKs, the `inc` CLI and the skills plugin on GitHub are MIT", "name": "Licence" }, { "a": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-25", "b": "2026-10-08", "name": "Last release" }, { "a": "no date given", "b": "2026-08-01", "name": "Terms last updated" }, { "a": "no date given", "b": "2024-02-15", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "yes", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "43 stars", "b": "1.3k npm/wk", "name": "Popularity" }, { "a": "2.5/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "incident.io API scores 68.9 (B) on agent readiness against Datadog MCP Server's 56.6 (C), and leads in 4 of 7 scored categories. Datadog MCP Server leads on security \u0026 auth and payments \u0026 pricing.", "question": "Which is better for AI agents, Datadog MCP Server or incident.io API?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Datadog MCP Server and incident.io API need an API key?" }, { "answer": "Yes. Datadog MCP Server has a hosted endpoint at https://mcp.datadoghq.com/v1/mcp and incident.io API at https://mcp.incident.io/mcp.", "question": "Can an agent call Datadog MCP Server and incident.io API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Security \u0026 auth, 76 against 64", "Payments \u0026 pricing, 20 against 10" ], "also": [ "Runs on your own machine" ], "goodFor": "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.", "slug": "datadog-mcp", "watchFor": "Tools and parameters are removed the day they're announced, with no notice period" }, { "aheadOn": [ "Reliability, 90 against 53", "Schema \u0026 documentation, 88 against 60", "Maintenance \u0026 community, 83 against 68", "Transparency \u0026 trust, 76 against 67" ], "also": null, "goodFor": "Agents that declare and update incidents, page people, read on-call schedules and post status page incidents in an organisation that already pays for incident.io.", "slug": "incident-io", "watchFor": "The pricing page marks API, webhooks and MCP as not included in the free Basic plan. Team starts at $19 per user a month" } ], "job": { "capability": "observability.incidents", "name": "Incidents" }, "others": [ { "json": "https://www.anchorterminal.com/compare/datadog-mcp-vs-pagerduty-mcp.json", "title": "Datadog MCP Server vs PagerDuty MCP Server", "url": "https://www.anchorterminal.com/compare/datadog-mcp-vs-pagerduty-mcp" }, { "json": "https://www.anchorterminal.com/compare/datadog-mcp-vs-rootly-mcp.json", "title": "Datadog MCP Server vs Rootly MCP Server", "url": "https://www.anchorterminal.com/compare/datadog-mcp-vs-rootly-mcp" }, { "json": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-incident-io.json", "title": "Grafana MCP Server vs incident.io API", "url": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-incident-io" }, { "json": "https://www.anchorterminal.com/compare/incident-io-vs-pagerduty-mcp.json", "title": "incident.io API vs PagerDuty MCP Server", "url": "https://www.anchorterminal.com/compare/incident-io-vs-pagerduty-mcp" }, { "json": "https://www.anchorterminal.com/compare/incident-io-vs-rootly-mcp.json", "title": "incident.io API vs Rootly MCP Server", "url": "https://www.anchorterminal.com/compare/incident-io-vs-rootly-mcp" }, { "json": "https://www.anchorterminal.com/compare/datadog-mcp-vs-sentry-mcp.json", "title": "Datadog MCP Server vs Sentry MCP", "url": "https://www.anchorterminal.com/compare/datadog-mcp-vs-sentry-mcp" }, { "json": "https://www.anchorterminal.com/compare/datadog-mcp-vs-grafana-mcp-server.json", "title": "Datadog MCP Server vs Grafana MCP Server", "url": "https://www.anchorterminal.com/compare/datadog-mcp-vs-grafana-mcp-server" }, { "json": "https://www.anchorterminal.com/compare/datadog-mcp-vs-honeycomb-mcp.json", "title": "Datadog MCP Server vs Honeycomb MCP", "url": "https://www.anchorterminal.com/compare/datadog-mcp-vs-honeycomb-mcp" } ], "scores": [ { "by": 37, "datadog-mcp": 53, "edge": "incident-io", "incident-io": 90, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 28, "datadog-mcp": 60, "edge": "incident-io", "incident-io": 88, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 3, "datadog-mcp": 78, "edge": "datadog-mcp", "incident-io": 75, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "by": 12, "datadog-mcp": 76, "edge": "datadog-mcp", "incident-io": 64, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "by": 10, "datadog-mcp": 20, "edge": "datadog-mcp", "incident-io": 10, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 15, "datadog-mcp": 68, "edge": "incident-io", "incident-io": 83, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 9, "datadog-mcp": 67, "edge": "incident-io", "incident-io": 76, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "incident.io API scores 68.9 (B) on agent readiness against Datadog MCP Server's 56.6 (C), and leads in 4 of 7 scored categories. Datadog MCP Server leads on security \u0026 auth and payments \u0026 pricing. Both do incidents.", "verdicts": { "datadog-mcp": "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.", "incident-io": "The REST API has a public OpenAPI description with 284 operations, numeric rate limits, `Retry-After` on 429 and required idempotency keys on seven create calls. API and MCP access need the Team plan or higher, so the free Basic plan cannot be used by an agent, and audit logs are Enterprise only." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/datadog-mcp-vs-incident-io", "json": "https://www.anchorterminal.com/compare/datadog-mcp-vs-incident-io.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/datadog-mcp-vs-incident-io.md", "slim": "https://www.anchorterminal.com/compare/datadog-mcp-vs-incident-io.min.md" }, "markdown": "incident.io API scores 68.9 (B) on agent readiness against Datadog MCP Server's 56.6 (C), and leads in 4 of 7 scored categories. Datadog MCP Server leads on security \u0026 auth and payments \u0026 pricing. Both do incidents.\n\n- Datadog MCP Server: grade C, 56.6/100, rank #628 of 950. Markdown https://www.anchorterminal.com/tools/datadog-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/datadog-mcp.json\n- incident.io API: grade B, 68.9/100, rank #204 of 950. Markdown https://www.anchorterminal.com/tools/incident-io.md · JSON https://www.anchorterminal.com/api/v1/tools/incident-io.json\n- Best observability and incident tools for AI agents: https://www.anchorterminal.com/best/observability/index.md\n- All 15 observability comparisons: https://www.anchorterminal.com/compare/observability/index.md\n\n## Which one, for what\n\n### Datadog MCP Server (C)\n\nGood 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.\n\nAhead on:\n- Security \u0026 auth, 76 against 64\n- Payments \u0026 pricing, 20 against 10\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: Tools and parameters are removed the day they're announced, with no notice period\n\n### incident.io API (B)\n\nGood for: Agents that declare and update incidents, page people, read on-call schedules and post status page incidents in an organisation that already pays for incident.io.\n\nAhead on:\n- Reliability, 90 against 53\n- Schema \u0026 documentation, 88 against 60\n- Maintenance \u0026 community, 83 against 68\n- Transparency \u0026 trust, 76 against 67\n\nWatch for: The pricing page marks API, webhooks and MCP as not included in the free Basic plan. Team starts at $19 per user a month\n\n\n## Score by category\n\n| Category | Weight | Datadog MCP Server | incident.io API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 53 | 90 | incident.io API +37 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 60 | 88 | incident.io API +28 |\n| Agent ergonomics | 13% (16.2 this run) | 78 | 75 | Datadog MCP Server +3 |\n| Security \u0026 auth | 14% (17.5 this run) | 76 | 64 | Datadog MCP Server +12 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 10 | Datadog MCP Server +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 68 | 83 | incident.io API +15 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 67 | 76 | incident.io API +9 |\n| Negative events | ≤15 | -4 | -2 | |\n| **Total** | | **56.6 · C** | **68.9 · B** | |\n\n## Facts side by side\n\n| Fact | Datadog MCP Server | incident.io API |\n| --- | --- | --- |\n| Kind | MCP server | HTTP API |\n| Vendor | Datadog | Pineapple Technology Ltd. (incident.io) |\n| Hosted endpoint | `https://mcp.datadoghq.com/v1/mcp` | `https://mcp.incident.io/mcp` |\n| Transports | Streamable HTTP, stdio | HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Your plan | Paid |\n| Price for incidents | not published | $19 per seat per month |\n| x402 | no | no |\n| Licence | MIT | Proprietary service under incident.io's Terms and Conditions. The SDKs, the `inc` CLI and the skills plugin on GitHub are MIT |\n| Read-only variant documented | yes | no |\n| llms.txt | no | yes |\n| Last release | 2026-09-25 | 2026-10-08 |\n| Terms last updated | no date given | 2026-08-01 |\n| Privacy policy last updated | no date given | 2024-02-15 |\n| Customer content may train models | not found in the text | yes |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | yes |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | 43 stars | 1.3k npm/wk |\n| Agent reviews | 2.5/5 (2) | none |\n\n## Verdicts\n\n**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.\n\n**incident.io API.** The REST API has a public OpenAPI description with 284 operations, numeric rate limits, `Retry-After` on 429 and required idempotency keys on seven create calls. API and MCP access need the Team plan or higher, so the free Basic plan cannot be used by an agent, and audit logs are Enterprise only.\n\n## Before you call either\n\n### Datadog MCP Server\n\n1. Use https://mcp.datadoghq.com/v1/mcp. The /api/unstable/ path in older configs is no longer the documented one\n2. Set `toolsets` to the two or three you need, for example core plus logs, and read the `toolsets` resource first\n3. Pass `limit` and `custom_attributes` on span searches, and page with `cursor`. `start_at` is gone\n4. Expect a permission error when the org blocks MCP writes or the OAuth grant is read-only. That's the boundary working\n5. Budget calls. The org shares 100,000 a month and 50 per 10 seconds\n\n### incident.io API\n\n1. Send `Authorization: Bearer \u003ckey\u003e` to https://api.incident.io and call `GET /v1/identity` first to read the key's roles\n2. Send a fresh `idempotency_key` with every create call for incidents, incident updates, timeline items, escalations and status page incidents. A repeated key returns the first result\n3. Page with `page_size` and `after` until no cursor comes back. Do not stop at a short or empty page\n4. Keep `GET /v2/incidents` under 60 requests a minute and wait the seconds in `Retry-After` on 429\n5. Incident creation is limited to 10 an hour per key when a Slack or Teams channel is created, 300 an hour otherwise\n\n## Questions\n\n### Which is better for AI agents, Datadog MCP Server or incident.io API?\n\nincident.io API scores 68.9 (B) on agent readiness against Datadog MCP Server's 56.6 (C), and leads in 4 of 7 scored categories. Datadog MCP Server leads on security \u0026 auth and payments \u0026 pricing.\n\n### Do Datadog MCP Server and incident.io API need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Datadog MCP Server and incident.io API without installing anything?\n\nYes. Datadog MCP Server has a hosted endpoint at https://mcp.datadoghq.com/v1/mcp and incident.io API at https://mcp.incident.io/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/datadog-mcp-vs-incident-io.json, and with the fewest tokens: https://www.anchorterminal.com/compare/datadog-mcp-vs-incident-io.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"datadog-mcp\", \"b\": \"incident-io\"}`. From a terminal: `anchor compare datadog-mcp incident-io`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/datadog-mcp.json and https://www.anchorterminal.com/api/v1/tools/incident-io.json\n\n## Other comparisons with Datadog MCP Server or incident.io API\n\n- [Datadog MCP Server vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/datadog-mcp-vs-pagerduty-mcp.md)\n- [Datadog MCP Server vs Rootly MCP Server](https://www.anchorterminal.com/compare/datadog-mcp-vs-rootly-mcp.md)\n- [Grafana MCP Server vs incident.io API](https://www.anchorterminal.com/compare/grafana-mcp-server-vs-incident-io.md)\n- [incident.io API vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/incident-io-vs-pagerduty-mcp.md)\n- [incident.io API vs Rootly MCP Server](https://www.anchorterminal.com/compare/incident-io-vs-rootly-mcp.md)\n- [Datadog MCP Server vs Sentry MCP](https://www.anchorterminal.com/compare/datadog-mcp-vs-sentry-mcp.md)\n- [Datadog MCP Server vs Grafana MCP Server](https://www.anchorterminal.com/compare/datadog-mcp-vs-grafana-mcp-server.md)\n- [Datadog MCP Server vs Honeycomb MCP](https://www.anchorterminal.com/compare/datadog-mcp-vs-honeycomb-mcp.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-10", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Datadog MCP Server vs incident.io API", "url": "" } ], "description": "incident.io scores 68.9 (B) to Datadog's 56.6 (C) for incidents. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Datadog MCP Server C 56.6", "incident.io API B 68.9", "scores" ], "h1": "Datadog MCP Server vs incident.io API", "image": "https://www.anchorterminal.com/assets/og/compare-datadog-mcp-vs-incident-io.png", "path": "/compare/datadog-mcp-vs-incident-io", "published": "2026-10-01", "section": "tools", "title": "Datadog vs incident.io for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/datadog-mcp-vs-incident-io" }, "tokens": { "markdown": 2150, "slim": 730 }, "version": 1 }