---
title: "Dynatrace remote MCP: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/mcp-servers/dynatrace-hosted/
description: "Generate and execute DQL and investigate telemetry through the MCP gateway in a Dynatrace environment."
---

# Dynatrace remote MCP: review, setup & limitations · Undominated.ai

> Generate and execute DQL and investigate telemetry through the MCP gateway in a Dynatrace environment.

[← Explore all mcp servers](/mcp-servers/)

OBSERVABILITY INVESTIGATION / Dynatrace

# Dynatrace remote MCP

Generate and execute DQL and investigate telemetry through the MCP gateway in a Dynatrace environment.

 [See setup guidance ↓](#setup)[Original source ↗](https://docs.dynatrace.com/docs/dynatrace-intelligence/dynatrace-mcp)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 2 linked sources
 Publisher Dynatrace
 Licence Not established
 [Read what was—and wasn’t—checked ↓](#review)

“Dynatrace MCP server”

 [Dynatrace · upstream description ↗](https://docs.dynatrace.com/docs/dynatrace-intelligence/dynatrace-mcp) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - Publisher-supported successor to the deprecated local adapter.
- Distinguishes DQL generation from execution and lists tool-specific permissions.
- Dynatrace’s MCP page says the bearer token works only inside the user’s permissions, and that an OAuth client’s effective permissions are the intersection of the client scopes and the creating user’s permissions.
- The agentic-AI page says MCP calls outside the UI are priced under the subscription model, and that accounts missing the required capability can no longer use the MCP server.

### A good fit for

 - Generate a DQL query, review it, then retrieve a bounded telemetry result.
- Inspect active problems using a token restricted to required storage categories.
- Calling Dynatrace MCP tools with a user or OAuth token whose permissions already include those tools
- Not for an account that the pricing page says no longer has the required capability

### Weigh up before choosing

 - Requires the documented DPS licensing capability; MCP and generated-query usage can consume billable capacity.
- The Data Analysis tool limits results to 1000 records; aggregate or narrow the query.
- OAuth requires a confidential client with secret; public clients, CIMD and dynamic registration are not supported in the reviewed guide.
- The bearer token does not expand past the user’s permissions, and an OAuth client does not keep scopes the creating user lacks.
- The “no longer able” sentence is split by a link. The quoted tail does not include the subject before that link.
- No licence was stated on these pages, and none was inferred.
- This review did not execute the resource.
- The server was not called.
- Effective OAuth permissions are the intersection of client and creator permissions, and supplying only a short-lived bearer token does not configure automatic refresh.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - https://docs.dynatrace.com/docs/dynatrace-intelligence/dynatrace-mcp
- https://docs.dynatrace.com/docs/dynatrace-intelligence/agentic-and-generative-ai
- Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.

### Our findings

 - The current official guide supports confidential OAuth as well as platform tokens; the older migration comparison saying token-only is stale.
- Generating DQL does not execute it; the Data Analysis tool does.
- The Dynatrace MCP page says that, whatever the authentication method, the bearer token works only within the user’s permissions.
- For an OAuth client, effective permissions are the intersection of the client’s configured permissions and the permissions of the user who created the client.
- The agentic and generative AI page says API or MCP calls outside the UI are priced on the subscription model, and the following text says those accounts are no longer able to use the MCP server or direct generative or agentic API calls.
- Hosted OAuth currently requires a confidential client with client ID and secret; CIMD, public clients and dynamic registration are not supported.

### Not established by this review

 - Server startup, authentication, live tool execution and security isolation were not tested.
- Published package/container parity with a source revision and hosted implementation internals were not tested.
- The resource was not executed and its tools were not called.
- The server was not called. A source review is not a runtime or security certification.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Connect a server deliberately.

[Upstream setup instructions ↗](https://docs.dynatrace.com/docs/dynatrace-intelligence/dynatrace-mcp)
 - Replace the environment placeholder and supply a platform bearer token through client secret headers, or configure the documented confidential OAuth client.
- Grant gateway invoke/read plus only the required tool scopes; log queries additionally require storage:buckets:read and storage:logs:read.
- Use small query time ranges and verify which identity and storage scope are active.
- Grant mcp-gateway:servers:read and mcp-gateway:servers:invoke to both user and token alongside the tool-specific scopes; use a Platform token or supported confidential-client flow.

### Before you start

 - A licensed Dynatrace environment and HTTP MCP client supporting the selected bearer or confidential OAuth flow.

### Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

 {
 "mcpServers": {
 "dynatrace": {
 "type": "http",
 "url": "https://YOUR_ENVIRONMENT.apps.dynatrace.com/platform-reserved/mcp-gateway/v0.1/servers/dynatrace-mcp/mcp"
 }
 }
} Copy configuration ↗

### Compatibility

A licensed Dynatrace environment and HTTP MCP client supporting the selected bearer or confidential OAuth flow.

### Transports

Streamable HTTP

### Observability investigation

 - Both user and token permissions constrain telemetry access; query execution consumes platform resources.

### Cost model

Dynatrace MCP invocations, generative capabilities and Grail queries follow the applicable consumption rate card.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Publisher setup, capabilities and operating boundaries ↗](https://docs.dynatrace.com/docs/dynatrace-intelligence/dynatrace-mcp) Checked 2026-10-14 https://docs.dynatrace.com/docs/dynatrace-intelligence/dynatrace-mcp Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports
- [Publisher setup, capabilities and operating boundaries ↗](https://docs.dynatrace.com/docs/dynatrace-intelligence/agentic-and-generative-ai) Checked 2026-10-14 https://docs.dynatrace.com/docs/dynatrace-intelligence/agentic-and-generative-ai Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### New Relic Ground Truth MCP ↗ Connect supported agents to New Relic telemetry and operational tools with account RBAC and OAuth.](/mcp-servers/new-relic/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Inspect resource evidence](/tools/)
- [Choose a host](/agents/)
- [Inspect reusable workflows](/skills/)
- [Use Undominated data](/api/)
