# Datadog — MCP Server

> Query metrics, logs, traces and monitors from a conversation instead of a dashboard.

**Source:** https://mcpplaygroundonline.com/mcp-servers/datadog  
**Transport:** http  
**Requires auth:** Yes

---

## What it does

The server turns the Datadog platform into a set of MCP tools an agent can chain. Log search accepts the same query syntax you use in the Log Explorer, scoped by time window, so an agent can narrow from a service to a single request. Metrics are queryable, which lets a model pull a timeseries and reason about the shape of it rather than describe a screenshot. APM traces are reachable for latency work, and monitors and incidents are readable so an agent can answer what is currently firing and what it is attached to. The practical value is correlation: the model can pull a monitor, fetch the logs from the same window, check the deploy events around it and propose a cause in one turn. Datadog runs regional endpoints — US1, US3, US5, EU and AP — and you must connect to the one your organisation lives in.

## Tools exposed

- log search — query logs with Log Explorer syntax over a time range
- metrics query — pull a timeseries for a metric and scope it by tag
- APM traces — fetch traces and spans for latency and error investigation
- monitors — list monitors, read definitions and check current state
- incidents — read incidents and their timelines
- events — deploy and change events for correlating a regression

## Example queries you can run

- "Which service accounted for the p99 latency increase between 14:00 and 14:30?"
- "Show me the error logs for checkout-api in the last hour, grouped by error type."
- "What monitors are alerting right now, and were there deploys just before they fired?"
- "Compare request volume for the payments service this week against last week."

## Details

- **Recommended model:** anthropic/claude-sonnet-4.5 — Incident work is multi-step correlation across logs, metrics and deploys. Sonnet 4.5 holds the thread across several tool calls where cheaper models stop at the first result.
- **Transport:** http
- **Authentication:** Required — Datadog API key plus an application key, sent as headers. Use the endpoint for your region — US3, US5, EU and AP have their own hostnames.
- **Hosted endpoint:** https://mcp.datadoghq.com/api/unstable/mcp-server/mcp
- **Official source:** [Datadog MCP Server — official documentation](https://docs.datadoghq.com/bits_ai/mcp_server/)

## Connecting to Datadog

URL format:

```
https://mcp.{region}.datadoghq.com/api/unstable/mcp-server/mcp
```

### Connection examples

**US1 (default)**

```
https://mcp.datadoghq.com/api/unstable/mcp-server/mcp
```

**EU**

```
https://mcp.datadoghq.eu/api/unstable/mcp-server/mcp
```

**US3**

```
https://mcp.us3.datadoghq.com/api/unstable/mcp-server/mcp
```

**US5**

```
https://mcp.us5.datadoghq.com/api/unstable/mcp-server/mcp
```

**AP1**

```
https://mcp.ap1.datadoghq.com/api/unstable/mcp-server/mcp
```

## Frequently asked questions

### What is the Datadog MCP server?

It is Datadog’s official remote MCP server. It exposes logs, metrics, APM traces, monitors, incidents and events as MCP tools, so an AI assistant can investigate your observability data directly instead of you translating a question into a dashboard query.

### Which endpoint should I use?

The one matching your Datadog site. US1 is mcp.datadoghq.com, EU is mcp.datadoghq.eu, and US3, US5 and AP1 each have their own hostname. Connecting to the wrong region fails authentication even with a valid key, which is the most common setup mistake.

### What credentials does it need?

A Datadog API key and an application key. The application key carries the permissions, so scope it deliberately — an agent inherits exactly what that key can do, and read-only is the right default for investigation work.

### Is the endpoint stable?

The path still contains "unstable", which is Datadog’s own signal that the API surface may change. It works today and is documented, but pin your expectations accordingly and re-check after Datadog platform updates.

### Can I test it without wiring up a client?

Yes. Paste the regional URL into MCP Playground with your keys and the tools list loads in the browser. You can run a log search and see the raw JSON before deciding whether to put it in front of an agent.

---

_Test this server across 40+ models on MCP Playground: https://mcpplaygroundonline.com/mcp-servers/datadog — free, no install._