← Back to directory
D

Datadog MCP Server

Community
MCP server for the Datadog API, enabling incident management and more.
GitHub source repository ↗
★ 143 Stars Category · Dev Tools Popular Source revision 24f2c5472861
33FMRS · D
Reliability
4/20
Security and permissions
6/20
Maintenance
6/20
Documentation
9/20
Setup experience
8/20

Community-maintained Datadog MCP server with broad coverage of Datadog features including incidents, monitoring, logs, and RUM, designed to be extensible. Requires proper configuration of Datadog API credentials.

Read the FMRS scoring method →

mcp-server-datadog is a community-maintained MCP server that integrates Datadog's observability capabilities into the MCP ecosystem. It provides a set of tools for managing incidents, retrieving monitors, logs, dashboards, metrics, APM traces, and managing hosts and downtimes, as well as RUM (Real User Monitoring) features. This server is developed independently and is not officially endorsed by Datadog.

Tools

list_incidents
Retrieve a list of incidents from Datadog with optional filters and pagination.
get_incident
Retrieve detailed information about a specific Datadog incident.
get_monitors
Fetch the status of Datadog monitors, filterable by state, name, and tags.
get_logs
Search and retrieve logs from Datadog using a query and time range.
list_dashboards
Get a list of dashboards from Datadog, filterable by name and tags.
get_dashboard
Retrieve a specific dashboard from Datadog by ID.
query_metrics
Retrieve metrics data from Datadog for a specified time range.
list_traces
Get a list of APM traces with query, time range, service, operation, and sorting filters.
list_hosts
Get a list of hosts from Datadog with filtering, sorting, pagination, and metadata options.
get_active_hosts_count
Get the total number of active hosts in Datadog.
mute_host
Mute a host in Datadog with optional message and end time.
unmute_host
Unmute a host in Datadog.
list_downtimes
List scheduled downtimes from Datadog, optionally filtering by current only or monitor ID.
schedule_downtime
Schedule a downtime in Datadog with scope, start/end times, message, timezone, monitor, and recurrence settings.
cancel_downtime
Cancel a scheduled downtime in Datadog by ID.
get_rum_applications
Get all RUM applications in the organization.
get_rum_events
Search and retrieve RUM events from Datadog using a query and time range.
get_rum_grouped_event_count
Search, group, and count RUM events by a specified dimension.
get_rum_page_performance
Get page (view) performance metrics from RUM data, including average, min, max, and count.
get_rum_page_waterfall
Retrieve RUM page (view) waterfall data filtered by application name and session ID.

Setup

  1. Ensure Node.js and pnpm are installed. 2. Clone the repository and run pnpm install and pnpm build. 3. Set environment variables DATADOG_API_KEY and DATADOG_APP_KEY (required), and optionally DATADOG_SITE, DATADOG_SUBDOMAIN, and DATADOG_STORAGE_TIER. 4. Configure the server in your MCP client using npx -y @winor30/mcp-server-datadog or point to the built build/index.js. 5. For automated installation, run npx -y @smithery/cli install @winor30/mcp-server-datadog --client claude.
claude_desktop_config.json
{
  "mcpServers": {
    "mcp-server-datadog": {
      "command": "npx",
      "args": [
        "-y",
        "@winor30/mcp-server-datadog"
      ],
      "env": {
        "DATADOG_API_KEY": "<YOUR_API_KEY>",
        "DATADOG_APP_KEY": "<YOUR_APP_KEY>",
        "DATADOG_SITE": "<YOUR_SITE>",
        "DATADOG_SUBDOMAIN": "<YOUR_SUBDOMAIN>",
        "DATADOG_STORAGE_TIER": "indexes"
      }
    }
  }
}

Fit and risk

Best for

  • Developers and SREs looking to integrate Datadog operations into AI-assisted workflows
  • Teams using Claude Desktop and other MCP-compatible clients

Not for

  • Users seeking official Datadog support
  • Those needing advanced Datadog API operations beyond the current tool set
  • Users unfamiliar with Datadog API authentication

Required permissions

  • Requires Datadog API key and application key with permissions for the used APIs, such as incidents, monitors, logs, dashboards, metrics, APM, hosts, downtimes, and RUM.

Risks and side effects

  • Community-maintained, unofficial, may have bugs or unexpected behavior
  • MCP server runs with persistent API keys, which can be leaked if not secured
  • Some operations like muting hosts or scheduling downtimes can have significant impact if misconfigured
  • API calls may consume Datadog quota or incur costs

Troubleshooting

  1. Verify DATADOG_API_KEY and DATADOG_APP_KEY are set correctly and have sufficient permissions.
  2. Check DATADOG_SITE and DATADOG_SUBDOMAIN match your Datadog account.
  3. Inspect MCP server logs, and use MCP Inspector (`npm run inspector`) for detailed debugging.
  4. Ensure the server executable path is correct or that `npx` commands can access the network.

Use cases

Manage Datadog incidents directly within your MCP client
Quickly query Datadog monitors, logs, dashboards, and metrics
Perform host mute/unmute and downtime scheduling without switching context
Monitor user experience through RUM tools

Supported clients

Claude DesktopFull support