Datadog监控
STDIO用于交互Datadog API的MCP服务器
用于交互Datadog API的MCP服务器
A Model Context Protocol (MCP) server for interacting with the Datadog API.
npm install -g datadog-mcp-server
npm install
npm run build
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.
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.
Different Datadog regions have different endpoints:
datadoghq.com
datadoghq.eu
ddog-gov.com
us5.datadoghq.com
ap1.datadoghq.com
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:
~/Library/Application Support/Claude/claude_desktop_config.json
%APPDATA%/Claude/claude_desktop_config.json
To use with the MCP Inspector tool:
npx @modelcontextprotocol/inspector datadog-mcp-server --apiKey=your_api_key --appKey=your_app_key
The server provides these MCP tools:
{ "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:
datadoghq.eu
for 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
Common issues:
MIT