> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/ai-and-agents/mcp/external/datadog.md).

# Datadog

Connect an agent to Datadog's MCP server for metrics, logs, traces and monitors, using a bearer token.

Datadog hosts its own MCP server, which gives an agent access to your Datadog metrics, logs, traces and monitors. ilert connects to it with a bearer token you create in Datadog.

#### Prerequisites

* A Datadog account with the MCP server enabled for your organisation
* A token for the MCP server, created as described in Datadog's [Setup guide](https://docs.datadoghq.com/mcp_server/setup/)
* The Datadog **site** your organisation is on — visible in your Datadog URL (`datadoghq.eu`, `us3.datadoghq.com`, …)

The endpoint is fixed per site and derived from your selection, so there is no URL field:

<table><thead><tr><th width="243.15625">Site</th><th>MCP endpoint</th></tr></thead><tbody><tr><td>US1 (datadoghq.com)</td><td><code>https://mcp.datadoghq.com/v1/mcp</code></td></tr><tr><td>US3 (us3.datadoghq.com)</td><td><code>https://mcp.us3.datadoghq.com/v1/mcp</code></td></tr><tr><td>US5 (us5.datadoghq.com)</td><td><code>https://mcp.us5.datadoghq.com/v1/mcp</code></td></tr><tr><td>EU1 (datadoghq.eu)</td><td><code>https://mcp.datadoghq.eu/v1/mcp</code></td></tr><tr><td>AP1 (ap1.datadoghq.com)</td><td><code>https://mcp.ap1.datadoghq.com/v1/mcp</code></td></tr><tr><td>AP2 (ap2.datadoghq.com)</td><td><code>https://mcp.ap2.datadoghq.com/v1/mcp</code></td></tr><tr><td>UK1 (uk1.datadoghq.com)</td><td><code>https://mcp.uk1.datadoghq.com/v1/mcp</code></td></tr></tbody></table>

#### Create the connector

{% stepper %}
{% step %}
Navigate to **Connectors** in the ilert navigation menu
{% endstep %}

{% step %}
Scroll to the **MCP Servers** section and click **Connect** on the **Datadog MCP Server** card
{% endstep %}

{% step %}
Fill in the dialog:

* **Name:** a name for the connector (defaults to "Datadog MCP")
* **Datadog region:** your Datadog site (defaults to EU1)
* **Token:** the Datadog MCP token you created

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2Fgit-blob-a9cef59d8096a8da29047b338f230d5d932d0131%2Fdatadog-mcp-create-dialog.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Click **Test connection** to confirm the token works and the tools can be listed
{% endstep %}

{% step %}
Click **Save**
{% endstep %}
{% endstepper %}

{% hint style="info" %}
The site must match the organisation the token belongs to. A token from a US organisation used against the EU endpoint fails authentication.
{% endhint %}

#### Connect MCP server with agent

To connect Datadog with your AI SRE agent:

{% stepper %}
{% step %}
Navigate to **Agents** in the ilert navigation menu
{% endstep %}

{% step %}
Open the agent detail view for the agent you want to configure
{% endstep %}

{% step %}
Go to the **Tools** tab
{% endstep %}

{% step %}
Under the **External MCP Servers** section, locate the **Datadog MCP Server** row
{% endstep %}

{% step %}
Click **Connect**
{% endstep %}

{% step %}
In the dialog, choose the Datadog connector you created under **Select connector** (or create one here — the same region and token fields appear)
{% endstep %}

{% step %}
Click **Add**
{% endstep %}

{% step %}
Expand the server card to load its tools and enable the ones the agent may use, then save the agent
{% endstep %}
{% endstepper %}

The Datadog integration is now connected and ready to use for root cause analysis.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ilert.com/ai-and-agents/mcp/external/datadog.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.