get-monitorsLABSCO SUMMARY
The dashboard you would have gone to open, answered in place.
During an incident the cost is not reading Datadog, it is getting to the right view. Monitors, logs, events and the incident record all land in the same thread as the theory you are testing — and the key can be scoped read-only, so the agent cannot change what it finds.
What it is
An MCP server over the Datadog API, v1 and v2. It reads monitors, dashboards, metric metadata, events, logs and incidents, with support for separate endpoints where your Datadog site uses different ones for logs and metrics.
What you get
- Monitors listed and read individually, with their configurations and states
- Dashboards listed and their definitions retrieved
- Available metrics listed, with metadata for any one of them
- Events searched and retrieved within a timeframe
- Logs searched with filtering and sorting, and aggregated
- Incident management data read
Requirements
A recent Node.js, a Datadog API key from Organization Settings → API Keys, and an Application key from Organization Settings → Application Keys. Application keys inherit every permission of the user who created them, so make a scoped one instead: monitors_read, dashboards_read, metrics_read, events_read, logs_read_data and incident_read cover everything here, and nothing in the server needs write access.
Setup effort
One command plus a key — npm install -g datadog-mcp-server, then supply credentials
USE CASES
01
Working out what is alerting right now
List the monitors, then read the one that fired in full.
02
Chasing an error through the logs
Search logs with filters and sorting, then aggregate to see how widespread it is.
03
Lining a spike up with something that happened
Pull events within the timeframe around it.
04
Finding out what a metric actually measures
List the available metrics and read the metadata before building a query on one.
05
Reading the dashboard without opening it
List the dashboards and retrieve the definition of the one you would have gone to.
06
Writing up an incident
Read the incident record alongside the monitors from the same window.
10 tools
Listed in project docs. Your client may show a different list.
get-monitorget-dashboardsget-dashboardget-metricsget-metric-metadataget-eventsget-incidentssearch-logsaggregate-logsBEFORE YOU INSTALL
What to know first
Tools you get
10 tools named in the project's documentation.
Requires
- npm on PATH
- A Datadog API key and Application key, passed as --apiKey and --appKey (or set as DD_API_KEY and DD_APP_KEY)
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npm install -g datadog-mcp-serverMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"datadog": {
"command": "npx",
"args": [
"datadog-mcp-server",
"--apiKey",
"<YOUR_API_KEY>",
"--appKey",
"<YOUR_APP_KEY>",
"--site",
"<YOUR_DD_SITE>"
]
}
}
}<YOUR_API_KEY> and <YOUR_APP_KEY> are your Datadog API key and Application key, and <YOUR_DD_SITE> is your Datadog site, for example datadoghq.com, datadoghq.eu or us5.datadoghq.com, without https://.
