Datadog MCP server for AI agents

The Datadog MCP Server provides a powerful interface to access Datadog's monitoring capabilities through the Model Context Protocol. This server enables you to manage incidents, monitors, logs, dashboards, metrics, and other Datadog features directly through MCP clients like Claude.

Setup Requirements

Datadog Credentials

Before using the MCP server, you'll need to configure your Datadog API credentials:

DATADOG_API_KEY: Your Datadog API key
DATADOG_APP_KEY: Your Datadog Application key
DATADOG_SITE (optional): The Datadog site (e.g. datadoghq.eu)
DATADOG_SUBDOMAIN (optional): The Datadog subdomain

Export these credentials in your environment:

export DATADOG_API_KEY="your_api_key"
export DATADOG_APP_KEY="your_app_key"
export DATADOG_SITE="your_datadog_site"  # Optional
export DATADOG_SUBDOMAIN="your_datadog_subdomain"  # Optional

Installation Options

Installing via Smithery

The easiest way to install the Datadog MCP Server for Claude Desktop is through Smithery:

npx -y @smithery/cli install @winor30/mcp-server-datadog --client claude

Manual Installation

If you prefer to install manually:

pnpm install
pnpm build
pnpm watch   # for development with auto-rebuild

Configuration with Claude Desktop

To use this MCP server with Claude Desktop, add it to your claude_desktop_config.json file:

Location:

MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%/Claude/claude_desktop_config.json

Configuration using local build:

{
  "mcpServers": {
    "datadog": {
      "command": "/path/to/mcp-server-datadog/build/index.js",
      "env": {
        "DATADOG_API_KEY": "<YOUR_API_KEY>",
        "DATADOG_APP_KEY": "<YOUR_APP_KEY>",
        "DATADOG_SITE": "<YOUR_SITE>",
        "DATADOG_SUBDOMAIN": "<YOUR_SUBDOMAIN>"
      }
    }
  }
}

Configuration using npx:

{
  "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>"
      }
    }
  }
}

Available Tools

Incident Management

list_incidents: Retrieve a list of incidents from Datadog
get_incident: Retrieve detailed information about a specific incident

Monitoring

get_monitors: Fetch the status of Datadog monitors
list_downtimes: List scheduled downtimes
schedule_downtime: Schedule a downtime in Datadog
cancel_downtime: Cancel a scheduled downtime

Logs & Metrics

get_logs: Search and retrieve logs from Datadog
query_metrics: Retrieve metrics data
list_traces: Retrieve a list of APM traces

Dashboards

list_dashboards: Get a list of dashboards
get_dashboard: Retrieve a specific dashboard

Host Management

list_hosts: Get list of hosts from Datadog
get_active_hosts_count: Get the total number of active hosts
mute_host: Mute a host in Datadog
unmute_host: Unmute a host in Datadog

RUM (Real User Monitoring)

get_rum_applications: Get all RUM applications
get_rum_events: Search and retrieve RUM events
get_rum_grouped_event_count: Search, group and count RUM events
get_rum_page_performance: Get page performance metrics
get_rum_page_waterfall: Retrieve RUM page waterfall data

Debugging

Since MCP servers communicate over standard input/output, debugging can be challenging. You can use the MCP Inspector tool:

npm run inspector

This will provide a URL you can open in your browser to see logs and send requests manually.

How to install this MCP server

For Claude Code

To add this MCP server to Claude Code, run this command in your terminal:

claude mcp add-json "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>"}}'

See the official Claude Code MCP documentation for more details.

For Cursor

There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.

If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.

Adding an MCP server to Cursor globally

To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".

When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:

{
    "mcpServers": {
        "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>"
            }
        }
    }
}

Adding an MCP server to a project

To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.

How to use the MCP server

Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.

The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.

You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.

For Claude Desktop

To add this MCP server to Claude Desktop:

1. Find your configuration file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Linux: ~/.config/Claude/claude_desktop_config.json

2. Add this to your configuration file:

{
    "mcpServers": {
        "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>"
            }
        }
    }
}

3. Restart Claude Desktop for the changes to take effect