Claude Code How to use Datadog with Claude Code
You want Datadog inside Claude Code so it can investigate production errors, compare incident volume over time, trace a slow request, and find useful observability dimensions — without you copy-pasting between tabs. Here is the whole setup, once.
Create your Datadog gateway
The gateway is the thing Claude Code connects to, and it is where you decide which Datadog tools an agent may use. You create it once and every client reuses it.
-
Create an Arcade account
Sign up and open the dashboard. The free tier is enough to follow this through.
-
Create an MCP Gateway and select your Datadog tools
In the dashboard, create a gateway and pick the Datadog tools you want to expose. The gateway is what your client connects to, and it is where tool access is decided.
-
Copy your gateway URL
Every client below needs it.
https://api.arcade.dev/mcp/<YOUR-GATEWAY-SLUG>
Connect the gateway to Claude Code
-
Add the gateway as a remote HTTP MCP server
claude mcp add arcade --transport http "<YOUR_ARCADE_GATEWAY_URL>"
-
Verify it was added
claude mcp get arcade claude mcp list
-
Try it out
Open Claude Code in your project and ask it to use one of your Datadog tools.
Full Claude Code guide in the docs steps verified 2026-08-13
Get started with Datadog prompts
Claude Code can now act on your Datadog account. Click a prompt to copy it.
Keep the shared API key or secret in Arcade and allow only the read-only searches your agent needs. Pair it with Contextual Access policies to control access before an agent can inspect logs, spans, or traces.
