Datadog MCP Server
The Datadog MCP that answers "why is this happening?" — not just "what's the value?"
Aggregation tools that fold 5–7 sequential API calls into one structured response. Full SLO CRUD. Fleet automation. The widest Datadog API coverage in any MCP — 163 tools built on the @us-all MCP standard.
What it does that others don't
- Aggregation tools —
analyze-monitor-stateandslo-compliance-snapshotcollapse 5–7 sequential API calls into one structured response with acaveatsarray for partial failures. No other Datadog MCP ships this pattern. - Full SLO CRUD — create, update, delete SLOs (and their corrections). The official Bits AI MCP and community alternatives are read-only on SLOs.
- Fleet Automation — 15 tools across deployments and schedules. Only this server.
- Status Pages — 21 tools for full status-page lifecycle (components, degradations, maintenances). Only this server.
- Token-efficient by design —
extractFieldsprojection,DD_TOOLS/DD_DISABLE16-category toggles, and asearch-toolsmeta-tool keep LLM context low across 163 tools. - Apps SDK card —
slo-compliance-snapshotrenders as a visual card on ChatGPT clients via_meta["openai/outputTemplate"]. Claude clients receive the same JSON content (non-breaking). - stdio + Streamable HTTP — defaults to stdio (Claude Desktop / Code). Set
MCP_TRANSPORT=httpfor ChatGPT Apps SDK or remote clients (Bearer auth viaMCP_HTTP_TOKEN).






