22 tools · Dual-Key Auth · Open Source

Datadog MCP Server

Connect your AI assistant to Datadog through the Model Context Protocol. 22 read tools, dual-key authentication, zero data stored.

22 Read · Dual-Key Auth · Multi-Site · Zero Storage

Get Started GitHub

Quick Start

1 Get your Datadog API Keys

Go to Datadog API Keys and create an API Key. Then go to Application Keys and create an Application Key. Both are required for authentication.

2 Know your Datadog site (optional)

If you use a non-US1 Datadog site, note your site domain: datadoghq.com (US1, default), us3.datadoghq.com (US3), us5.datadoghq.com (US5), datadoghq.eu (EU1), ap1.datadoghq.com (AP1), ddog-gov.com (GOV).

3 Configure your MCP client

Choose your client below and add the configuration. You'll need both keys as header values.

See the MCP Client Configuration section below for detailed setup instructions for each client.

MCP Client Configuration

Claude Desktop Claude Code Cursor VS Code

macOS ~/Library/Application Support/Claude/claude_desktop_config.json
Linux ~/.config/Claude/claude_desktop_config.json
Windows %APPDATA%\Claude\claude_desktop_config.json

Claude Desktop's built-in Custom Connector does not support custom headers. Use the mcp-remote wrapper instead.

Dual-Key Authentication

json

{
  "mcpServers": {
    "datadog": {
      "command": "bunx",
      "args": [
        "mcp-remote",
        "https://mcp-datadog.flaremity.com/mcp",
        "--header",
        "DD-API-KEY: ${DD_API_KEY}",
        "--header",
        "DD-APPLICATION-KEY: ${DD_APP_KEY}"
      ],
      "env": {
        "DD_API_KEY": "<your-api-key>",
        "DD_APP_KEY": "<your-application-key>"
      }
    }
  }
}

Non-US1 site variant

json

{
  "mcpServers": {
    "datadog": {
      "command": "bunx",
      "args": [
        "mcp-remote",
        "https://mcp-datadog.flaremity.com/mcp",
        "--header",
        "DD-API-KEY: ${DD_API_KEY}",
        "--header",
        "DD-APPLICATION-KEY: ${DD_APP_KEY}",
        "--header",
        "X-Datadog-Site: ${DD_SITE}"
      ],
      "env": {
        "DD_API_KEY": "<your-api-key>",
        "DD_APP_KEY": "<your-application-key>",
        "DD_SITE": "datadoghq.eu"
      }
    }
  }
}

Dual-Key Authentication

bash

claude mcp add datadog \
  https://mcp-datadog.flaremity.com/mcp \
  --transport http \
  --header "DD-API-KEY: <your-api-key>" \
  --header "DD-APPLICATION-KEY: <your-application-key>"

Or edit config file directly

json

{
  "mcpServers": {
    "datadog": {
      "type": "http",
      "url": "https://mcp-datadog.flaremity.com/mcp",
      "headers": {
        "DD-API-KEY": "<your-api-key>",
        "DD-APPLICATION-KEY": "<your-application-key>"
      }
    }
  }
}

Project .mcp.json (project root)
User ~/.claude.json (macOS/Linux)
User %USERPROFILE%\.claude.json (Windows)

Add via Settings → MCP → Add MCP Server, or edit config file directly.

Global ~/.cursor/mcp.json
Project .cursor/mcp.json

Dual-Key Authentication

json

{
  "mcpServers": {
    "datadog": {
      "command": "bunx",
      "args": [
        "mcp-remote",
        "https://mcp-datadog.flaremity.com/mcp",
        "--header",
        "DD-API-KEY: ${DD_API_KEY}",
        "--header",
        "DD-APPLICATION-KEY: ${DD_APP_KEY}"
      ],
      "env": {
        "DD_API_KEY": "<your-api-key>",
        "DD_APP_KEY": "<your-application-key>"
      }
    }
  }
}

.vscode/mcp.json (cross-platform)

Dual-Key Authentication

json

{
  "servers": {
    "datadog": {
      "url": "https://mcp-datadog.flaremity.com/mcp",
      "type": "http",
      "headers": {
        "DD-API-KEY": "<your-api-key>",
        "DD-APPLICATION-KEY": "<your-application-key>"
      }
    }
  }
}

Features

📊

22 Datadog Tools

Monitors, dashboards, logs, metrics, events, incidents, hosts, APM traces, containers, downtimes, and software catalog — all accessible via MCP.

🌍

Multi-Site Support

Works with all Datadog sites: US1, US3, US5, EU1, AP1, and GOV. Set via the X-Datadog-Site header.

🔐

Dual-Key Auth

Secure authentication with both API Key and Application Key via DD-API-KEY and DD-APPLICATION-KEY headers.

🛡️

Read-Only by Default

22 read-only tools across 11 domains. Write tools coming soon with READ_ONLY_MODE support.

⚡

Anti-Hanging Design

Fetch timeouts, 5MB response size guards, metric point caps, and response simplification.

☁️

Zero Data Storage

Stateless proxy on Cloudflare Workers. No database, no logs, no data retention.

Tools Catalog

22 read tools organized by category

Monitors 2 tools

list_monitors List monitors with name, tag, and state filters Read

get_monitor Get monitor details by ID Read

Dashboards 2 tools

list_dashboards List all dashboards with title and layout type Read

get_dashboard Get dashboard details including widgets Read

Logs 2 tools

search_logs Search logs with query and time range Read

aggregate_logs Aggregate logs with compute and group-by Read

Metrics 4 tools

query_metrics Query metric timeseries data Read

search_metrics Search metrics by name Read

get_metric_metadata Get metric metadata (type, unit, description) Read

list_active_metrics List actively reporting metrics Read

Events 2 tools

search_events Search events with query and time range Read

get_event Get event details by ID Read

Incidents 2 tools

list_incidents List incidents with pagination Read

get_incident Get incident details by ID Read

Hosts 2 tools

list_hosts List hosts with filtering and sorting Read

get_host_totals Get total active and up host counts Read

APM Traces 2 tools

search_spans Search APM trace spans with query and time range Read

aggregate_spans Aggregate spans with compute and group-by Read

Containers 2 tools

list_containers List containers with tag filtering Read

list_container_images List container images in infrastructure Read

Downtimes 2 tools

list_downtimes List scheduled downtimes Read

get_downtime Get downtime details by ID Read

Software Catalog 2 tools

list_service_definitions List service definitions from Software Catalog Read

get_service_definition Get service definition by name Read

FAQ

What Datadog keys do I need?

You need two keys: an API Key (from Organization Settings → API Keys) and an Application Key (from Organization Settings → Application Keys). Both are required for all API calls.

Does this work with non-US1 Datadog sites?

Yes. Add the X-Datadog-Site header with your site domain (e.g. datadoghq.eu for EU1, us3.datadoghq.com for US3). The server defaults to datadoghq.com (US1) if no site header is provided.

Are write operations supported?

The server currently provides 22 read-only tools across 11 domains (monitors, dashboards, logs, metrics, events, incidents, hosts, APM traces, containers, downtimes, and software catalog). Write tools are planned for a future release. The server also supports READ_ONLY_MODE to ensure no accidental modifications.

Where is my data stored?

Nowhere. This server is a stateless proxy running on Cloudflare Workers. It does not store any of your Datadog data, credentials, or API responses. Each request is processed and immediately discarded. No database, no logs, no KV storage.

Can I self-host this?

Yes. Clone the repository, run bun install, and deploy to your own Cloudflare Workers account with bun run deploy. Set your keys via wrangler secret put DD_API_KEY and wrangler secret put DD_APP_KEY.