home / mcp / datadog mcp server

Datadog MCP Server

Provides MCP access to Datadog data for monitors, metrics, dashboards, logs, events, and incidents.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "abhi276k-datadog-mcp": {
      "command": "node",
      "args": [
        "/absolute/path/to/datadog/index.js"
      ],
      "env": {
        "DD_SITE": "datadoghq.com",
        "DD_API_KEY": "YOUR_API_KEY",
        "DD_APP_KEY": "YOUR_APP_KEY"
      }
    }
  }
}

You can run a Datadog MCP Server locally to access Datadog monitors, metrics, dashboards, logs, events, and incidents through a lightweight MCP interface. This lets you query and manage Datadog data from your MCP-enabled clients with consistent tooling and scripts.

How to use

Start by configuring your MCP client to connect to the Datadog MCP Server as a local, stdio-based server. You run the server on your machine and point your MCP client to it, allowing you to fetch monitors, metrics, dashboards, logs, events, and incidents from Datadog through familiar MCP endpoints.

How to install

Prerequisites: you need Node.js and npm installed on your system.

Install dependencies for the MCP server package.

npm install

Configure Datadog credentials by creating a local environment file from a template and placing your keys inside. You will use these keys to authenticate with Datadog.

Copy the environment template to a new file and edit it with your keys.

cp .env.template .env

Obtain your credentials from your Datadog account, then fill them in the .env file along with the site region.

DD_API_KEY=your_datadog_api_key_here
DD_APP_KEY=your_datadog_app_key_here
DD_SITE=datadoghq.com  # or another site like datadoghq.eu

Test the configuration to ensure the MCP server can authenticate with Datadog.

npm test

Configuration and usage notes

Use a local, stdio-based MCP server configuration so your MCP clients can launch and control the server directly from your machine.

The example configuration shown below demonstrates how to run the Datadog MCP Server as a local process with environment variables.

{
  "type": "stdio",
  "name": "datadog",
  "command": "node",
  "args": ["/absolute/path/to/datadog/index.js"],
  "env": {
    "DD_API_KEY": "your_api_key",
    "DD_APP_KEY": "your_app_key",
    "DD_SITE": "datadoghq.com"
  }
}

Troubleshooting

Common issues include authentication problems, incorrect site configuration, and network connectivity. Ensure your API and application keys are correct, the DD_SITE matches your Datadog instance, and the machine has outbound HTTPS access to Datadog APIs.

If you encounter a startup or runtime issue, run with debug logging enabled to surface detailed information that helps pinpoint the cause.

Development

During development, you can install dependencies, run tests, and start in development mode to verify behavior and iterate quickly.

npm install
npm test
npm run dev

Available tools

get_monitors

Retrieve Datadog monitors with filtering options such as status and tags.

get_metrics

Search for metrics in your Datadog account using a query and limit results.

get_dashboards

List Datadog dashboards and retrieve details with optional filters.

search_logs

Search logs with advanced filtering, supporting query, time range, and limit.

get_events

Retrieve events within a specified time range and optional filters like priority and tags.

get_incidents

List incidents from Datadog incident management with optional query and limit.