If you came here for the command, use this.
Quick command
claude mcp add --transport http datadog https://mcp.datadoghq.com/api/unstable/mcp-server/mcpThe 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 Datadog's default MCP endpoint. If your organization runs on another Datadog site, use the endpoint Datadog lists for that site.
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.
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 listInside Claude Code, you can also run:
/mcpThe 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 may send you through a browser login.
Claude Code can only read data that your Datadog account can read. Your role also needs MCP permissions for the tools you want to use, plus the normal Datadog product permission for the resource being queried.
For example, reading monitors needs MCP read access and monitor read access. The same pattern applies to logs, metrics, dashboards, and APM.
Optional: limit Datadog tools
Add toolsets to the URL if you only want Claude Code to see specific Datadog tool groups.
For example:
claude mcp add --transport http datadog "https://mcp.datadoghq.com/api/unstable/mcp-server/mcp?toolsets=apm,llmobs"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.
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 your Datadog role, MCP permissions, and product permissions.
If the endpoint fails, make sure you are using the endpoint for your Datadog site.
If the setup flow looks different from this post, follow Datadog's docs. MCP support is still on an unstable endpoint, so the exact flow may change.
References
Final check
Most setups only need the HTTP command, OAuth login, and the right permissions. Change the URL only when your Datadog site or toolset requirements call for it.