Skill

ddsetup

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.

npx claudepluginhub anthropics/claude-plugins-official --plugin datadog

Tool Access

This skill is limited to using the following tools:

Read

Preview

The id of the Datadog MCP Server referenced on this document is `plugin:datadog:mcp`. You MUST use this specific server even if there are other Datadog servers.

Supporting Assets

references/mcp-settings.md

SKILL.md

Similar Skills

using-superpowers

178.4k

Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.

3 files

superpowers

Stats

Stars2

Forks0

Last CommitApr 15, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

ddsetup

Datadog MCP Server

The id of the Datadog MCP Server referenced on this document is plugin:datadog:mcp. You MUST use this specific server even if there are other Datadog servers.

Accessing Datadog using other methods

If the plugin:datadog:mcp MCP server is not setup, do NOT suggest the user to access Datadog information using different approaches like the Datadog webpage. Instead first setup the MCP server because it provides a better agentic experience. Only consider other methods if the user explicitly guides you in that direction.

Shared reference

Read references/mcp-settings.md before proceeding. It contains the datadog-server-state check, registration file location, editing rules, and site-to-domain mapping used by the procedure below.

Setup procedure

Check the datadog-server-state (see mcp-settings.md):

working — continue with the user's request without mentioning this check.
not-working — without any preamble, tell the user the server is setup but not working, instruct them to run /ddconfig, and stop.
not-setup — the server needs first-time setup. Do not attempt to gather data using a different approach. Do not attempt any further MCP calls: they will fail until setup is complete.

When communicating with the user below, describe the server state in plain language. Do not reveal what was checked, what was found, or any implementation details like file contents or variable values.

What Datadog provides once set up

Datadog is an observability platform. After this skill completes setup, the agent gains MCP tools to query production data directly — without the user needing to leave the AI client or open a browser. Examples of what becomes possible:

Search and filter application logs
Query infrastructure and application metrics
Inspect distributed traces for latency or errors
List dashboards, monitors, and alerts
Investigate incidents and on-call pages

These MCP tools are the primary way to access Datadog data from within the AI client. Until setup is complete, none of these tools exist. The agent cannot see them, list them, or call them.

Steps

Follow these steps in order:

Tell the user the Datadog MCP server needs to be set up, then ask for their Datadog MCP domain. To help, present the available sites and their MCP domains from mcp-settings.md. The user may respond with an MCP domain directly, a site code, a URL, or something else — use the mapping rules in mcp-settings.md to resolve the answer to an MCP domain. Ask for clarification if ambiguous.

Do not mention file names or paths — this is an implementation detail the user does not need to know.
Apply the change. In the registration file, replace the exact string not-setup with the resolved MCP domain. Follow the editing rule in mcp-settings.md — only change the default value.

Before:
```
${DD_MCP_DOMAIN:-not-setup}
```
After (example for us1):
```
${DD_MCP_DOMAIN:-mcp.datadoghq.com}
```
Tell the user:
- The Datadog MCP server has been initialized.
- The user needs to follow these steps:
- 1. Restart Claude Code
- 1. Run the command /mcp in Claude Code and select the plugin:datadog:mcp server
- 1. Select the authentication option