Skip to content
MCP server

Dynatrace Managed MCP

Query logs, events, metrics, problems and SLOs from self-hosted Dynatrace Managed

Runs locallyStatus and history
Install
Pricing
Open source
Platforms
CLI, self-hosted, Linux
Runs
Locally
Version
2.0.0
Listing updated
today

Similar MCP servers

About Dynatrace Managed MCP

Dynatrace Managed MCP is an open-source MCP server for cloud and infrastructure. It runs locally on your machine and is started by your AI client.

This community-supported server is built for Dynatrace Managed, the self-hosted edition, and the README points SaaS users to a separate Dynatrace MCP. One use case it names is reading historical observability data that was never migrated after a move to SaaS, with a SaaS server handling live data.

It covers problems, security problems and vulnerabilities, monitored entities with their relationships, SLOs with evaluation and error budgets, system events, log search with content and time filters, and metrics through the V2 Metrics API. Several Managed environments can be configured at once with aliases, and a rate limiter defaults to 20 calls per 20 seconds.

Setup needs an API token with read scopes such as problems, logs, metrics, entities, events, security problems and SLO, plus an environment configuration in a YAML or JSON file or the DT_ENVIRONMENT_CONFIGS variable. It runs locally over stdio, with a remote HTTP and SSE mode, and Claude Code can install it as a plugin. Telemetry is optional.

Install

Run in a terminal

claude mcp add dynatrace-managed-mcp --env DT_ENVIRONMENT_CONFIGS='<DT_ENVIRONMENT_CONFIGS>' -- npx -y @dynatrace-oss/dynatrace-managed-mcp-server

Add to claude_desktop_config.json

{
  "mcpServers": {
    "dynatrace-managed-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@dynatrace-oss/dynatrace-managed-mcp-server"
      ],
      "env": {
        "DT_ENVIRONMENT_CONFIGS": "<DT_ENVIRONMENT_CONFIGS>"
      }
    }
  }
}

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "dynatrace-managed-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@dynatrace-oss/dynatrace-managed-mcp-server"
      ],
      "env": {
        "DT_ENVIRONMENT_CONFIGS": "<DT_ENVIRONMENT_CONFIGS>"
      }
    }
  }
}

Add to .vscode/mcp.json

{
  "servers": {
    "dynatrace-managed-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@dynatrace-oss/dynatrace-managed-mcp-server"
      ],
      "env": {
        "DT_ENVIRONMENT_CONFIGS": "<DT_ENVIRONMENT_CONFIGS>"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "dynatrace-managed-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@dynatrace-oss/dynatrace-managed-mcp-server"
      ],
      "env": {
        "DT_ENVIRONMENT_CONFIGS": "<DT_ENVIRONMENT_CONFIGS>"
      }
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "dynatrace-managed-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@dynatrace-oss/dynatrace-managed-mcp-server"
      ],
      "env": {
        "DT_ENVIRONMENT_CONFIGS": "<DT_ENVIRONMENT_CONFIGS>"
      }
    }
  }
}

Using several servers? Build one config file with the MCP config generator.

Configuration

  • DT_MCP_RATE_LIMIT_MAX_CALLSMaximum number of tool calls allowed per rate limit window. Defaults to 20.
  • DT_MCP_RATE_LIMIT_WINDOW_MSRate limit window size in milliseconds. Defaults to 20000 (20 seconds).
  • DT_ENVIRONMENT_CONFIGSAn escaped JSON array that defines the Dynatrace Managed environment(s) to connect to. See README file for contents of this.Required
  • LOG_LEVELLogging level (e.g. debug, info, warning, error)
  • DT_MCP_ENABLE_TELEMETRYEnable telemetry

What it does

Problems and security
List and fetch problems and vulnerability details.
Entities and SLOs
Inspect monitored entities, relationships and error budgets.
Log search
Filter logs by content and time.
Metrics queries
Analyse metrics via the V2 Metrics API.
Multiple environments
Query several Managed clusters by alias.
Rate limiting
Defaults to 20 calls per 20 seconds.

Good for

  • Investigate an incident with problems, logs and metrics together
  • Review vulnerability findings across environments
  • Read historical data left in a Managed cluster after migration
  • Check SLO error budgets

Pricing

Open source

Dynatrace Managed MCP FAQ

Does it work with Dynatrace SaaS?

No. It targets Managed; the README points to a separate Dynatrace MCP for SaaS.

What access does it need?

An API token with read scopes for entities, events, logs, metrics, problems, security problems and SLOs.

Can it query several environments?

Yes, through the environment configuration file with aliases.

Is it officially supported?

It is open source and supported by the community through GitHub Issues.

Is Dynatrace Managed MCP free?

Yes. Dynatrace Managed MCP is open source, so you can use and self-host it for free.

How do I add Dynatrace Managed MCP to Claude Code?

Run this command in your terminal: claude mcp add dynatrace-managed-mcp --env DT_ENVIRONMENT_CONFIGS='<DT_ENVIRONMENT_CONFIGS>' -- npx -y @dynatrace-oss/dynatrace-managed-mcp-server

What are the best alternatives to Dynatrace Managed MCP?

The closest alternatives to Dynatrace Managed MCP are REA, Context7, Chrome DevTools MCP, Codebase Memory and GitHub.

Where this comes from

  • Description: written from the project's README.
  • Install steps: from the official MCP Registry entry.

How AIPoweredBot checks servers