Datadog
About
Integrates with Datadog monitoring platform to provide access to metrics, logs, dashboards, monitors, and incidents for DevOps and SRE workflows
Details
- Author
- geli2001
- Repository
- GeLi2001/datadog-mcp-server
- GitHub stars
- 41
- Downloads
- 1,819
- License
- MIT License
- Categories
- Cloud Service, Other, Infrastructure, Productivity, Developer Tools, Design, AI, Search
- Tags
- #datadog, #integration, #web, #analytics
Jump to
- 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
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
DatadogCommand (node, npx, python, etc.)npxArguments-
Argument 1
datadog-mcp-server -
Argument 2
--apiKey -
Argument 3
<YOUR_API_KEY> -
Argument 4
--appKey -
Argument 5
<YOUR_APP_KEY> -
Argument 6
--site -
Argument 7
<YOUR_DD_SITE>(e.g us5.datadoghq.com)
Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
-
Argument 1
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
You can configure the Datadog MCP server using either environment variables or command-line arguments.
Create a .env file with your Datadog credentials:
DD_API_KEY=your_api_key_here
DD_APP_KEY=your_app_key_here
DD_SITE=datadoghq.com
DD_LOGS_SITE=datadoghq.com
DD_METRICS_SITE=datadoghq.com
Note: DD_LOGS_SITE and DD_METRICS_SITE are optional and will default to the value of DD_SITE if not specified.
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.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"datadog": {
"env": {},
"args": [
"datadog-mcp-server",
"--apiKey",
"<YOUR_API_KEY>",
"--appKey",
"<YOUR_APP_KEY>",
"--site",
"<YOUR_DD_SITE>(e.g us5.datadoghq.com)"
],
"command": "npx"
}
}
}
Linux
{
"env": [],
"args": [
"datadog-mcp-server",
"--apiKey",
"<YOUR_API_KEY>",
"--appKey",
"<YOUR_APP_KEY>",
"--site",
"<YOUR_DD_SITE>(e.g us5.datadoghq.com)"
],
"command": "npx"
}
Macos
{
"env": [],
"args": [
"datadog-mcp-server",
"--apiKey",
"<YOUR_API_KEY>",
"--appKey",
"<YOUR_APP_KEY>",
"--site",
"<YOUR_DD_SITE>(e.g us5.datadoghq.com)"
],
"command": "npx"
}
Windows
{
"env": [],
"args": [
"/c",
"npx",
"datadog-mcp-server",
"--apiKey",
"<YOUR_API_KEY>",
"--appKey",
"<YOUR_APP_KEY>",
"--site",
"<YOUR_DD_SITE>(e.g us5.datadoghq.com)"
],
"command": "cmd"
}
A Model Context Protocol (MCP) server for interacting with the Datadog API.
- 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
- Node.js (version 16 or higher)
- Datadog account with:
- API key - Found in Organization Settings > API Keys
- Application key - Found in Organization Settings > Application Keys
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, butscoped Application Keysallow you to follow the principle of least privilege.
The following scopes are required for the corresponding features:
- Go toOrganization Settings>Application Keys
- ClickNew Key
- Enter a name (e.g., "MCP Server - Read Only")
- UnderScopes, 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
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.
- Clone this repository
- Install dependencies:
npm install
You can configure the Datadog MCP server using either environment variables or command-line arguments.
Create a.envfile with your Datadog credentials:
DD_API_KEY=your_api_key_here DD_APP_KEY=your_app_key_here DD_SITE=datadoghq.com DD_LOGS_SITE=datadoghq.com DD_METRICS_SITE=datadoghq.com
Note:DD_LOGS_SITEandDD_METRICS_SITEare optional and will default to the value ofDD_SITEif not specified.
datadog-mcp-server --apiKey=your_api_key --appKey=your_app_key --site=datadoghq.eu
Advanced usage with service-specific endpoints:
datadog-mcp-server --apiKey=your_api_key --appKey=your_app_key --site=datadoghq.com --logsSite=logs.datadoghq.com --metricsSite=metrics.datadoghq.com
Note: Site arguments don't needhttps://- it will be added automatically.
Different Datadog regions have different endpoints:
- US (Default):datadoghq.com
- EU:datadoghq.eu
- US3 (GovCloud):ddog-gov.com
- US5:us5.datadoghq.com
- AP1:ap1.datadoghq.com
Add this to yourclaude_desktop_config.json:
{ "mcpServers": { "datadog": { "command": "npx", "args": [ "datadog-mcp-server", "--apiKey", "<YOUR_API_KEY>", "--appKey", "<YOUR_APP_KEY>", "--site", "<YOUR_DD_SITE>(e.g us5.datadoghq.com)" ] } } }
For more advanced configurations with separate endpoints for logs and metrics:
{ "mcpServers": { "datadog": { "command": "npx", "args": [ "datadog-mcp-server", "--apiKey", "<YOUR_API_KEY>", "--appKey", "<YOUR_APP_KEY>", "--site", "<YOUR_DD_SITE>", "--logsSite", "<YOUR_LOGS_SITE>", "--metricsSite", "<YOUR_METRICS_SITE>" ] } } }
Locations for the Claude Desktop config file:
- MacOS:~/Library/Application Support/Claude/claude_desktop_config.json
- Windows:%APPDATA%/Claude/claude_desktop_config.json
npx @modelcontextprotocol/inspector datadog-mcp-server --apiKey=your_api_key --appKey=your_app_key
- 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
{ "method": "tools/call", "params": { "name": "get-monitors", "arguments": { "groupStates": ["alert", "warn"], "limit": 5 } } }
{ "method": "tools/call", "params": { "name": "get-dashboard", "arguments": { "dashboardId": "abc-def-123" } } }
{ "method": "tools/call", "params": { "name": "search-logs", "arguments": { "filter": { "query": "service:web-app status:error", "from": "now-15m", "to": "now" }, "sort": "-timestamp", "limit": 20 } } }
{ "method": "tools/call", "params": { "name": "aggregate-logs", "arguments": { "filter": { "query": "service:web-app", "from": "now-1h", "to": "now" }, "compute": [ { "aggregation": "count" } ], "groupBy": [ { "facet": "status", "limit": 10, "sort": { "aggregation": "count", "order": "desc" } } ] } } }
{ "method": "tools/call", "params": { "name": "get-incidents", "arguments": { "includeArchived": false, "query": "state:active", "pageSize": 10 } } }
If you encounter a 403 Forbidden error, verify that:
- Your API key and Application key are correct
- The keys have the necessary permissions to access the requested resources
- Your account has access to the requested data
- You're using the correct endpoint for your region (e.g.,datadoghq.eufor EU customers)
If you encounter issues, check Claude Desktop's MCP logs:
# On macOS tail -n 20 -f ~/Library/Logs/Claude/mcp.log # On Windows Get-Content -Path "$env:APPDATA\Claude\Logs\mcp.log" -Tail 20 -Wait
- 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
- Endpoint mismatches: Verify that service-specific endpoints are correctly set if you're using separate domains for logs and metrics
Provides comprehensive Datadog monitoring capabilities through any MCP client.
The IBM Instana MCP server enables seamless interaction with the IBM Instana observability platform, allowing you to access real-time observability data directly within your development workflow.
Query and interact with kubernetes environments monitored by Metoro
Fetch logs, metrics, traces, and events from the Chronosphere observability platform.
An MCP server for the Dynatrace observability platform.
Civilian situational awareness for AI deployments — real-time risk dashboards, multi-source threat correlation, anomaly detection, and automated alerting for critical infrastructure and enterprise AI systems.
MCP server for AI agent deployment health — gateway status, CPU/memory/swap, recent errors, skill registry integrity, upgrade outcomes, cron + disk usage. HEALTHY/DEGRADED/CRITICAL classification per component.
An MCP server for dynamically configuring OpenTelemetry Collectors, including receivers, processors, and exporters.
ThousandEyes Network Performance Monitoring MCP Server
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.




