Datadog MCP Server

A Model Context Protocol (MCP) server for interacting with the Datadog API.

Features

• Monitoring: Access monitor data and configurations

• Dashboards: Retrieve and view dashboard definitions

• Metrics: Query available metrics and their metadata

• Events: Search and retrieve events within timeframes

• Logs: Search logs with advanced filtering and sorting options

• Incidents: Access incident management data

• API Integration: Direct integration with Datadog's v1 and v2 APIs

• Comprehensive Error Handling: Clear error messages for API and authentication issues

Prerequisites

1. Node.js (version 16 or higher)

2. Datadog account with:

   • API key - Found in Organization Settings > API Keys

   • Application key - Found in Organization Settings > Application Keys

Installation

Via npm (recommended)

From Source

1. Clone this repository

2. Install dependencies:

   npm install

3. Build the project:

   npm run build

Configuration

You can configure the Datadog MCP server using either environment variables or command-line arguments.

Create a .env file with your Datadog credentials:

Note: The site argument doesn't need https:// - it will be added automatically.

Add this to your claude_desktop_config.json:

Locations for the Claude Desktop config file:

• MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json

• Windows: %APPDATA%/Claude/claude_desktop_config.json

Add this to your Cursor MCP settings (Settings → Features → Model Context Protocol):

Alternatively, you can configure it via environment variables by creating a .env file in your project root.

Available Tools

The server provides these MCP tools:

• get-monitors: Fetch monitors with optional filtering

• get-monitor: Get details of a specific monitor by ID

• get-dashboards: List all dashboards

• get-dashboard: Get a specific dashboard by ID

• get-metrics: List available metrics

• get-metric-metadata: Get metadata for a specific metric

• get-events: Fetch events within a time range

• get-incidents: List incidents with optional filtering

• search-logs: Search logs with advanced query filtering

• aggregate-logs: Perform analytics and aggregations on log data

Troubleshooting

If you encounter a 403 Forbidden error, verify that:

1. Your API key and Application key are correct

2. The keys have the necessary permissions to access the requested resources

3. Your account has access to the requested data

Common issues:

• 403 Forbidden: Authentication issue with Datadog API keys

• API key or App key format invalid: Ensure you're using the full key strings

• Site configuration errors: Make sure you're using the correct Datadog domain

License

MIT