Get the FREE Ultimate OpenClaw Setup Guide →

datadog

MCP server providing AI assistants with full Datadog observability access.

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio tantiope-datadog-mcp-server npx -y datadog-mcp \
  --env DD_SITE="datadoghq.com" \
  --env DD_API_KEY="your-api-key" \
  --env DD_APP_KEY="your-app-key"

How to use

This MCP server integrates with Datadog to provide AI-assisted access to Datadog observability data. It enables tools for logs search, APM trace filtering, metrics querying, dashboards, and event management, organized through the MCP protocol so you can interact via the standard MCP client/server interface. The server exposes a suite of Datadog APIs through a consistent MCP toolset, including monitors, dashboards, logs, metrics, traces, events, incidents, SLOs, synthetics, and downtimes, with role-based access and scope requirements described in the Tools table. You can run the server via npx or in Docker, and you can tailor behavior with environment variables and optional flags to control transport, port, host, and tool availability.

How to install

Prerequisites:\n- Node.js (recommended) and npm installed on your machine.\n- Access to a Datadog account with API and APP keys.\n\nInstallation steps:\n1) Install or run via npx (no local install required):\n npx -y datadog-mcp\n\n2) If you prefer a local install, install the package globally and run the server:\n npm i -g datadog-mcp\n datadog-mcp\n\n3) Optional: Run with Docker (example):\n docker run -i --rm -e DD_API_KEY=your-api-key -e DD_APP_KEY=your-app-key -e DD_SITE=datadoghq.com ghcr.io/tantiope/datadog-mcp\n\nPrerequisites for docker or http transport setup are described in the README and expose the /mcp endpoint for the MCP protocol when enabled.

Additional notes

Environment variables:\n- DD_API_KEY: Datadog API key. Required for API access.\n- DD_APP_KEY: Datadog APP key. Required for API access.\n- DD_SITE: Datadog site (e.g., datadoghq.com). Optional; defaults apply if omitted.\n\nConfiguration tips:\n- You can override defaults with MCP flags such as --site, --transport, --port, and --host.\n- Use --disable-tools to disable specific tools (e.g., synthetics, rum, security).\n- When using Kubernetes, consider using environment variables to avoid argument parsing issues.\n- If you operate behind proxies or require network restrictions, ensure the host and port are accessible to your MCP clients.

Related MCP Servers

Sponsor this space

Reach thousands of developers