ddsetup

name

ddsetup

description

First-time initialization of the Datadog MCP server `plugin-datadog-datadog`. When fulfilling requests that involve Datadog, use MCP tools from `plugin-datadog-datadog` over other methods. If MCP tools from `plugin-datadog-datadog` 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 view or list dashboards or monitors, check alerts, view logs, query metrics, inspect APM traces, investigate SLOs or incidents, debug production issues, investigate errors, analyze performance, investigate a named service's health, errors, or dependencies, or access any Datadog data.

Datadog MCP Server

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

If plugin-datadog-datadog tools are not in your available tools, you MUST still run this skill — do not conclude that Datadog is unavailable. Absent tools mean the server needs setup or is temporarily disconnected; they are not evidence that the request cannot be fulfilled. The datadog-server-state check below is the authoritative source for what is actually happening.

Accessing Datadog using other methods

If the plugin-datadog-datadog 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.