The `datadog-mcp-server` package provides a Model Context Protocol (MCP) server designed to interface with the Datadog API. Currently at version 1.0.9, this server acts as a comprehensive gateway for accessing various Datadog resources including monitors, dashboards, metrics, events, logs, and incidents. It offers direct integration with both Datadog's v1 and v2 APIs, featuring robust error handling and support for service-specific endpoints across different Datadog regional sites. The server is primarily distributed as a command-line interface (CLI) tool, configured via environment variables or CLI arguments, and is intended to run as a background service or be invoked by other MCP-compatible tools like Claude Desktop or MCP Inspector. Its main differentiator is providing a standardized MCP interface over the extensive Datadog API.
npm install datadog-mcp-serverVerified import paths — ran on the pinned version, not inferred.
Demonstrates how to programmatically launch the `datadog-mcp-server` CLI using `npx` with required Datadog API credentials, showing proper setup and process management.
Ensure your Node.js environment is updated to version 16 or newer. Use `nvm` or `volta` to manage Node.js versions if necessary.
Provide valid `DD_API_KEY` and `DD_APP_KEY` from your Datadog organization settings. For production, use environment variables; for testing, command-line arguments are acceptable.
Verify your Datadog account's region and set the `DD_SITE` environment variable or `--site` argument accordingly (e.g., `datadoghq.eu`, `us5.datadoghq.com`). Also consider `DD_LOGS_SITE` and `DD_METRICS_SITE` for specific endpoints if needed.
For production environments, deploy the server using process managers like PM2, systemd, or containerize it with Docker to ensure reliable operation, automatic restarts, and resource limits.
Upgrade your Node.js installation to version 16 or newer. Check your current version with `node -v`.
Set `DD_API_KEY` and `DD_APP_KEY` environment variables, or pass `--apiKey` and `--appKey` command-line arguments with correct values.
Verify the `--site` argument or `DD_SITE` environment variable is set to the correct regional endpoint (e.g., `datadoghq.com`, `datadoghq.eu`). Check network connectivity to Datadog's API.
Include both `--apiKey=<YOUR_API_KEY>` and `--appKey=<YOUR_APP_KEY>` in your command-line arguments, or ensure `DD_API_KEY` and `DD_APP_KEY` are set in your environment.
No dependency data recorded yet.