Dynatrace Managed

listing.by

Query problems, logs, events, metrics, SLOs and security issues from self-hosted Dynatrace Managed environments.

state.local.long (state.local.title)listing.badge.runs_with

listing.install

listing.local.explain

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

listing.local.needs listing.local.note

  • DT_MCP_RATE_LIMIT_MAX_CALLS listing.env.optional Maximum number of tool calls allowed per rate limit window. Defaults to 20.
  • DT_MCP_RATE_LIMIT_WINDOW_MS listing.env.optional Rate limit window size in milliseconds. Defaults to 20000 (20 seconds).
  • DT_ENVIRONMENT_CONFIGS An escaped JSON array that defines the Dynatrace Managed environment(s) to connect to. See README file for contents of this.
  • LOG_LEVEL listing.env.optional Logging level (e.g. debug, info, warning, error)
  • DT_MCP_DISABLE_TELEMETRY listing.env.optional Disable telemetry
act.add_to a11y.new_tabact.add_to a11y.new_tab

listing.share.h

listing.share.p_local

mcp.tc/i/dynatrace-managed

listing.about

Connects an AI assistant to one or more self-hosted Dynatrace Managed deployments. It can list and inspect problems, security problems, monitored entities and their relationships, SLOs with error budgets, and system events. It can also search logs and query metrics through the V2 Metrics API.

It runs locally through npx over stdio and supports several Managed environments from one server. A Dynatrace Managed API token with read scopes is required, and environments are defined in a config file or the DT_ENVIRONMENT_CONFIGS variable. The project is community supported and is meant for Managed, not SaaS.

listing.can

  • List and get problem details from monitored services
  • List and get security problems and vulnerabilities
  • Look up monitored entities and their relationships
  • Check SLO status and error budgets
  • List and get system events
  • Search and filter logs by content and time
  • Query performance metrics with the V2 Metrics API
  • Query multiple Managed environments from one server

listing.tools

listing.notools.local

listing.prompts

  • List open problems in my production Dynatrace Managed environment

  • Search logs for errors from the checkout service in the last hour

  • Show the error budget for our payments SLO

  • Which security problems affect my Kubernetes workloads?

listing.setup.h

listing.setup.local

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport stdio dynatrace-managed --env "DT_ENVIRONMENT_CONFIGS=<YOUR_DT_ENVIRONMENT_CONFIGS>" -- npx -y @dynatrace-oss/dynatrace-managed-mcp-server
  1. Start Claude Code and type /mcp. dynatrace-managed should show as connected.

Add --scope user to make it available in every project. Replace the placeholders with your own values.

Claude Desktop

  1. Open Settings → Developer → Edit Config. It opens claude_desktop_config.json. Add:
claude_desktop_config.json
{
  "mcpServers": {
    "dynatrace-managed": {
      "command": "npx",
      "args": [
        "-y",
        "@dynatrace-oss/dynatrace-managed-mcp-server"
      ],
      "env": {
        "DT_ENVIRONMENT_CONFIGS": "<YOUR_DT_ENVIRONMENT_CONFIGS>"
      }
    }
  }
}
  1. Save the file and restart Claude Desktop. Replace the placeholders with your own values.

Needs Node.js on your computer. The file lives in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows.

Cursor

Add to Cursor a11y.new_tab

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

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

Needs Node.js on your computer. Replace the placeholders with your own values.

VS Code

Install in VS Code a11y.new_tab

Or from a terminal:

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

Or commit it to the repo in .vscode/mcp.json:

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

Needs Node.js on your computer.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "dynatrace-managed": {
      "command": "npx",
      "args": [
        "-y",
        "@dynatrace-oss/dynatrace-managed-mcp-server"
      ],
      "env": {
        "DT_ENVIRONMENT_CONFIGS": "<YOUR_DT_ENVIRONMENT_CONFIGS>"
      }
    }
  }
}
  1. Refresh the MCP server list in Cascade. Replace the placeholders with your own values.

Devin Desktop is the new name for Windsurf.

Codex

codex mcp add dynatrace-managed --env "DT_ENVIRONMENT_CONFIGS=<YOUR_DT_ENVIRONMENT_CONFIGS>" -- npx -y @dynatrace-oss/dynatrace-managed-mcp-server

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.dynatrace-managed]
command = "npx"
args = ["-y", "@dynatrace-oss/dynatrace-managed-mcp-server"]
env = { DT_ENVIRONMENT_CONFIGS = "<YOUR_DT_ENVIRONMENT_CONFIGS>" }

Needs Node.js on your computer. Replace the placeholders with your own values.

Gemini CLI

gemini mcp add -e "DT_ENVIRONMENT_CONFIGS=<YOUR_DT_ENVIRONMENT_CONFIGS>" dynatrace-managed npx -- -y @dynatrace-oss/dynatrace-managed-mcp-server

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients that start local servers accept this shape:

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

Zed puts servers under context_servers in its settings, with the same command, args and env fields.

Needs Node.js on your computer. Replace the placeholders with your own values.

listing.faq

Can I paste mcp.tc/i/dynatrace-managed into my MCP client?

No. Dynatrace Managed runs on your own computer, started by your client, so it has no web address to connect to. The quick link is the page to share; the install command is npx -y @dynatrace-oss/dynatrace-managed-mcp-server.

Does Dynatrace Managed need an API key?

No. It reads DT_ENVIRONMENT_CONFIGS from its environment; the setup steps show where to set it.

Is Dynatrace Managed a remote or a local server?

Local. Your client starts it as a process on your computer with npx -y @dynatrace-oss/dynatrace-managed-mcp-server, which needs Node.js.

What can Dynatrace Managed do?

You can list and get problem details from monitored services, list and get security problems and vulnerabilities and look up monitored entities and their relationships.

Which clients can use it?

Any client that starts local servers: Claude Code, Claude Desktop, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. claude.ai and ChatGPT only connect to remote servers.

Who wrote this page?

mcp.tc's robot read Dynatrace Managed's public metadata (its package and repository pages), and an AI model drafted the text from it. A person reviews anything the checks can't confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

listing.em.h

listing.em.lead_local listing.em.how

listing.em.badge

em.prev_lightem.prev_dark
Markdown
[![Dynatrace Managed on mcp.tc](https://mcp.tc/i/dynatrace-managed/badge.svg)](https://mcp.tc/i/dynatrace-managed)
HTML
<a href="https://mcp.tc/i/dynatrace-managed"><img src="https://mcp.tc/i/dynatrace-managed/badge.svg" alt="Dynatrace Managed on mcp.tc" height="20"></a>

listing.em.badge_note

listing.em.widget

HTML
<script src="https://mcp.tc/w/dynatrace-managed.js" async></script>

listing.em.widget_note

iframe

HTML
<iframe src="https://mcp.tc/embed/dynatrace-managed" title="Dynatrace Managed on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

listing.em.iframe_note

JSON

listing.em.json_local

https://mcp.tc/i/dynatrace-managed.json

listing.em.fields

listing.related

listing.more_in

  • AWS CloudWatchvf.sr

    Amazon Web Services

    state.local.label (state.local.title)

    Troubleshoot AWS services with CloudWatch metrics, alarms, PromQL and Logs Insights queries.

    mcp.tc/i/aws-cloudwatch

  • openstatus

    Observability & Incidents

    state.auth.label (state.auth.title)

    Manage monitors, status pages, incidents and maintenances in your openstatus workspace from an AI assistant.

    mcp.tc/i/openstatus

  • Better Stack

    Observability & Incidents

    state.auth.label (state.auth.title)

    Query Better Stack incidents, uptime monitors, on-call schedules and telemetry data such as logs, metrics and traces from your AI assistant.

    mcp.tc/i/better-stack

  • Braintrust

    Observability & Incidents

    state.auth.label (state.auth.title)

    Query Braintrust experiments, datasets, prompts and production logs, author scorers, run evals and search the docs from your assistant.

    mcp.tc/i/braintrust

  • Langfuse

    Observability & Incidents

    state.key.label (state.key.title)

    Work with Langfuse prompts, observations, datasets, scores, evaluators and dashboards for LLM apps from your AI assistant.

    mcp.tc/i/langfuse

  • Cloudflare Logpushvf.sr

    Cloudflare

    state.auth.label (state.auth.title)

    Check the health of Cloudflare Logpush jobs and find failing or erroring jobs across your accounts.

    mcp.tc/i/cloudflare-logpush

listing.disclaimer_checked