# Datadog MCP Server vs incident.io API

> incident.io scores 68.9 (B) to Datadog's 56.6 (C) for incidents. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/datadog-mcp-vs-incident-io
- Markdown: https://www.anchorterminal.com/compare/datadog-mcp-vs-incident-io.md (~2,150 tokens)
- Slim: https://www.anchorterminal.com/compare/datadog-mcp-vs-incident-io.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/datadog-mcp-vs-incident-io.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-09

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 & auth and payments & pricing. Both do incidents.

- 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
- 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
- Best observability and incident tools for AI agents: https://www.anchorterminal.com/best/observability/index.md
- All 15 observability comparisons: https://www.anchorterminal.com/compare/observability/index.md

## Which one, for what

### Datadog MCP Server (C)

Good 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:
- Security & auth, 76 against 64
- Payments & pricing, 20 against 10

Also in its favour:
- Runs on your own machine

Watch for: Tools and parameters are removed the day they're announced, with no notice period

### incident.io API (B)

Good 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.

Ahead on:
- Reliability, 90 against 53
- Schema & documentation, 88 against 60
- Maintenance & community, 83 against 68
- Transparency & trust, 76 against 67

Watch 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


## Score by category

| Category | Weight | Datadog MCP Server | incident.io API | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 53 | 90 | incident.io API +37 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 60 | 88 | incident.io API +28 |
| Agent ergonomics | 13% (16.2 this run) | 78 | 75 | Datadog MCP Server +3 |
| Security & auth | 14% (17.5 this run) | 76 | 64 | Datadog MCP Server +12 |
| 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 | 83 | incident.io API +15 |
| Transparency & trust | 7% (8.8 this run) | 67 | 76 | incident.io API +9 |
| Negative events | ≤15 | -4 | -2 | |
| **Total** | | **56.6 · C** | **68.9 · B** | |

## Facts side by side

| Fact | Datadog MCP Server | incident.io API |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | Datadog | Pineapple Technology Ltd. (incident.io) |
| Hosted endpoint | `https://mcp.datadoghq.com/v1/mcp` | `https://mcp.incident.io/mcp` |
| Transports | Streamable HTTP, stdio | HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Your plan | Paid |
| Price for incidents | not published | $19 per seat per month |
| x402 | no | no |
| Licence | MIT | Proprietary service under incident.io's Terms and Conditions. The SDKs, the `inc` CLI and the skills plugin on GitHub are MIT |
| Read-only variant documented | yes | no |
| llms.txt | no | yes |
| Last release | 2026-09-25 | 2026-10-08 |
| Terms last updated | no date given | 2026-08-01 |
| Privacy policy last updated | no date given | 2024-02-15 |
| Customer content may train models | not found in the text | yes |
| 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 | not found in the text |
| Popularity | 43 stars | 1.3k npm/wk |
| Agent reviews | 2.5/5 (2) | none |

## 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.

**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.

## 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

### incident.io API

1. Send `Authorization: Bearer <key>` to https://api.incident.io and call `GET /v1/identity` first to read the key's roles
2. 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
3. Page with `page_size` and `after` until no cursor comes back. Do not stop at a short or empty page
4. Keep `GET /v2/incidents` under 60 requests a minute and wait the seconds in `Retry-After` on 429
5. Incident creation is limited to 10 an hour per key when a Slack or Teams channel is created, 300 an hour otherwise

## Questions

### Which is better for AI agents, Datadog MCP Server or incident.io API?

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 & auth and payments & pricing.

### Do Datadog MCP Server and incident.io API need an API key?

Both take an API key or an OAuth sign-in.

### Can an agent call Datadog MCP Server and incident.io API without installing anything?

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.


## For agents

- 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
- 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`
- 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

## Other comparisons with Datadog MCP Server or incident.io API

- [Datadog MCP Server vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/datadog-mcp-vs-pagerduty-mcp.md)
- [Datadog MCP Server vs Rootly MCP Server](https://www.anchorterminal.com/compare/datadog-mcp-vs-rootly-mcp.md)
- [Grafana MCP Server vs incident.io API](https://www.anchorterminal.com/compare/grafana-mcp-server-vs-incident-io.md)
- [incident.io API vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/incident-io-vs-pagerduty-mcp.md)
- [incident.io API vs Rootly MCP Server](https://www.anchorterminal.com/compare/incident-io-vs-rootly-mcp.md)
- [Datadog MCP Server vs Sentry MCP](https://www.anchorterminal.com/compare/datadog-mcp-vs-sentry-mcp.md)
- [Datadog MCP Server vs Grafana MCP Server](https://www.anchorterminal.com/compare/datadog-mcp-vs-grafana-mcp-server.md)
- [Datadog MCP Server vs Honeycomb MCP](https://www.anchorterminal.com/compare/datadog-mcp-vs-honeycomb-mcp.md)