> 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/dynatrace.md).

# Dynatrace

Connect an agent to a Dynatrace environment's MCP server for problems, logs, metrics and entity data.

Dynatrace runs an MCP server per environment, behind its MCP gateway. It gives an agent access to problems, logs, metrics and entity data from your Dynatrace environment. ilert connects to it with a bearer token.

#### Prerequisites

* A Dynatrace environment with the MCP gateway available
* A platform token with the scopes the tools need, created as described in Dynatrace's [Setup guide](https://docs.dynatrace.com/docs/dynatrace-intelligence/dynatrace-mcp)
* Your environment's MCP **Server URL**

Unlike Datadog and New Relic, the Dynatrace endpoint is per environment, so you supply it yourself. It follows this shape:

```
https://{environment}.apps.dynatrace.com/platform-reserved/mcp-gateway/v0.1/servers/dynatrace-mcp/mcp
```

Replace `{environment}` with your environment ID. The same URL is shown as a hint under the field in the dialog.

#### 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 **Dynatrace MCP Server** card
{% endstep %}

{% step %}
Fill in the dialog:

* **Name:** a name for the connector (defaults to "Dynatrace MCP")
* **Server URL:** your environment's MCP gateway URL
* **Token:** the Dynatrace platform token

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

{% step %}
Click **Test connection** to confirm the URL and token work
{% endstep %}

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

{% hint style="info" %}
The Server URL must be a public `https://` address. A Dynatrace Managed environment that is only reachable inside your network has to be exposed through a public HTTPS hostname first — see [Host URL rules](/ai-and-agents/mcp/external.md#host-url-rules).
{% endhint %}

#### Connect MCP server with agent

To connect Dynatrace 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 **Dynatrace MCP Server** row
{% endstep %}

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

{% step %}
In the dialog, choose the Dynatrace connector you created under **Select connector** (or create one here — the same Server URL 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 Dynatrace 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/dynatrace.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.