# Datadog

<div style={{maxWidth: '720px'}}>
![The Datadog connector in Workspace Settings, for logs, metrics, traces, and incidents, with a Connect button](</docs/_next/static/media/datadog-connector.3i7gfb1wkzwb0.jpg>)
</div>

The [Datadog MCP server](https://docs.datadoghq.com/mcp_server/) lets agents query your Datadog account, so they have production context when they debug errors, slow requests, and incidents.

For use cases and example prompts, see [Datadog for AI coding agents](/integrations/datadog).

## What is Datadog? [#what-is-datadog]

[Datadog](https://www.datadoghq.com) is an observability platform for logs, metrics, traces, monitoring, and incident management.

## What agents can do [#what-agents-can-do]

Once you connect Datadog, agents can use Datadog's default MCP tools to:

- Search logs, metrics, APM traces, and spans
- Look up monitors, incidents, events, and hosts
- Read real user monitoring (RUM) data
- Read, create, and update dashboards
- Read, create, edit, and delete notebooks

Agents can only do what your access token allows. A Datadog admin also controls MCP under **Organization Settings → MCP Server**: **MCP Access** must be on, and agents can only change anything once **MCP Write Access** is on, which it isn't by default. The token's account needs the **MCP Read** permission, plus **MCP Write** for changes; the Standard role has both. See [Datadog's required permissions](https://docs.datadoghq.com/mcp_server/setup/#required-permissions).

## Setup [#setup]

Create a [personal access token](https://docs.datadoghq.com/account_management/personal-access-tokens/) in Datadog under **Personal Settings → Access Tokens**. For a connection owned by **Workspace**, use a [service access token](https://docs.datadoghq.com/account_management/service-access-tokens/) from **Organization Settings → Service Accounts** instead, so it doesn't depend on one person. Datadog API keys and application keys won't work here.

Then connect it in Superconductor: find **Datadog** on the [Connectors page](https://www.superconductor.com/workspaces/default/connectors), click **Connect**, and paste the token into **Datadog Access Token**. The [Connectors guide](/docs/integrations/connectors#fill-in-the-connection-details) explains **Me** and **Workspace** ownership and the separate settings for personal assistants, team assistants, and projects. When the token expires, agents lose their Datadog tools and the Connectors page won't warn you, so paste a new one under **Manage** before then.

<Callout type="info">
**Is your Datadog organization outside US1?** This connector works with organizations on US1 (`app.datadoghq.com`). If your organization uses another site, such as `datadoghq.eu`, [add your own MCP server](/docs/integrations/connectors/custom-mcp-servers) with your site's URL from [Datadog's setup guide](https://docs.datadoghq.com/mcp_server/setup/), choose **Bearer**, and paste your token.
</Callout>

## When to use it [#when-to-use-it]

Ask agents to use Datadog when a ticket involves production errors, slow requests, a firing monitor, or an open incident. For example:

```text
Find the errors behind the checkout incident in Datadog, then fix the code that's throwing them.
```

```text
Check the p95 latency for the /api/orders endpoint in Datadog over the last week and find what made it slower.
```

```text
Our "High error rate" monitor in Datadog fired overnight. Find out why and suggest a fix.
```

```text
Summarize last week's traffic and error rates from our Datadog service dashboard for the weekly team report.
```