Datadog
Query metrics, logs, and events and manage Datadog agents or deployments from your coding agent in production.
Overview
Datadog is an MCP server for the Operate phase that monitors infrastructure and tracks metrics, logs, events, and agent deployments in Datadog.
What is this MCP server?
- Monitor infrastructure and track metrics, logs, and events in Datadog
- Manage agents and deployments through MCP-exposed operations
- mcparmory-datadog v1.0.3 with uvx or Docker stdio transport
- Supports agents triaging outages and config drift without leaving the IDE
- Published in mcparmory MCP registry from GitHub
- Registry version 1.0.3
- Capabilities span metrics, logs, events, agents, and deployments per description
- Dual package distribution: PyPI uvx and OCI Docker
Community signal: 25 GitHub stars.
What problem does it solve?
During incidents you bounce between the IDE, Datadog dashboards, and deployment notes while the agent lacks live observability context.
Who is it for?
Indie operators already on Datadog who want Claude Code or Cursor to investigate alerts and manage agents alongside code fixes.
Skip if: Projects with no observability stack, or teams that forbid agents from holding production API keys.
What do I get? / Deliverables
Your agent can pull Datadog metrics, logs, and events and perform allowed agent or deployment actions through MCP for faster production debugging.
- Agent access to Datadog metrics, logs, and events tooling
- Operational hooks for agents and deployments as exposed by the server
Recommended MCP Servers
Journey fit
Observability and incident context belong on Operate once you are running real traffic and need sustained visibility. Monitoring subphase is the canonical shelf for metrics, logs, events, and agent lifecycle against Datadog.
How it compares
Datadog observability MCP bridge, not a local log tail or synthetic monitoring skill.
Common Questions / FAQ
Who is com.mcparmory/datadog for?
Solo builders and small teams running production on Datadog who want agents to query telemetry and assist with agent or deployment management.
When should I use com.mcparmory/datadog?
Use it in operate and monitoring work when debugging live issues, reviewing logs and metrics, or adjusting Datadog-related deployment configuration via an agent.
How do I add com.mcparmory/datadog to my agent?
Configure the MCP server with stdio, start mcparmory-datadog through uvx or the ghcr.io/mcparmory/datadog image, and supply Datadog API and app keys securely.