If you came here for the command, use this.
Quick command
claude mcp add --transport http datadog https://mcp.datadoghq.com/v1/mcp
The alias is datadog. That is the name you will see in claude mcp list and /mcp. You can pick another alias, but the rest of this post assumes datadog.
That URL is for Datadog's US1 site (app.datadoghq.com). If your organization is on another site, use its endpoint from the table below.
Older guides, including an earlier version of this post, use https://mcp.datadoghq.com/api/unstable/mcp-server/mcp. Datadog's docs now list the /v1/mcp endpoints, so switch to those.
After this, Claude Code can use the Datadog MCP tools your account is allowed to use: monitors, logs, metrics, dashboards, APM, and anything else your role permits.
Or install the Datadog plugin
Datadog now recommends its Claude Code plugin from the official Anthropic marketplace over the manual command. The plugin bundles the same MCP server with Datadog skills and updates itself:
/plugin install datadog@claude-plugins-official
Then run /ddsetup (or ask any Datadog question), pick your Datadog site, and finish the OAuth login. /ddtoolsets turns tool groups on and off.
Use one or the other. If you already added the server with claude mcp add, remove it before installing the plugin so you don't have two Datadog servers:
claude mcp remove datadog
Endpoint for your Datadog site
Each Datadog site has its own endpoint: mcp. in front of the site domain, /v1/mcp at the end.
| Site | Endpoint |
|---|---|
US1 (datadoghq.com) | https://mcp.datadoghq.com/v1/mcp |
US3 (us3.datadoghq.com) | https://mcp.us3.datadoghq.com/v1/mcp |
US5 (us5.datadoghq.com) | https://mcp.us5.datadoghq.com/v1/mcp |
EU1 (datadoghq.eu) | https://mcp.datadoghq.eu/v1/mcp |
AP1 (ap1.datadoghq.com) | https://mcp.ap1.datadoghq.com/v1/mcp |
AP2 (ap2.datadoghq.com) | https://mcp.ap2.datadoghq.com/v1/mcp |
UK1 (uk1.datadoghq.com) | https://mcp.uk1.datadoghq.com/v1/mcp |
The US1-FED and US2-FED government sites aren't supported.
Why --transport http?
Datadog runs MCP as a remote server. Claude Code connects to it over HTTP instead of starting a local MCP process through stdio, so the command needs --transport http.
Verify the setup
After you add it, make sure Claude Code registered the server:
claude mcp list
Inside Claude Code, you can also run:
/mcp
The datadog server should show up there. If it does not, restart Claude Code and check again.
Then ask a small Datadog question:
Are there any triggered monitors in Datadog?
If Claude returns your Datadog data, the setup worked. If it connects but gives a blank or unhelpful answer, check permissions first. The command is probably not the problem.
Authentication and permissions
Datadog MCP uses OAuth. The first time Claude Code needs Datadog, it sends you through a browser login.
Claude Code can only read data that your Datadog account can read. Three things have to line up:
- An org admin has turned on MCP Access in Organization Settings. When it's off, nobody in the org can use the MCP server, whatever their role says. Write tools also need MCP Write Access.
- Your role has
mcp_read(andmcp_writefor tools that change things). Datadog's built-in Standard role has both. - Your role has the normal Datadog permission for the resource. Reading monitors needs
mcp_readand Monitors Read. The same pattern applies to logs, metrics, dashboards, and APM.
Optional: limit Datadog tools
Add toolsets to the URL to choose which Datadog tool groups Claude Code sees. Without it you get the core set.
For example, this enables only APM and LLM Observability tools:
claude mcp add --transport http datadog "https://mcp.datadoghq.com/v1/mcp?toolsets=apm,llmobs"
toolsets=all turns on every generally available group.
I would start without toolsets unless you already know you need it. Once you see which tools you actually use, add a filter to cut down the list.
Connect Datadog to the Claude app (claude.ai and Desktop)
The Claude app doesn't use claude mcp add. Datadog publishes an official connector in Claude's Connectors Directory:
- In Claude, click the + at the bottom of the prompt box, then Add connector.
- Find Datadog and enable it.
- Pick the region where your Datadog account is hosted, then click Connect.
- Finish the OAuth login.
The same permissions apply: MCP Access on for the org, mcp_read on your role, and read access to the resources you ask about.
If the directory connector isn't available on your plan or workspace, add Datadog as a custom connector and paste your site's endpoint from the table above. Remove the custom connector if you later switch to the directory one, so the two don't conflict.
Troubleshooting
If datadog appears in claude mcp list but Claude Code still cannot use it, restart Claude Code.
If OAuth does not start, open /mcp in Claude Code and check the Datadog server status.
If Claude connects but cannot read Datadog data, check MCP Access in your org settings, then your role's mcp_read and product permissions.
If the endpoint fails, make sure you are using the /v1/mcp endpoint for your Datadog site, not the old /api/unstable/ URL.
If the setup flow looks different from this post, follow Datadog's docs. Datadog has changed the endpoint and the recommended install path at least once already.