OBSERVABILITY INVESTIGATION / Dynatrace
Dynatrace remote MCP
Generate and execute DQL and investigate telemetry through the MCP gateway in a Dynatrace environment.
“Dynatrace MCP server”
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.
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.
- 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"
}
}
} 04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://docs.dynatrace.com/docs/dynatrace-intelligence/dynatrace-mcp
Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports
https://docs.dynatrace.com/docs/dynatrace-intelligence/agentic-and-generative-ai
Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports