Datadog runs on your own machine — the client starts it, so there is no endpoint to ping. 461 installs a week from npm. Last commit 10 Jul 2026.
Datadog MCP — 165 tools for metrics, monitors, logs, APM, RUM, incidents, CI/CD, fleet
What the code does
We read the source, 2 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
function update(){ document.getElementById('app').innerHTML = render(window.openai && window.openai.toolOutput); }
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add datadog -e 'DD_API_KEY=<DD_API_KEY>' -e 'DD_APP_KEY=<DD_APP_KEY>' -- npx -y @us-all/datadog-mcp{
"mcpServers": {
"datadog": {
"command": "npx",
"args": [
"-y",
"@us-all/datadog-mcp"
],
"env": {
"DD_API_KEY": "<DD_API_KEY>",
"DD_APP_KEY": "<DD_APP_KEY>"
}
}
}
}[mcp_servers.datadog]
command = "npx"
args = ["-y", "@us-all/datadog-mcp"]
env = { DD_API_KEY = "<DD_API_KEY>", DD_APP_KEY = "<DD_APP_KEY>" }{
"mcpServers": {
"datadog": {
"command": "npx",
"args": [
"-y",
"@us-all/datadog-mcp"
],
"env": {
"DD_API_KEY": "<DD_API_KEY>",
"DD_APP_KEY": "<DD_APP_KEY>"
}
}
}
}{
"servers": {
"datadog": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@us-all/datadog-mcp"
],
"env": {
"DD_API_KEY": "<DD_API_KEY>",
"DD_APP_KEY": "<DD_APP_KEY>"
}
}
}
}Put your own values in place of
<DD_API_KEY> (Datadog API key), <DD_APP_KEY> (Datadog application key).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
DD_SITE (Datadog site (datadoghq.com, datadoghq.eu, us3.datadoghq.com, etc.)), DD_TOOLS (Comma-separated category allowlist (e.g. metrics,monitors,logs). Default: all categories enabled), DD_DISABLE (Comma-separated category disablelist), DD_ALLOW_WRITE (Set to 'true' to enable write/destructive tools. Default read-only).
Alternatives to Datadog
same job, measured the same wayDatadog metrics, dashboards, logs, incidents, and monitors from your MCP client.
Full Datadog API access: monitors, logs, metrics, traces, dashboards, and observability tools
Manage uptime monitors and incidents and search logs, metrics and traces from an AI assistant.
Monitoring for small teams. Logs, traces, metrics, live issue tracking, API/MCP uptime.
Monitor infrastructure, manage agents and deployments, track metrics, logs, and events
MCP server for Dynatrace Managed to access logs, events, and metrics.
Client-website monitoring for agencies: uptime, incidents, SSL/domain expiry, server metrics.
An MCP server that provides tools for managing and monitoring your Fleet Device Management instance.
Datadog — questions
Answers built from our own checks of this server.