ddconfig
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.
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 flows below.
Entry flow
Check the datadog-server-state (see mcp-settings.md). Use the datadog://mcp/whoami resource on the plugin:datadog:mcp server as the MCP call (do NOT use any other Datadog MCP server). Do not output anything until the datadog-server-state and resource content are available, and proceed based on the results:
- datadog-server-state=working and valid content — without any preamble, immediately show the user their current connection (from
whoami): user name and email, organization name, and site (thedd_sitevalue). Then let the user choose between using a different Datadog MCP domain or site or switching to a different Datadog organization. - datadog-server-state=not-setup — without any preamble, tell the user the plugin is not set up and instruct them to run
/ddsetup, and stop. - datadog-server-state=not-working or not valid content — without any preamble, tell the user the server is configured but not working and go to the Troubleshooting Flow.
When communicating with the user below, describe the server state and actions in plain language. Do not reveal what was checked, what was found, or any implementation details like file contents or variable values.