GitHub
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Description from the maker (original English)
Datadog MCP — 165 tools for metrics, monitors, logs, APM, RUM, incidents, CI/CD, fleet
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
DD_API_KEY, DD_APP_KEY, DD_SITE, DD_TOOLS, DD_DISABLE, DD_ALLOW_WRITEValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"datadog": {
"command": "npx",
"args": [
"-y",
"@us-all/datadog-mcp"
],
"env": {
"DD_API_KEY": "your-value",
"DD_APP_KEY": "your-value",
"DD_SITE": "your-value",
"DD_TOOLS": "your-value",
"DD_DISABLE": "your-value",
"DD_ALLOW_WRITE": "your-value"
}
}
}
}Run this in your terminal
claude mcp add datadog --env DD_API_KEY=your-value --env DD_APP_KEY=your-value --env DD_SITE=your-value --env DD_TOOLS=your-value --env DD_DISABLE=your-value --env DD_ALLOW_WRITE=your-value -- npx -y @us-all/datadog-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"datadog": {
"command": "npx",
"args": [
"-y",
"@us-all/datadog-mcp"
],
"env": {
"DD_API_KEY": "your-value",
"DD_APP_KEY": "your-value",
"DD_SITE": "your-value",
"DD_TOOLS": "your-value",
"DD_DISABLE": "your-value",
"DD_ALLOW_WRITE": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"datadog": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@us-all/datadog-mcp"
],
"env": {
"DD_API_KEY": "your-value",
"DD_APP_KEY": "your-value",
"DD_SITE": "your-value",
"DD_TOOLS": "your-value",
"DD_DISABLE": "your-value",
"DD_ALLOW_WRITE": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
DD_SITE envDD_TOOLS envDD_DISABLE envDD_ALLOW_WRITE envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account us-all, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: DD_API_KEY, DD_APP_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.21.1) reached the registry 5 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
analyze-monitor-state and slo-compliance-snapshot collapse 5–7 sequential API calls into one structured response with a caveats array for partial failures. No other Datadog MCP ships this pattern.extractFields projection, DD_TOOLS/DD_DISABLE 16-category toggles, and a search-tools meta-tool keep LLM context low across 163 tools.slo-compliance-snapshot renders as a visual card on ChatGPT clients via _meta["openai/outputTemplate"]. Claude clients receive the same JSON content (non-breaking).MCP_TRANSPORT=http for ChatGPT Apps SDK or remote clients (Bearer auth via MCP_HTTP_TOKEN).Connect the server to Claude Desktop or Claude Code, then paste any of these:
checkout-service. Pull the linked monitors, the recent error spikes from APM, and which deployments touched the service in the last 24h."*datadog-agent 7.55.0 rollout to the staging cluster, weekends only, starting next Saturday."*Datadog's official MCP (Bits AI MCP, GA 2026-03-09) is complementary, not a replacement:
| Official Datadog MCP | @us-all/datadog-mcp (this) | |
|---|---|---|
| Tool count | 16+ core toolsets | 163 tools across full API surface |
| Deployment | Remote (managed by Datadog) | Self-host stdio (npx / Docker / npm) |
| Auth | Datadog SSO | API + APP key |
| Sites | Public Datadog sites | Any site, incl. internal/sovereign; US5 default |
| SLO writes | ❌ | ✅ create/update/delete SLOs + corrections |
| Fleet automation | ❌ | ✅ 15 tools |
| Status pages | ❌ | ✅ 21 tools |
| Aggregation tools | ❌ | ✅ analyze-monitor-state, slo-compliance-snapshot |
| MCP Prompts | ❌ | ✅ 4 (triage-incident, audit-monitor-noise, analyze-rum-error-spike, investigate-slow-trace) |
| MCP Resources | ❌ | ✅ dd://service/{serviceName}, dd://team/{teamId}, dd://synthetics/{testId}, etc. |
Use the official Bits AI MCP for fast managed onboarding and SSO. Use this when you need full API coverage, SLO/fleet/status-page write parity, or self-hosting (internal sites, isolated networks, dev/CI sandboxes).
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": { "datadog": { "command": "npx", "args": ["-y", "@us-all/datadog-mcp"], "env": { "DD_API_KEY": " ", "DD_APP_KEY": " ", "DD_SITE": "datadoghq.com" } } } }
claude mcp add datadog -s user \
-e DD_API_KEY= -e DD_APP_KEY= -e DD_SITE=datadoghq.com \ -- npx -y @us-all/datadog-mcp
docker run -e DD_API_KEY=... -e DD_APP_KEY=... -e DD_SITE=datadoghq.com \
ghcr.io/us-all/datadog-mcp-server:latest
git clone https://github.com/us-all/datadog-mcp-server.git
cd datadog-mcp-server && pnpm install && pnpm build node dist/index.js
| Variable | Required | Default | Description |
|---|---|---|---|
DD_API_KEY | ✅ | — | Datadog API key |
DD_APP_KEY | ✅ | — | Datadog Application key |
DD_SITE | ❌ | us5.datadoghq.com | Datadog site (see table below) |
DD_ALLOW_WRITE | ❌ | false | Set true to enable mutations (create/update/delete) |
DD_TOOLS | ❌ | — | Comma-sep allowlist of categories. Only these load — biggest token saver. |
DD_DISABLE | ❌ | — | Comma-sep denylist. Ignored when DD_TOOLS is set. |
MCP_TRANSPORT | ❌ | stdio | http to enable Streamable HTTP transport |
MCP_HTTP_TOKEN | conditional | — | Bearer token. Required when MCP_TRANSPORT=http |
MCP_HTTP_PORT | ❌ | 3000 | HTTP listen port |
MCP_HTTP_HOST | ❌ | 127.0.0.1 | HTTP bind host (DNS rebinding protection auto-enabled for localhost) |
MCP_HTTP_SKIP_AUTH | ❌ | false | Skip Bearer auth — e.g. behind a reverse proxy that handles it |
Categories (16): metrics, monitors, dashboards, logs, apm, rum, incidents, security, synthetics, ci, infra, fleet, status-pages, oncall, teams, account.
When MCP_TRANSPORT=http: POST /mcp (Bearer-auth JSON-RPC) + GET /health (public liveness).
Sites:
| Site | Value | Region |
|---|---|---|
| US1 | datadoghq.com | US (Virginia) |
| US3 | us3.datadoghq.com | US (Virginia) |
| US5 | us5.datadoghq.com | US (Oregon) |
| EU1 | datadoghq.eu | EU (Frankfurt) |
| AP1 | ap1.datadoghq.com | Asia-Pacific (Tokyo) |
Naive setup loads ~25K tokens of tool schema before any conversation. Three knobs mitigate:
| Scenario | Tools | Schema tokens | vs default |
|---|---|---|---|
| default (all categories) | 163 | 25,200 | — |
typical (DD_TOOLS=metrics,monitors,logs,apm,dashboards) | 55 | 9,300 | −63% |
narrow (DD_TOOLS=metrics,monitors) | 24 | 3,800 | −85% |
DD_TOOLS=metrics,monitors,logs,apm (biggest win).get-dashboard { dashboardId: "abc", extractFields: "id,title,widgets.*.definition.type" }.By default, all writes are blocked to prevent accidental mutations by AI agents. The following require DD_ALLOW_WRITE=true:
create-monitor, update-monitor, delete-monitor, mute-monitor, create-dashboard, update-dashboard, delete-dashboard, send-logs, post-event, trigger-synthetics, create-synthetics-test, update-synthetics-test, delete-synthetics-test, create-downtime, cancel-downtime, create-case, update-case-status, send-dora-deployment, send-dora-incident, create-slo, update-slo, delete-slo, plus all fleet/status-page/security writes.
Workflow templates the model can invoke directly:
triage-incident — given an incident ID, walks linked monitors, recent error spikes, and recent deploys.audit-monitor-noise — flag flapping monitors via alert frequency × MTTR.analyze-rum-error-spike — diff RUM error rates across two windows, attribute to top error groups.investigate-slow-trace — given a slow trace ID, traverse the span tree and surface bottleneck spans.Read-only entities by URI: dd://monitor/{id}, dd://dashboard/{id}, dd://slo/{id}, dd://incident/{id}, dd://service/{serviceName}, dd://team/{teamId} (team + members), dd://synthetics/{testId}, dd://host/{name}.
163 tools across 16 categories. Use the search-tools meta-tool to discover at runtime; the full list is collapsed below.
| Domain | Tools |
|---|---|
| Status Pages | 21 |
| RUM (events + apps + metrics + retention) | 27 |
| Metrics, Hosts, SLOs, Downtimes, Containers, Processes | 19 |
| Fleet Automation | 15 |
| Synthetics, Logs/Spans Metrics, SLO Corrections | 16 |
| Monitors, Dashboards, Notebooks, Events | 16 |
| Incidents, Cases, Error Tracking, Audit | 13 |
| OnCall, Teams, Users, Services, Bots | 11 |
| Security signals + rules + suppressions | 9 |
| APM, CI Visibility, DORA, Network Devices | 9 |
| + aggregations | analyze-monitor-state, slo-compliance-snapshot |
| + meta | search-tools |
Full tool list (click to expand)
query-metrics, get-metrics, get-metric-metadata, list-active-metrics, list-metric-tags
get-monitors, get-monitor, create-monitor, update-monitor, delete-monitor, mute-monitor, validate-monitor, analyze-monitor-state *(aggregation)*
get-dashboards, get-dashboard, create-dashboard, update-dashboard, delete-dashboard
search-logs, aggregate-logs, send-logs
get-events, post-event
get-incidents, get-incident, search-incidents, create-incident, update-incident, delete-incident
search-spans
search-rum-events, aggregate-rum, list-rum-applications, get-rum-application, create-rum-application, update-rum-application, delete-rum-application, list-rum-metrics, get-rum-metric, create-rum-metric, update-rum-metric, delete-rum-metric, list-rum-retention-filters, get-rum-retention-filter, create-rum-retention-filter, update-rum-retention-filter, delete-rum-retention-filter
list-slos, get-slo, get-slo-history, create-slo, update-slo, delete-slo, slo-compliance-snapshot *(aggregation)*, plus 5 SLO-correction tools
list-synthetics, get-synthetics-result, trigger-synthetics, create-synthetics-test, update-synthetics-test, delete-synthetics-test
list-hosts, get-host-totals, list-containers, list-processes
list-downtimes, create-downtime, cancel-downtime
search-security-signals, get-security-signal, list-security-rules, get-security-rule, delete-security-rule, list-security-suppressions, get-security-suppression, create-security-suppression, delete-security-suppression
search-ci-pipelines, aggregate-ci-pipelines, search-ci-tests, aggregate-ci-tests
list-cases, get-case, create-case, update-case-status
list-error-tracking-issues, get-error-tracking-issue
send-dora-deployment, send-dora-incident
list-network-devices, get-network-device
list-notebooks, get-notebook
get-team-oncall, `get-oncall-schedul
Only the beginning is shown; read the rest in the repo