GeLi2001/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
- **Service-Specific Endpoints**: Support for different endpoints for logs and metrics
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
Application Key Scopes
For improved security, you can scope your Application Key to grant only the minimum permissions required by this MCP server. By default, Application Keys inherit all permissions from the user who created them, but scoped Application Keys allow you to follow the principle of least privilege.
Required Scopes
The following scopes are required for the corresponding features:
| Tool(s) | Required Scope | Description |
|---------|----------------|-------------|
| get-monitors, get-monitor | monitors_read | Read access to monitor configurations and states |
| get-dashboards, get-dashboard | dashboards_read | Read access to dashboard definitions |
| get-metrics, get-metric-metadata | metrics_read | Read access to metrics list and metadata |
| get-events | events_read | Read access to events from the event stream |
| search-logs, aggregate-logs | logs_read_data | Read access to log data for search and aggregation |
| get-incidents | incident_read | Read access to incident management data |
Creating a Scoped Application Key
1. Go to **Organization Settings** > **Application Keys**
2. Click **New Key**
3. Enter a name (e.g., "MCP Server - Read Only")
4. Under **Scopes**, select only the permissions you need:
- For full functionality: monitors_read, dashboards_read, metrics_read, events_read, logs_read_data, incident_read
- For logs only: logs_read_data
- For monitoring only: monitors_read, dashboards_read, metrics_read
5. Click **Create Key**
> **Note**: If you don't specify any scopes when creating an Application Key, it will have full access with all permissions of the creating user. For production use, we recommend always specifying explicit scopes.
Installation
Via npm (recommended)
From Source
1. Clone this repository
2. Install dependencies:
3. Build the project:
Configuration
You can configure the Datadog MCP server using either environment variables or command-line arguments.
Environment Variables
Create a .env file with your Datadog credentials:
**Note**: DD_LOGS_SITE and DD_METRICS_SITE are optional and will default to the value of DD_SITE if not specified.
Command-line Arguments
Basic usage with global site setting:
Advanced usage with service-specific endpoints: