Connect Datadog to Claude Code
Search, read and write Datadog from Claude Code. Arlet links the two through one MCP connection and takes care of keys and authentication.
Arlet makes Datadog's official MCP server available from the AI client you already use. Signing in to Datadog completes the connection.
The AI can search logs, metrics, traces, monitors, incidents, dashboards and RUM events and create notebooks (core toolset). This targets the US1 site (datadoghq.com), and your role needs the mcp_read permission (mcp_write for writes). The available tools are those provided by Datadog's official server.
How to connect Datadog to Claude Code
- 1
In the Arlet dashboard, open Integrations β Add an integration and choose Datadog. Sign in with Link Datadog, name the connection and click Create.
- 2
In your terminal, run claude mcp add --transport http arlet https://mcp.arlet.dev/mcp/ to add Arlet as an MCP server.
- 3
Start Claude Code, run /mcp, select arlet and click Authenticate.
- 4
Your browser opens. Sign in with Google and click Allow on the consent screen. The connection is complete.
The connection is per user and works across every project on the same machine.
What you can do
Datadog tools that Claude Code can call.
search_datadog_logsSearch logs.
analyze_datadog_logsAggregate and analyze logs.
search_datadog_metricsSearch metrics.
get_datadog_metricGet metric values.
search_datadog_spansSearch APM spans.
get_datadog_traceGet a trace.
search_datadog_monitorsSearch monitors.
search_datadog_incidentsSearch incidents.
get_datadog_incidentGet an incident's details.
search_datadog_eventsSearch events.
search_datadog_hostsSearch hosts.
search_datadog_dashboardsSearch dashboards.
search_datadog_rum_eventsSearch RUM events.
search_datadog_notebooksSearch notebooks.
create_datadog_notebookCreate a notebook.
The tool list follows what Datadog's official MCP server provides and may change.
Example uses
Investigate an outage
Start from the firing monitors, follow the related logs and traces, and list likely causes.
Understand error trends
Aggregate recent error logs by service and error type.
Write a postmortem
Collect an incident's timeline and related metrics into a notebook.
Check performance
Query latency metrics and spans to find the slowest endpoints.
Prompts you can use as-is
- List the monitors currently alerting and show five related error logs for each
- Aggregate the last hour of error logs for the checkout service by error type
- Collect the timeline and related metrics for incident #123 and create a postmortem notebook
- Show the five endpoints in the api service with the highest p95 latency
