Dynatrace MCP Server for Claude
Connect Claude to Dynatrace observability data — run DQL queries, investigate problems and vulnerabilities, analyze Kubernetes events, forecast timeseries, and resolve entity names — with the official Dynatrace open-source MCP server.
Open the source and read safety notes before installing.
Safety notes
- The server connects to your live Dynatrace environment — keep DT_ENVIRONMENT scoped to a non-production environment during initial testing.
- Platform tokens are stored in the OS keychain by default; ensure keychain access is secured on shared systems.
- DQL execution and automation tools (event notifications, Slack messaging) can take actions on your Dynatrace account — review Claude's proposed operations before executing.
Privacy notes
- DQL query results, entity data, problem details, and log content from your Dynatrace environment are surfaced in Claude's context.
- Dynatrace Platform Tokens are secrets — store them in your environment or MCP client config, never in repositories.
Prerequisites
- A Dynatrace Platform environment URL (e.g. `https://abc12345.apps.dynatrace.com`).
- First-run auth is handled via browser-based Authorization Code Flow — no token needed initially.
- For headless use: a Dynatrace Platform Token with `mcp-gateway:servers:invoke` and `mcp-gateway:servers:read` permissions.
- Node.js and an MCP client such as Claude Code or Claude Desktop.
Schema details
- Install type
- cli
- Troubleshooting
- No
- Scope
- Source repo
- Estimated setup
- 10 minutes
- Difficulty
- intermediate
- Website
- https://dynatrace.com
Full copyable content
{
"mcpServers": {
"dynatrace": {
"command": "npx",
"args": ["-y", "@dynatrace-oss/dynatrace-mcp-server@latest"],
"env": {
"DT_ENVIRONMENT": "https://YOUR_ENV.apps.dynatrace.com"
}
}
}
}About this resource
Overview
The Dynatrace MCP Server (@dynatrace-oss/dynatrace-mcp-server) is the official open-source
Model Context Protocol server from Dynatrace. It gives Claude access to your Dynatrace
observability platform — running DQL queries, investigating problems and vulnerabilities, analyzing
Kubernetes events, forecasting timeseries, and exploring entities — through natural language.
Authentication uses browser-based Authorization Code Flow on first run (no token needed to get started); tokens are stored in the OS keychain. For headless/CI workflows, a Platform Token with the required permissions can be used instead. The server runs as a local stdio process and is MIT-licensed.
Dynatrace also provides a native hosted MCP gateway at
https://{env}.apps.dynatrace.com/platform-reserved/mcp-gateway/v0.1/servers/dynatrace-mcp/mcp
for environments where a local npm install is not desirable.
Key capabilities
- DQL queries — generate, explain, and execute Dynatrace Query Language queries.
- Problem investigation — retrieve and analyze open problems and vulnerabilities.
- Kubernetes event analysis — explore and correlate Kubernetes events.
- Timeseries analysis — forecast and analyze metric timeseries data.
- Entity resolution — resolve entity names to IDs and explore entity metadata.
- Document retrieval — retrieve Dynatrace troubleshooting documentation and guidance.
- Automation — trigger event notifications and Slack messages from workflows.
- Davis AI — access Davis Intelligence for AI-powered root cause analysis.
How it compares
| Server | DQL/query language | Problem investigation | Kubernetes | AI-native analysis | Transport |
|---|---|---|---|---|---|
| Dynatrace MCP | Yes (DQL) | Yes | Yes | Davis AI | stdio |
| New Relic MCP | Yes (NRQL) | Yes | Limited | No | Remote HTTP |
| Datadog MCP | Yes (DQL/Logs) | Yes | Yes | No | Remote HTTP |
| Honeycomb MCP | Limited | Yes | No | No | Remote HTTP |
Dynatrace's MCP is notable for its Davis AI integration — providing AI-native root-cause analysis and anomaly detection, not just raw query access.
Installation
Claude Code
claude mcp add dynatrace \
-e DT_ENVIRONMENT=https://YOUR_ENV.apps.dynatrace.com \
-- npx -y @dynatrace-oss/dynatrace-mcp-server@latest
Replace YOUR_ENV with your environment ID. On first run, a browser window opens for
Authorization Code Flow authentication.
Claude Desktop
{
"mcpServers": {
"dynatrace": {
"command": "npx",
"args": ["-y", "@dynatrace-oss/dynatrace-mcp-server@latest"],
"env": {
"DT_ENVIRONMENT": "https://YOUR_ENV.apps.dynatrace.com"
}
}
}
}
Platform Token (headless)
Set DT_PLATFORM_TOKEN in your environment alongside DT_ENVIRONMENT to authenticate without a
browser. The token requires mcp-gateway:servers:invoke and mcp-gateway:servers:read scopes.
Requirements
- A Dynatrace Platform environment.
- Node.js (npx).
- An MCP client (Claude Code or Claude Desktop).
Security
- Prefer browser-based auth for interactive use; tokens live in the OS keychain.
- For CI/headless use, create a scoped Platform Token and rotate it regularly.
- Never commit
DT_PLATFORM_TOKENto source control.
Source Verification Notes
Verified on 2026-06-18:
- The official repository
github.com/dynatrace-oss/dynatrace-mcp(MIT, 122 stars) documents the@dynatrace-oss/dynatrace-mcp-serverpackage,DT_ENVIRONMENTenv var, Authorization Code Flow and Platform Token authentication, stdio transport, and the capability categories. - Dynatrace's official MCP documentation at
docs.dynatrace.com/docs/dynatrace-intelligence/dynatrace-mcpconfirms the native hosted gateway URL pattern and required permissions. - The Dynatrace Hub listing confirms the DQL, problem, Kubernetes, timeseries, and Davis AI capabilities as the primary tools.
- Claude Code's MCP documentation describes the
-eenv var injection pattern used above.
Source citations
Add this badge to your README
How it compares
Dynatrace MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Dynatrace MCP Server for Claude Connect Claude to Dynatrace observability data — run DQL queries, investigate problems and vulnerabilities, analyze Kubernetes events, forecast timeseries, and resolve entity names — with the official Dynatrace open-source MCP server. Open dossier | Axiom MCP Server for Claude Query observability data, manage dashboards, and monitor your systems from Claude — run APL queries against datasets, list metrics, inspect monitors, and retrieve saved queries — with the official Axiom remote MCP server. Open dossier | Honeycomb MCP Server for Claude Connect Claude to Honeycomb observability data — query traces and events, investigate alerts, manage boards and triggers, create SLOs, and cross-reference production behavior with your codebase — with the official Honeycomb hosted MCP server. Open dossier | Pydantic Logfire MCP Server for Claude Query OpenTelemetry traces and metrics, manage dashboards, analyze distributed traces, and investigate exceptions from Claude — with the official Pydantic Logfire remote MCP server hosted at logfire-us.pydantic.dev/mcp. Open dossier |
|---|---|---|---|---|
| Trust | ||||
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Category | mcp | mcp | mcp | mcp |
| Source | source-backed | source-backed | source-backed | source-backed |
| Author | Dynatrace | Axiom, Inc. | Honeycomb | Pydantic |
| Added | 2026-06-18 | 2026-06-18 | 2026-06-18 | 2026-06-18 |
| Platforms | Claude CodeCodexCursorClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop |
| Source repo | — | — | — | — |
| Safety notes | ✓The server connects to your live Dynatrace environment — keep DT_ENVIRONMENT scoped to a non-production environment during initial testing. Platform tokens are stored in the OS keychain by default; ensure keychain access is secured on shared systems. DQL execution and automation tools (event notifications, Slack messaging) can take actions on your Dynatrace account — review Claude's proposed operations before executing. | ✓The MCP server includes dashboard management tools (create, update, delete) — review any write operations before confirming. APL queries run against live datasets; complex queries over large time windows may be slow or consume significant dataset quota. | ✓The server is hosted by Honeycomb (AWS-backed) and authenticated via OAuth 2.1 or API key — write-scoped access can create/update Boards, Triggers, and SLOs. Writing to Honeycomb resources (boards, triggers, SLOs) requires the `create` scope; verify you grant only the scopes your workflow needs. Canvas investigations and alert management are write operations — review Claude's proposed changes before executing in production environments. | ✓Telemetry data returned by the MCP server may include user-controlled content from traces, logs, exceptions, model payloads, tool arguments, and tool results — treat query results as diagnostic data, not instructions. Dashboard create, update, and delete operations permanently modify your Logfire workspace; review before confirming. |
| Privacy notes | ✓DQL query results, entity data, problem details, and log content from your Dynatrace environment are surfaced in Claude's context. Dynatrace Platform Tokens are secrets — store them in your environment or MCP client config, never in repositories. | ✓Log data, traces, metrics, and monitor configurations from your Axiom datasets and organization are surfaced in Claude's context. OAuth is the recommended authentication method — no API token is stored in your MCP configuration. | ✓Trace data, event fields, alert details, and query results from Honeycomb are sent through Honeycomb's hosted MCP endpoint and surfaced in Claude's context. Honeycomb API keys (`KEY_ID:SECRET_KEY` format) are secrets — store them in your MCP client config or environment, never in repositories. | ✓OpenTelemetry trace data, span metadata, exception stack traces, query results, dashboard configurations, and project metadata from your Logfire account are surfaced in Claude's context. Remote MCP uses OAuth — no API keys in your MCP config when authenticating via browser. For API key auth, store the key in MCP config rather than shell history. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Featured in
Signals
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.