Log inSubmit server
Dynatrace MCP logo

Dynatrace MCP

by dynatrace-oss

Connects AI assistants to Dynatrace for observability queries, incident analysis, security insights, and automation.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Dynatrace MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "dynatrace-oss-dynatrace-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@dynatrace-oss/dynatrace-mcp-server"
      ],
      "env": {
        "DT_ENVIRONMENT": "YOUR_VALUE_HERE",
        "DT_MCP_TOKEN_STORAGE": "YOUR_VALUE_HERE",
        "DT_GRAIL_QUERY_BUDGET_GB": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @dynatrace-oss/dynatrace-mcp-server

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1mo ago.

Overview

The dynatrace-oss/dynatrace-mcp MCP server connects AI assistants to a Dynatrace environment through a local stdio process. It exposes tools for DQL queries, problem and vulnerability analysis, entity discovery, Davis Intelligence, notifications, and shared notebooks. Authentication uses an OAuth authorization flow in a browser, with tokens stored in the operating system keychain by default. The repository is deprecated at version 2.1.2, so use it only when maintaining an existing setup or evaluating its migration path.

Use cases

  • Investigate Dynatrace problems with correlated logs and traces
  • Query Grail data using natural-language DQL requests
  • Review vulnerabilities, exceptions, and Kubernetes events
  • Send operational notifications through Slack, email, or events
  • Create Dynatrace notebooks from investigation results

Key features

  • Execute and validate Dynatrace DQL
  • Search Dynatrace entities and observability problems
  • Query vulnerabilities, exceptions, and Kubernetes events
  • Use Davis Copilot and Davis analyzers
  • Send notifications and create notebooks
  • Track Grail query budget consumption

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

Not checked yetLast checked Today

We have not completed a health check for this listing yet.

10/27 checks healthy over the last 92d

Supply-chain signal

1 high-severity advisory on record for this package. Most advisories affect transitive dependencies and may not be exploitable in this server's actual usage — this is a directional signal, not a security audit.

Critical 0High 1Medium 2Low 1

Scanned 6d ago via OSV.dev · @dynatrace-oss/dynatrace-mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars137Stargazers on the source repository.
npm downloads84kPackage downloads in the last 30 days.
Last commit2mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How Dynatrace MCP works

What the dynatrace-oss/dynatrace-mcp MCP server does

The dynatrace-oss/dynatrace-mcp MCP server lets supported AI assistants access data and workflows in the Dynatrace observability platform. It is intended for local development environments and communicates with an MCP client through stdio. The project can retrieve production observability data, investigate incidents, inspect security findings, and help automate operational actions.

Available capability areas include problem management, vulnerability and exception lookup, Kubernetes event retrieval, Grail data queries, entity search, Davis Copilot interactions, notifications, and result sharing. Example operations include executing or validating DQL, generating DQL from natural-language requests, explaining DQL, finding entities by name, sending Slack or email messages, sending events, and creating Dynatrace notebooks.

The repository is deprecated. Release 2.1.2 was stated to be the final release, with no further updates planned. The README recommends Dynatrace-for-AI with dtctl for local development and a separate Dynatrace Remote MCP Server for remote or agent-to-agent use cases.

How it works

An MCP client starts the package as a local stdio server using Node.js. The server requires the URL of a Dynatrace Platform environment through DT_ENVIRONMENT; classic Dynatrace URLs are not supported for this setting. After startup, authentication uses the OAuth Authorization Code Flow in a browser. The resulting token is reused from the operating system keychain on later starts, so the browser generally opens only once per token lifetime.

The dynatrace-oss/dynatrace-mcp MCP server can issue DQL queries against Dynatrace Grail. Query operations may create consumption charges based on the amount of data scanned, including logs, events, and metrics. A session-level Grail budget tracks scanned bytes and warns as usage approaches the configured limit.

Setup and configuration

Node.js version 24 or newer is required. The package can be launched with:

Terminal
npx -y @dynatrace-oss/dynatrace-mcp-server

Configure DT_ENVIRONMENT with a Dynatrace Platform URL such as https://abc12345.apps.dynatrace.com. The default token storage uses the host operating system’s keychain. For headless or container environments where that facility is unavailable, set DT_MCP_TOKEN_STORAGE=file; tokens are then stored under ~/.config/dynatrace-mcp/.

DT_GRAIL_QUERY_BUDGET_GB controls the session budget for Grail queries and defaults to 1000 GB. Restarting the MCP server resets the session budget. Narrow time ranges and Grail buckets can help reduce query consumption.

Tools and capabilities

The dynatrace-oss/dynatrace-mcp MCP server supports these documented groups:

  • Observability and problem management, including problems, vulnerabilities, exceptions, and Kubernetes events
  • Grail querying with DQL execution, verification, generation, and explanation
  • Entity discovery by name
  • Dynatrace Intelligence through Davis Copilot and analyzer operations
  • Notifications through Slack, email, and Dynatrace events
  • Sharing results by creating Dynatrace notebooks
  • Investigation workflows that correlate problems, spans, logs, and trace IDs
  • Deployment health gates and security compliance assessment, where the relevant Dynatrace capabilities are available

Limitations and notes

The local package is free to use, but Dynatrace Grail queries may incur charges under the account’s consumption model. Review the applicable Dynatrace pricing and licensing terms before running broad or repeated queries.

New deployments should evaluate the maintained alternatives listed by the project rather than assuming this repository will receive fixes or new features. The server also requires a Dynatrace environment and an authentication flow, so it is not a standalone monitoring data source.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Dynatrace MCP

Use Node.js 24 or newer and run `npx -y @dynatrace-oss/dynatrace-mcp-server` as a stdio MCP server.

Set `DT_ENVIRONMENT` to the URL of a Dynatrace Platform environment, not a classic Dynatrace URL.

No platform token or OAuth client is required for the documented quickstart. Authentication uses an OAuth Authorization Code Flow in a browser, and the token is stored for reuse.

It can use file-based token storage when the OS keychain is unavailable. Set `DT_MCP_TOKEN_STORAGE=file` to store tokens under `~/.config/dynatrace-mcp/`.

No. The repository is deprecated, and version 2.1.2 was identified as the final release. The README recommends maintained alternatives.

Related MCP servers

All in Monitoring All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewDynatrace MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/dynatrace-oss-dynatrace-mcp?style=directory)](https://allmcps.com/mcp/dynatrace-oss-dynatrace-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/dynatrace-oss-dynatrace-mcp"><img src="https://allmcps.com/api/badge/dynatrace-oss-dynatrace-mcp?style=directory" alt="Dynatrace MCP on AllMCPs" /></a>