← Back to directory
D

Datadog MCP Server

Community
Read-only access to Datadog monitoring data via MCP
GitHub source repository ↗
★ 69 Stars Category · Dev Tools Popular
62FMRS · C

A community-maintained MCP server, documented in the README, offering read-only access to monitors, dashboards, metrics, events, logs, and incidents via Datadog's official APIs. The tool set is clear, regional endpoints and scoped keys are supported, and security guidance is sensible — but it is a third-party project with no write capabilities.

Reliability
7/20
Security and permissions
15/20
Maintenance
10/20
Documentation
16/20
Setup experience
14/20
Read the FMRS scoring method →

Datadog MCP Server is a Model Context Protocol server that provides read-only access to monitors, dashboards, metrics, events, logs, and incident data through Datadog's official v1 and v2 APIs. It supports multiple Datadog regional endpoints (US, EU, US3, US5, AP1) and separate endpoints for logs and metrics. Configuration is via environment variables (DD_API_KEY, DD_APP_KEY, DD_SITE, etc.) or command-line arguments. This is a community-maintained project (GeLi2001/datadog-mcp-server), not an official Datadog product, licensed under MIT.

Tools

get-monitors
Fetch monitors with optional filtering
get-monitor
Get details of a specific monitor by ID
get-dashboards
List all dashboards
get-dashboard
Get a specific dashboard by ID
get-metrics
List available metrics
get-metric-metadata
Get metadata for a specific metric
get-events
Fetch events within a time range
get-incidents
List incidents with optional filtering
search-logs
Search logs with advanced query filtering
aggregate-logs
Perform analytics and aggregations on log data

Setup

  1. Prepare Node.js 16+ and a Datadog API key and Application key (created in Organization Settings). 2. Install globally via npm: npm install -g datadog-mcp-server, or build from source with npm install && npm run build. 3. Add an mcpServers entry to Claude Desktop's claude_desktop_config. using npx datadog-mcp-server with --apiKey, --appKey, and --site arguments; the config file is at ~/Library/Application Support/Claude/ on macOS or %APPDATA%/Claude/ on Windows. 4. Alternatively debug with MCP Inspector: npx @modelcontextprotocol/inspector datadog-mcp-server --apiKey=... --appKey=...
claude_desktop_config.json
{"mcpServers":{"datadog":{"command":"npx","args":["datadog-mcp-server","--apiKey","<YOUR_API_KEY>","--appKey","<YOUR_APP_KEY>","--site","<YOUR_DD_SITE>"]}}}

Fit and risk

Best for

  • Ops and SRE teams using Claude Desktop who need read-only access to Datadog data
  • Developers who want monitors, logs, and metrics queries inside LLM workflows
  • Teams practicing least privilege who can scope their Application Keys

Not for

  • Scenarios requiring write operations to Datadog (creating/modifying monitors, muting, etc.) — the server offers read-only tools only
  • Users without a Datadog account, API key, and Application key
  • Those requiring official Datadog support — this is a community project, not official

Required permissions

  • DD_API_KEY: Datadog API key
  • DD_APP_KEY: Datadog Application key, recommended scopes per feature: monitors_read, dashboards_read, metrics_read, events_read, logs_read_data, incident_read
  • Application Keys without explicit scopes inherit all permissions of the creating user

Risks and side effects

  • Leaked API or Application keys expose organizational monitoring and log data
  • Application Keys without scopes carry the creator's full permissions, violating least privilege
  • Third-party community project, not audited by Datadog
  • Logs and metrics may contain sensitive business data entering LLM context — consider compliance implications

Troubleshooting

  1. 403 Forbidden: verify API and Application keys are correct, have required permissions, and the account can access the data
  2. Confirm the correct regional endpoint (e.g., datadoghq.eu for EU customers)
  3. Invalid key format errors: ensure you are using the full key strings
  4. Endpoint mismatches: if logs and metrics use different domains, check --logsSite and --metricsSite settings
  5. Check Claude Desktop MCP logs (macOS: ~/Library/Logs/Claude/mcp*.log, Windows: %APPDATA%/Claude/Logs/)

Use cases

Query Datadog monitor states and configurations in conversation
Inspect dashboard definitions by ID
Search and aggregate logs for troubleshooting
Look up metric metadata and event stream data
Review active incidents

Supported clients

Claude DesktopFull support