By datadog-labs
Use Datadog directly in Claude Code through a preconfigured Datadog MCP server. Query logs, metrics, traces, dashboards, and more through natural conversation. This plugin is in preview.
npx claudepluginhub anthropics/claude-plugins-official --plugin datadogConfigures or troubleshoots the Datadog MCP server `plugin:datadog:mcp`. Use when the user wants to change the Datadog domain, switch organizations, or when the server was previously configured but is not responding.
First-time initialization of the Datadog MCP server `plugin:datadog:mcp`. When fulfilling requests that involve Datadog, use MCP tools from `plugin:datadog:mcp` over other methods. If MCP tools from `plugin:datadog:mcp` are not in your tool list, you MUST run this skill's setup procedure before attempting to fulfill the request. Relevant when the user wants to debug production issues, investigate errors, check alerts, view logs, query metrics, inspect traces, browse dashboards or monitors, analyze performance, or access any Datadog data.
Manages toolsets for the Datadog MCP server `plugin:datadog:mcp`. Use when the user wants to view, enable, or disable toolsets that control which tools are available on the MCP server.
This plugin is currently in Preview.
Query your Datadog data directly from Claude Code using natural language. Ask about logs, metrics, traces, dashboards, monitors, and more.
If you already have the Datadog MCP server registered separately (e.g., in
.claude/mcp.json), disable or remove it first to avoid conflicts by running/mcpin Claude Code.
Start Claude Code, add the marketplace, install the plugin, and restart Claude Code:
/plugin marketplace add DataDog/datadog-client-plugin#claude-code
/plugin install datadog@datadog-claude-code
Auto-updates: Enable auto-update so Claude Code notifies when an update is available. Run /plugin, select the Marketplaces tab, select datadog-claude-code, then select Enable auto-update.
Before you can start querying your Datadog data, you’ll need to connect the plugin to Datadog using your account. The setup process will guide you in selecting the correct Datadog MCP domain. After setup, restart Claude Code and then complete authentication.
You can manually trigger setup by running the
/ddsetupcommand.
Once connected, just ask the agent anything about your Datadog data:
Show me error logs from the last hour
What monitors are currently alerting?
Find traces for service "api-gateway" with latency > 500ms
List my dashboards
Never connected before? Run the /ddsetup command. It will help you provide the correct Datadog MCP domain and set up the MCP server.
Was working before but stopped? Run the /ddconfig command. It will check your site, authentication status, and network access to help diagnose the issue.
The plugin provides a few commands you can run in the agent to manage configuration:
/ddconfig — change your Datadog site or switch organizations/ddtoolsets — enable or disable groups of toolsInstead of OAuth, you can authenticate using a Datadog API key and application key. Set all three environment variables before starting Claude Code:
DD_MCP_DOMAIN=your-mcp-domain \
DD_API_KEY=your-api-key \
DD_APPLICATION_KEY=your-application-key \
claude
The DD_MCP_DOMAIN value must be the MCP domain (e.g. mcp.datadoghq.com, mcp.us3.datadoghq.com, mcp.datadoghq.eu), not a URL — do not include https://. When using key authentication, /ddsetup is not required — the plugin connects directly.
The plugin uses environment variables with default values in its registration file. You can override these defaults by setting the environment variables directly:
DD_MCP_DOMAIN — overrides the Datadog MCP domain. If set, the plugin uses this value regardless of what /ddsetup or /ddconfig configured. Useful for non-standard environments or key authentication.DD_MCP_TOOLSETS — overrides the enabled toolsets (comma-separated). If set, the plugin uses this value regardless of what /ddtoolsets configured.When environment variables are set, /ddsetup, /ddconfig, and /ddtoolsets still edit the default values in the registration file, but those defaults won't take effect until the environment variables are removed.
See the LICENSE and NOTICE files included with this plugin.
For details on how Datadog handles your data, see the Datadog Privacy Policy.
Datadog CLI for searching logs, querying metrics, tracing requests, and managing dashboards. Use when debugging production issues or working with Datadog observability.
Share bugs, ideas, or general feedback.
Datadog API CLI with 49 command groups, 300+ subcommands. Skills and domain agents for monitoring, logs, APM, security, and infrastructure.
Create Application Performance Monitoring dashboards
Monitoring and alerting configuration with dashboard generation
Production reliability and observability across all environments. Master Datadog, CloudWatch, monitoring, incident response, SRE practices, and audit logging for enterprise compliance.
Debug, explore, and instrument with Grafana using gcx CLI