Datadog MCP Server
by
Enables interaction with the Datadog API through a Model Context Protocol server, providing access to monitors, dashboards, metrics, logs, events, and incident data.
Datadog MCP Server Overview
What is Datadog MCP Server about?
Enables interaction with the Datadog API via MCP tools, allowing retrieval and management of monitoring data, dashboards, metrics, logs, events, and incidents.
How to use Datadog MCP Server?
- Installation
- Recommended:
npm install -g datadog-mcp-server - Or run directly with npx (no global install needed).
- Recommended:
- Configuration
- Set credentials via environment variables in a
.envfile:DD_API_KEY=your_api_key DD_APP_KEY=your_app_key DD_SITE=datadoghq.com DD_LOGS_SITE=datadoghq.com # optional DD_METRICS_SITE=datadoghq.com # optional - Or pass them as command‑line arguments:
npx datadog-mcp-server --apiKey <YOUR_API_KEY> --appKey <YOUR_APP_KEY> --site datadoghq.eu - For service‑specific endpoints add
--logsSiteand--metricsSite.
- Set credentials via environment variables in a
- Running with Claude Desktop
Add the following to
claude_desktop_config.json:{ "mcpServers": { "datadog": { "command": "npx", "args": [ "datadog-mcp-server", "--apiKey", "<YOUR_API_KEY>", "--appKey", "<YOUR_APP_KEY>", "--site", "<YOUR_DD_SITE>" ] } } } - Using with MCP Inspector
npx @modelcontextprotocol/inspector datadog-mcp-server --apiKey=your_api_key --appKey=your_app_key - Calling Tools
Use the provided MCP tools (e.g.,
get-monitors,search-logs) via the standard MCP call format.
Key Features
- Access to Datadog monitors, dashboards, metrics, events, logs, and incidents.
- Direct integration with Datadog v1 and v2 APIs.
- Support for regional endpoints (US, EU, GovCloud, AP1, etc.).
- Environment variable and CLI argument configuration.
- Comprehensive error handling with clear messages.
- Service‑specific endpoint configuration for logs and metrics.
- Ready-to-use MCP tools for common Datadog operations.
Use Cases
- Retrieve and display real‑time monitor status in custom dashboards.
- Automate incident investigation by pulling recent events and logs.
- Integrate Datadog metrics into AI agents or other automated workflows.
- Enable Claude Desktop or other MCP‑compatible clients to query Datadog data without custom code.
- Perform log aggregation and analytics directly via MCP calls.
FAQ
Q: Which Node.js version is required? A: Node.js 16 or higher.
Q: How do I specify a non‑default Datadog region?
A: Use the --site flag (e.g., datadoghq.eu) or set DD_SITE in the .env file. Optional --logsSite and --metricsSite can override per‑service domains.
Q: What should I do if I receive a 403 Forbidden error? A: Verify that the API and Application keys are correct, have the needed permissions, and that you are targeting the correct regional endpoint.
Q: Can I run the server without installing it globally?
A: Yes, invoke it with npx datadog-mcp-server and provide the required arguments.
Q: Where can I find MCP logs for debugging?
A: On macOS: ~/Library/Logs/Claude/mcp*.log; on Windows: %APPDATA%\Claude\Logs\mcp*.log.
Datadog MCP Server's README
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
- 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
Installation
Via npm (recommended)
npm install -g datadog-mcp-server
From Source
- Clone this repository
- Install dependencies:
npm install - Build the project:
npm run build
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:
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.
Command-line Arguments
Basic usage with global site setting:
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 need https:// - it will be added automatically.
Regional Endpoints
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
Usage with Claude Desktop
Add this to your claude_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
Usage with MCP Inspector
To use with the MCP Inspector tool:
npx @modelcontextprotocol/inspector datadog-mcp-server --apiKey=your_api_key --appKey=your_app_key
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
Examples
Example: Get Monitors
{
"method": "tools/call",
"params": {
"name": "get-monitors",
"arguments": {
"groupStates": ["alert", "warn"],
"limit": 5
}
}
}
Example: Get a Dashboard
{
"method": "tools/call",
"params": {
"name": "get-dashboard",
"arguments": {
"dashboardId": "abc-def-123"
}
}
}
Example: Search Logs
{
"method": "tools/call",
"params": {
"name": "search-logs",
"arguments": {
"filter": {
"query": "service:web-app status:error",
"from": "now-15m",
"to": "now"
},
"sort": "-timestamp",
"limit": 20
}
}
}
Example: Aggregate Logs
{
"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"
}
}
]
}
}
}
Example: Get Incidents
{
"method": "tools/call",
"params": {
"name": "get-incidents",
"arguments": {
"includeArchived": false,
"query": "state:active",
"pageSize": 10
}
}
}
Troubleshooting
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)
Debugging
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
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
- Endpoint mismatches: Verify that service-specific endpoints are correctly set if you're using separate domains for logs and metrics
License
MIT
Datadog MCP Server Reviews
Login Required
Please log in to share your review and rating for this MCP.
Actions
Datadog MCP Server's Information
- Author
- GeLi2001
- Category
- Monitoring & Observability
- Language
- TypeScript
- License
- MIT License
- Version
- v1.0.8
- Stars
- 55
- Updated
- 21 days ago
Configuration
{
"mcpServers": {
"datadog": {
"command": "npx",
"args": [
"datadog-mcp-server",
"--apiKey",
"<YOUR_API_KEY>",
"--appKey",
"<YOUR_APP_KEY>",
"--site",
"<YOUR_DD_SITE>"
]
}
}
}Configure Clients
Similar MCP Servers like Datadog MCP Server
Explore related MCPs that share similar capabilities and solve comparable challenges
Phoenix
Officialby Arize-ai
Open-source AI observability platform enabling tracing, evaluation, dataset versioning, experiment tracking, prompt management, and interactive playground for LLM applications.
Grafana MCP Server
by grafana
Provides programmatic access to a Grafana instance and its surrounding ecosystem through the Model Context Protocol, enabling AI assistants and other clients to query and manipulate dashboards, datasources, alerts, incidents, on‑call schedules, and more.
Dynatrace MCP Server
by dynatrace-oss
Provides a local server that enables real‑time interaction with the Dynatrace observability platform, exposing tools for querying data, retrieving problems, sending Slack notifications, and integrating AI assistance.
VictoriaMetrics MCP Server
by VictoriaMetrics-Community
Provides a Model Context Protocol server exposing read‑only VictoriaMetrics APIs, enabling seamless monitoring, observability, and automation through AI‑driven assistants.
JMeter MCP Server
by QAInsights
Execute JMeter test plans through Model Context Protocol clients, capture console output, generate HTML dashboards, and automatically analyze JTL results to surface performance metrics, bottlenecks, and actionable recommendations.
Loki MCP Server
by grafana
Provides a Model Context Protocol (MCP) server that enables AI agents to query Grafana Loki log data via stdin/stdout or Server‑Sent Events, supporting both local binary execution and containerized deployment.
Kibana MCP Server
by TocharianOU
Provides a Model Context Protocol (MCP) server that enables MCP‑compatible clients to access, search, and manage Kibana APIs using natural language or programmatic requests.
Raygun Mcp Server
by MindscapeHQ
Provides comprehensive access to Raygun's API V3 endpoints for crash reporting and real user monitoring via the Model Context Protocol.
Tempo MCP Server
by grafana
Provides Model Context Protocol endpoints that enable AI assistants to query and analyze distributed tracing data stored in Grafana Tempo, supporting both stdin/stdout communication and an HTTP SSE interface.