Datadog Mcp
Let your coding agent query Datadog monitors, logs, metrics, traces, and dashboards without leaving the editor.
Overview
Datadog MCP is a MCP server for the Operate phase that exposes Datadog monitors, logs, metrics, traces, and dashboards to your agent.
What is this MCP server?
- Monitors, logs, metrics, traces, and dashboards via MCP tools
- stdio npm package datadog-mcp 1.0.9
- DD_SITE support for US, EU, and regional Datadog tenants
- Pairs DD_API_KEY and DD_APP_KEY for full API access
- Agent-driven investigations during outages or regressions
- npm package datadog-mcp version 1.0.9 with stdio transport
- Coverage spans monitors, logs, metrics, traces, and dashboards per server description
Community signal: 4 GitHub stars.
What problem does it solve?
Production debugging means constantly context-switching between your IDE and Datadog’s UI while incidents drag on.
Who is it for?
Solo builders on Datadog who want agent-assisted incident review and observability queries.
Skip if: Teams without a Datadog account or builders who only need local dev logging.
What do I get? / Deliverables
Your agent pulls monitors, logs, metrics, and traces through MCP so you stay in one workflow during triage.
- Agent-accessible Datadog monitor and dashboard queries
- Log and metric lookups without manual UI navigation
- Trace-aware debugging context inside the coding session
Recommended MCP Servers
Journey fit
How it compares
Datadog API bridge via MCP, not a hosted monitoring product or a deployment skill.
Common Questions / FAQ
Who is Datadog MCP for?
Developers and solo operators who already use Datadog and want their AI coding agent to query observability data directly.
When should I use Datadog MCP?
Use it during Operate when debugging errors, correlating traces, checking monitor status, or summarizing dashboard metrics from the agent.
How do I add Datadog MCP to my agent?
Install npm datadog-mcp, set DD_API_KEY and DD_APP_KEY (and DD_SITE if needed), and register the stdio server in your MCP client config.