dynatrace-managed

dynatrace-managed is an MCP server for Claude Code from dynatrace-oss/dynatrace-managed-mcp. Its token cost is not measured, scanned A, original, Apache-2.0.

An MCP server for Dynatrace Managed, a self-hosted system for monitoring applications and infrastructure. It runs locally and needs three environment variables for its configuration.

In plain words
What is it for?
It is for projects that need to connect a coding agent to a self-hosted Dynatrace environment.
Why use it?
It provides a local connection to an existing Dynatrace Managed installation without describing any additional features beyond that connection.

MCP server for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: listed in a Claude config.

Part of the dynatrace-managed-mcp plugin — 1 skill, 1 command, 2 MCP servers shipped together

Good fit It is for projects that need to connect a coding agent to a self-hosted Dynatrace environment.

Compare 6 mcp servers from other repositories ↓
Install with agentmods
npx agentmods add mcp/dynatrace-oss/dynatrace-managed-mcp/dynatrace-managed
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/dynatrace-oss/dynatrace-managed-mcp

Made for: Claude Code.

Or install dynatrace-managed-mcp, the plugin that ships this one along with the rest of its 1 skill, 1 command, 2 MCP servers.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for dynatrace-managed

README.md
[![agentmods](https://agentmods.dev/badge/mcp/dynatrace-oss/dynatrace-managed-mcp/dynatrace-managed/github.svg)](https://agentmods.dev/mcp/dynatrace-oss/dynatrace-managed-mcp/dynatrace-managed)
Your own site
<a href="https://agentmods.dev/mcp/dynatrace-oss/dynatrace-managed-mcp/dynatrace-managed"><img src="https://agentmods.dev/badge/mcp/dynatrace-oss/dynatrace-managed-mcp/dynatrace-managed/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for dynatrace-managed

Your own site · 80×15
<a href="https://agentmods.dev/mcp/dynatrace-oss/dynatrace-managed-mcp/dynatrace-managed"><img src="https://agentmods.dev/badge/mcp/dynatrace-oss/dynatrace-managed-mcp/dynatrace-managed.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

dynatrace-managed scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.mcp.json · 15 lines

What it actually says

{
  "dynatrace-managed": {
    "type": "stdio",
    "command": "npx",
    "args": [
      "-y",
      "@dynatrace-oss/dynatrace-managed-mcp-server@<2"
    ],
    "env": {
      "DT_ENVIRONMENT_CONFIGS": "${user_config.dt_environment_configs}",
      "DT_CONFIG_FILE": "${user_config.dt_config_file}",
      "LOG_LEVEL": "${user_config.log_level}"
    }
  }
}
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 15 lines scan A ee8a320a1538

Subscribe to this mod's changes

dynatrace-managed is an MCP server published in the GitHub repository dynatrace-oss/dynatrace-managed-mcp (28 stars, last pushed today), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-10.