Dynatrace Managed Mcp

Name: Dynatrace Managed Mcp
Author: dynatrace-oss

by dynatrace-osscommunityv0.5.3

The Dynatrace Managed MCP server allows AI Assistants to interact with self-hosted Dynatrace Managed deployments, providing observability data for AI-assisted workflows. It supports both local and remote modes for flexible deployment options.

From the registry: MCP server for Dynatrace Managed to access logs, events, and metrics.

GitHub Repository

Dynatrace Managed MCP Server Stars on GitHub

Dynatrace Managed MCP Server Contributors on GitHub

Install & configure

Prerequisites

required
Create Dynatrace Managed API token
In your Dynatrace Managed environment, create an API token with the scopes required by the MCP tools (see project docs).
https://www.dynatrace.com/support/help/shortlink/token
required
Write a dt-config.yaml
Create a Dynatrace environment config file that uses ${TOKEN_NAME} interpolation so it can be committed without secrets.

Install in your client

Paste into the AI you're chatting with — it will figure out the rest

Please install the `dynatrace-managed-mcp` MCP server into my current AI client (that's you).

Required prerequisites (do these first if not already done):
- **Create Dynatrace Managed API token** — In your Dynatrace Managed environment, create an API token with the scopes required by the MCP tools (see project docs). (https://www.dynatrace.com/support/help/shortlink/token)
- **Write a dt-config.yaml** — Create a Dynatrace environment config file that uses ${TOKEN_NAME} interpolation so it can be committed without secrets.

Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["-y","@dynatrace-oss/dynatrace-managed-mcp-server@latest"]
- optional environment variables:
  - `DT_CONFIG_FILE`: Path to a YAML/JSON config file listing your Dynatrace Managed environments. (example: `./dt-config.yaml`)
  - `DT_ENVIRONMENT_CONFIGS`: Alternative to DT_CONFIG_FILE — a JSON string describing environments. (example: `<your-dt-environment-configs-json>`)
  - `LOG_LEVEL`: Log level (default info). (example: `info`)

Note: Dynatrace Managed (self-hosted) MCP server. For Dynatrace SaaS use the separate dynatrace-mcp package. Tokens are typically injected via ${TOKEN_NAME} interpolation inside the config file.

Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.

Note: Dynatrace Managed (self-hosted) MCP server. For Dynatrace SaaS use the separate dynatrace-mcp package. Tokens are typically injected via ${TOKEN_NAME} interpolation inside the config file.