Developer · Local MCP server
Datadog
Datadog MCP - 165 tools for metrics, monitors, logs, APM, RUM, incidents, CI/CD, fleet.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.us-all/datadog- Version
- 1.21.1
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-06-19
- Updated
- 2026-06-19
- Publisher
- us-all (GitHub) · 8 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/us-all) · how
- Listed under
- Datadog MCP servers
- Repository
- github.com/us-all/datadog-mcp-server
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @us-all/datadog-mcp | 1.21.1 | stdio |
How to connect Datadog
Datadog runs locally from a Node.js package published to the npm registry: @us-all/datadog-mcp version 1.21.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @us-all/datadog-mcp@1.21.1. It reads these environment variables: DD_API_KEY (required, secret), DD_APP_KEY (required, secret), DD_SITE, DD_TOOLS, DD_DISABLE and DD_ALLOW_WRITE; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"datadog": {
"command": "npx",
"args": [
"-y",
"@us-all/datadog-mcp@1.21.1"
],
"env": {
"DD_API_KEY": "<secret>",
"DD_APP_KEY": "<secret>",
"DD_SITE": "<value>",
"DD_TOOLS": "<value>",
"DD_DISABLE": "<value>",
"DD_ALLOW_WRITE": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from us-all (GitHub)
| Server | Runs |
|---|---|
| AirflowAirflow MCP - list DAGs/runs/task instances, tail logs, trigger and clear (write-gated) | Local · stdio |
| AndroidAndroid MCP - ADB-based device, apps, UI, logcat, emulator, files, system, debug. | Local · stdio |
| DbtDbt MCP - manifest/run_results/sources/catalog parsing + DQ result tables (BigQuery/Postgres) | Local · stdio |
| Google DriveGoogle Drive + Workspace MCP - Docs, Sheets, Slides, Shared Drives, Labels, Approvals, DWD. | Local · stdio |
| MlflowMLflow MCP - experiments, runs, registered models, versions, traces, assessments (MLflow 3) | Local · stdio |
| OpenmetadataOpenMetadata MCP - metadata, lineage, search, data quality, OM 1.12+ Data Contracts. | Local · stdio |
| UnifiUniFi semantic-analysis MCP - fleet health, anomaly detection, cross-site analytics. | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| Databricks MCP Server263 tools for Databricks: Unity Catalog, SQL, Compute, Jobs, Serving, and more. | Local · stdio |
| Databutler StatsExact statistics & probability: distributions, hypothesis tests, CIs, Bayesian updates, regression. | Remote · HTTPLive check: ✓ handshake |
| DataClawe - Database as a UtilityAI-native database utility. Talk to your DB in plain language. No SQL. MySQL & PostgreSQL. | Remote · SSELive check: sign-in required |
| DatadogMonitor infrastructure, manage agents and deployments, track metrics, logs, and events. | Local · stdio |
| Datadog MCPFull Datadog API access: monitors, logs, metrics, traces, dashboards, and observability tools. | Local · stdio |
| dataecho.aiDeploy files, sites, and Dockerfile apps to live URLs + private drives for agent memory. | Remote · HTTPLive check: ✓ handshake |
| DatahogoScan a project for security issues locally with the open-source Data Hogo engine. | Local · stdio |
| DataLinkMCP server for secure database access (PostgreSQL, MySQL, SQLite) | Local · stdio |