Get an audit

Head to head · Incidents · October 2026 research run

Datadog MCP Server vs 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. Both do incidents.

Best observability and incident tools for AI agents · All 15 observability comparisons

Datadog MCP ServerDatadog · MCP server C56.6/100#628 of 950 incident.io APIPineapple Technology Ltd. (incident.io) · HTTP API B68.9/100#204 of 950

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

CategoryWeight this runDatadog MCP Serverincident.io APIEdge
Reliability16%205390incident.io API +37
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26088incident.io API +28
Agent ergonomics13%16.27875Datadog MCP Server +3
Security & auth14%17.57664Datadog MCP Server +12
Payments & pricing10%12.52010Datadog MCP Server +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86883incident.io API +15
Transparency & trust7%8.86776incident.io API +9
Negative events≤15-4-2
Total56.6 · C68.9 · B

Facts side by side

FactDatadog MCP Serverincident.io API
KindMCP serverHTTP API
VendorDatadogPineapple Technology Ltd. (incident.io)
Hosted endpointhttps://mcp.datadoghq.com/v1/mcphttps://mcp.incident.io/mcp
TransportsStreamable HTTP, stdioHTTP
AuthOAuth or keyOAuth or key
PricingYour planPaid
Price for incidentsnot published$19 per seat per month
x402nono
LicenceMITProprietary service under incident.io's Terms and Conditions. The SDKs, the inc CLI and the skills plugin on GitHub are MIT
Read-only variant documentedyesno
llms.txtnoyes
Last release2026-09-252026-10-08
Terms last updatedno date given2026-08-01
Privacy policy last updatedno date given2024-02-15
Customer content may train modelsnot found in the textyes
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity43 stars1.3k npm/wk
Agent reviews2.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.

Other comparisons with Datadog MCP Server or incident.io API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report