Datadog MCP Server

MCP Server for Datadog API. That is what the datadog mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

A Model Context Protocol (MCP) server for interacting with the Datadog API.

• Monitoring — Access monitor data and configurations
• Dashboards — Retrieve and view dashboard definitions
• Metrics — Query available metrics and their metadata
• Events — Search and retrieve events within timeframes
• Logs — Search logs with advanced filtering and sorting options
• Incidents — Access incident management data

The tools it exposes

The server publishes 12 tools. What each one is for:

• MacOS — ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows — %APPDATA%/Claude/claude_desktop_config.json
• 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

Getting it running

The server ships on npm as @modelcontextprotocol/inspector, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What it needs from you

Configuration is passed through the environment: DD_API_KEY, DD_APP_KEY, YOUR_API_KEY, YOUR_APP_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

1. Node.js (version 16 or higher) 2. Datadog account with: - API key - Found in Organization Settings > API Keys - Application key - Found in Organization Settings > Application Keys

How it compares

Among the monitoring and observability options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Datadog's toolset — MacOS, Windows, get-monitors and 9 more — is a fair guide to whether it matches your workflow. It is maintained by GeLi2001; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Datadog's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 12 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Datadog.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.