Datadog MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DD_SITE | No | Datadog site (e.g. datadoghq.eu, us5.datadoghq.com). | datadoghq.com |
| DD_API_KEY | Yes | API Key — identifies your Datadog organization. Found in Organization Settings → API Keys. | |
| DD_APP_KEY | Yes | Application Key — tied to a specific user account and grants that user's read permissions. Create one in Organization Settings → Application Keys. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_logsA | Search Datadog logs with structured filters or raw query. Returns log entries with timestamp, service, status, host, and message. |
| query_metricsA | Query Datadog timeseries metrics. Returns summary statistics (avg, min, max, latest) per series. |
| list_metricsA | Search available Datadog metric names. Useful for discovering what metrics exist before querying. |
| list_monitorsB | List Datadog monitors with optional filtering by name, tags, status, or type. |
| get_monitorA | Get full details for a specific Datadog monitor by ID, including query, message, thresholds, and options. |
| search_monitorsA | Full-text search across Datadog monitors. Searches name, query, tags, and message. |
| search_tracesA | Search Datadog APM traces/spans with structured filters or raw query. Returns span details with service, resource, duration, and status. |
| list_hostsC | List Datadog infrastructure hosts with status, CPU, load, and IOWait metrics. |
| get_host_totalsB | Get total counts of active and up hosts in Datadog. |
| list_dashboardsC | List Datadog dashboards with optional search filtering. |
| get_dashboardA | Get full details of a Datadog dashboard including widgets, queries, and layout. |
| list_eventsC | Search Datadog events (deploys, alerts, comments, etc.) with filtering. |
| list_incidentsC | List Datadog incidents with optional search filtering. |
| get_incidentA | Get full details of a specific Datadog incident by ID. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Tools target distinct Datadog resources (metrics, monitors, traces, logs, hosts, dashboards, events, incidents), so overlap is low. Minor ambiguity between list_monitors and search_monitors, since both can retrieve monitors with filtering.
Mostly consistent verb_noun style: list_*, get_*, search_*, query_*. The deviation is get_host_totals, which is noun-first rather than get_host_total/host resource style, but overall naming is readable and predictable.
14 tools is well-scoped for a Datadog observability surface. Each tool covers a distinct Datadog domain and earns its place without excessive redundancy.
The server provides strong read/search coverage across metrics, monitors, traces, logs, hosts, dashboards, events, and incidents. However, it is almost entirely read-only: there are no create, update, delete, mute, or incident management operations, leaving notable lifecycle gaps.