Datadog
by
Datadog MCP Server is a Model Context Protocol (MCP) server that interacts with the official Datadog API. It enables users to access and manage various Datadog functionalities, including monitoring, dashboards, metrics, events, logs, and incidents.
Datadog Overview
Datadog MCP Server
Datadog MCP Server is a Model Context Protocol (MCP) server designed to interact with the official Datadog API. It enables users to access and manage various Datadog functionalities, including monitoring, dashboards, metrics, events, logs, and incidents.
How to Use Datadog MCP Server
Installation
Via npm (recommended):
npm install -g datadog-mcp-server
From Source:
- Clone the repository.
- Install dependencies:
npm install - Build the project:
npm run build
Configuration
Configure using environment variables (e.g., in a .env file) or command-line arguments. You'll need your Datadog API key and Application key.
Environment Variables:
DD_API_KEY=your_api_key_here
DD_APP_KEY=your_app_key_here
DD_SITE=datadoghq.com
DD_LOGS_SITE=datadoghq.com (optional)
DD_METRICS_SITE=datadoghq.com (optional)
Command-line Arguments:
datadog-mcp-server --apiKey=your_api_key --appKey=your_app_key --site=datadoghq.eu
For 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
Usage with Claude Desktop
Add the following 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>"
]
}
}
}
Usage with MCP Inspector
npx @modelcontextprotocol/inspector datadog-mcp-server --apiKey=your_api_key --appKey=your_app_key
Key Features of Datadog MCP Server
- 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, and perform aggregations.
- Incidents: Access incident management data.
- API Integration: Direct integration with Datadog's v1 and v2 APIs.
- Comprehensive Error Handling: Provides clear error messages for API and authentication issues.
- Service-Specific Endpoints: Supports different endpoints for logs and metrics.
Use Cases of Datadog MCP Server
- Automated Monitoring and Alerting: Programmatically fetch monitor data and integrate with custom alerting systems.
- Dashboard Management: Automate the retrieval and analysis of dashboard configurations.
- Performance Analysis: Query metrics and events to analyze application performance and identify trends.
- Log Analysis and Troubleshooting: Search, filter, and aggregate logs for debugging and incident investigation.
- Incident Management Integration: Access incident data for integration with internal incident response workflows.
- Custom Reporting: Generate custom reports by programmatically accessing various Datadog data points.
FAQ about Datadog MCP Server
Q: What are the prerequisites for using Datadog MCP Server? A: You need Node.js (version 16 or higher) and a Datadog account with API and Application keys.
Q: How do I configure regional endpoints?
A: You can specify the site argument (e.g., datadoghq.eu for EU) or service-specific endpoints like logsSite and metricsSite.
Q: What should I do if I encounter a 403 Forbidden error? A: Verify your API and Application keys, ensure they have necessary permissions, confirm account access to resources, and check if you're using the correct regional endpoint.
Q: How can I debug issues with Datadog MCP Server? A: You can check Claude Desktop's MCP logs. Common issues include incorrect API/App key formats, site configuration errors, and endpoint mismatches.
Datadog'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 Reviews
Login Required
Please log in to share your review and rating for this MCP.
Actions
Datadog's Information
- Author
- GeLi2001
- Category
- Monitoring & Observability
- Language
- TypeScript
- License
- MIT License
- Version
- v1.0.8
- Stars
- 49
- Updated
- 3 months ago
Related MCP Servers
Discover more MCP servers with similar functionality and use cases
Netdata
by netdata
Real-time, per‑second infrastructure monitoring platform that provides instant insights, auto‑discovery, edge‑based machine‑learning anomaly detection, and lightweight visualizations without requiring complex configuration.
Arize Phoenix
Officialby Arize-ai
Arize Phoenix is an open-source AI and LLM observability tool for inspecting traces, managing prompts, curating datasets, and running experiments.
Tianji
by msgbyte
Provides website analytics, uptime monitoring, and server status in a single self‑hosted application.
MCP Server For Grafana
by grafana
Provides programmatic access to Grafana dashboards, datasources, alerts, incidents, and related operational data through a Model Context Protocol server, enabling AI assistants and automation tools to query and manipulate Grafana resources.
Dynatrace MCP Server
by dynatrace-oss
Provides a local server that enables real‑time interaction with the Dynatrace observability platform, exposing tools for problem retrieval, DQL execution, Slack notifications, workflow automation, and AI‑assisted troubleshooting.
Logfire MCP
by pydantic
Provides tools to retrieve, query, and visualize OpenTelemetry traces and metrics from Pydantic Logfire via a Model Context Protocol server.
VictoriaMetrics MCP Server
by VictoriaMetrics-Community
Access VictoriaMetrics instances through Model Context Protocol, enabling AI assistants and tools to query metrics, explore labels, debug configurations, and retrieve documentation without leaving the conversational interface.
Axiom
Officialby axiomhq
Axiom MCP Server implements the Model Context Protocol (MCP) for Axiom, enabling AI agents to query logs, traces, and other event data using the Axiom Processing Language (APL). It allows AI agents to perform monitoring, observability, and natural language analysis of data for debugging and incident response.
Last9 MCP Server
by last9
Provides AI agents with real‑time production context—logs, metrics, and traces—through a Model Context Protocol server that can be queried from development environments.