Dynatrace Managed

The localDynatrace Managed MCP serverallows AI Assistants to interact with one or more self-hostedDynatrace Manageddeployments, bringing observability data directly into your AI-assisted workflow.

[!TIP] This MCP server is specifically designed for Dynatrace Managed (self-hosted) deployments. For Dynatrace SaaS environments, please use theDynatrace MCP.

[!NOTE] This open source product is supported by the community. For feature requests, questions, or assistance, please useGitHub Issues.

You can add this MCP server to your AI Assistant, such as VSCode, Claude, Cursor, Kiro, Windsurf, ChatGPT, or Github Copilot. For more details, please refer to theconfiguration section below.

# Production environment - dynatraceUrl: https://my-dashboard.company.com/ apiEndpointUrl: https://my-api.company.com/ environmentId: abc-123 alias: production # Token is injected from an environment variable at runtime apiToken: ${DT_PROD_TOKEN} httpProxyUrl: http://proxy.company.com:8080 # Staging environment - dynatraceUrl: https://staging-dashboard.company.com/ apiEndpointUrl: https://staging-api.company.com/ environmentId: xyz-789 alias: staging apiToken: ${DT_STAGING_TOKEN}

[ { "dynatraceUrl": "https://my-dashboard.company.com/", "apiEndpointUrl": "https://my-api.company.com/", "environmentId": "abc-123", "alias": "production", "apiToken": "${DT_PROD_TOKEN}", "httpProxyUrl": "http://proxy.company.com:8080" } ]

Usage in MCP configuration (e.g.,claude_desktop_config.json):

Option A: Using npx (Recommended - no installation required)

{ "mcpServers": { "dynatrace-managed": { "command": "npx", "args": ["-y", "@dynatrace-oss/dynatrace-managed-mcp-server@latest"], "env": { "DT_CONFIG_FILE": "./dt-config.yaml", "DT_PROD_TOKEN": "dt0c01.ABC123...", "DT_STAGING_TOKEN": "dt0c01.XYZ789...", "LOG_LEVEL": "info" } } } }

Option B: Local development (requires cloning the repository)

{ "mcpServers": { "dynatrace-managed": { "command": "node", "args": ["./dist/index.js"], "env": { "DT_CONFIG_FILE": "./dt-config.yaml", "DT_PROD_TOKEN": "dt0c01.ABC123...", "DT_STAGING_TOKEN": "dt0c01.XYZ789...", "LOG_LEVEL": "info" } } } }

Note:Option B requires cloning this repository and runningnpm install && npm run buildfirst.

Security Best Practice:Use environment variable interpolation (${TOKEN_NAME}) in your config files so you can commit them to version control without exposing secrets!

Seeexamples/dt-config.yamlandexamples/dt-config.jsonfor complete examples.

DT_ENVIRONMENT_CONFIGS='[{"apiEndpointUrl":"https://api.example.com/","environmentId":"abc-123","alias":"production","apiToken":"dt0c01.ABC123"}]'

- ✅ Kubernetes ConfigMaps/Secrets
- ✅ Docker containers
- ✅ CI/CD pipelines
- ⚠️ Not ideal for local development (quote escaping is cumbersome)

While you can use a.envfile, multiline values don't work reliably.Use Method 1 (config file) insteadfor cleaner local development.

If multiple configuration methods are set, the MCP server uses this priority:
- DT_CONFIG_FILE- External file (highest priority)
- DT_ENVIRONMENT_CONFIGS- JSON string
- Error- If neither is set

You need to configure the connection to your Dynatrace Managed environment(s). Each environment requires:

[ { "dynatraceUrl": "https://my-dashboard-endpoint.com/", "apiEndpointUrl": "https://my-api-endpoint.com/", "environmentId": "my-env-id-1", "alias": "alias-env", "apiToken": "my-api-token", "httpProxyUrl": "", "httpsProxyUrl": "" } ]

- dynatraceUrl: base URL for Dynatrace Managed dashboard, to which the environment ID will be appended (e.g.https://dmz123.dynatrace-managed.com). If not specified, will default to use the same value asDT_API_ENDPOINT_URL.
- apiEndpointUrl: base URL for Dynatrace Managed API, to which the environment ID will be appended (e.g.https://abc123.dynatrace-managed.com:9999)
- environmentId: ID of the managed environment, used for constructing URL for API and dashboards (e.g., of the form01234567-89ab-cdef-abcd-ef0123456789)
- alias: a friendly/human-readable name for the environment
- apiToken: API token with required scopes (seeAuthentication)
- (optional)httpProxyUrl/httpsProxyUrl: URL of proxy server for requests (seeEnvironment Variables)

If you are using multiple environments, we strongly recommend that you set up rules (seeRules) to guide your LLM in better understanding each environment.

Once configured, you can start usingexample promptslikeGet all details of the Dynatrace entity 'my-service'orWhat problems has Dynatrace identified? Give details of the first problem..

X-Dynatrace-Tokens: prod=dt0c01.AAA;staging=dt0c01.BBB

Environment config in HTTP mode does not includeapiToken— onlyalias+ URLs, which are non-secret. Seeexamples/dt-config-http.yamlandexamples/mcp-config-http.json.

node --max-http-header-size=65536 ./dist/index.js --http

- Problems- List and getproblemdetails from your services (for example Kubernetes)
- Security- List and get security problems /vulnerabilitydetails
- Entities- Get more information about a monitored entity, including relationship mappings
- SLO- List and get Service Level Objective details, including evaluation and error budgets
- Event Tracking- List and get system events
- Log Investigation- Search and filter logs with advanced content and time-based queries
- Metrics Analysis- Query and analyze performance metrics using V2 Metrics API

{ "servers": { "npx-dynatrace-managed-mcp": { "command": "npx", "cwd": "${workspaceFolder}", "args": ["-y", "@dynatrace-oss/dynatrace-managed-mcp-server@latest"], "envFile": "${workspaceFolder}/.env" } } }

Please note: In this config,the${workspaceFolder}variableis used. This only works if the config is stored in the current workspace, e.g.,<your-repo>/.vscode/mcp.json. Alternatively, this can also be stored in user settings, and you can defineenvas follows:

{ "servers": { "npx-dynatrace-managed-mcp": { "command": "npx", "args": ["-y", "@dynatrace-oss/dynatrace-managed-mcp-server@latest"], "env": { "DT_ENVIRONMENT_CONFIGS": "[{\"dynatraceUrl\":\"https://my-dashboard-endpoint.com/\",\"apiEndpointUrl\":\"https://my-api-endpoint.com/\",\"environmentId\":\"my-env-id-1\",\"alias\":\"alias-env\",\"apiToken\":\"my-api-token\"},{\"dynatraceUrl\":\"https://my-dashboard2-endpoint.com/\",\"apiEndpointUrl\":\"https://my-api2-endpoint.com/\",\"environmentId\":\"my-env-id-2\",\"alias\":\"alias-env-2\",\"apiToken\":\"my-api-token-2\"}]" } } } }

{ "mcpServers": { "dynatrace-managed-mcp": { "command": "npx", "args": ["-y", "@dynatrace-oss/dynatrace-managed-mcp-server@latest"], "env": { "DT_ENVIRONMENT_CONFIGS": "[{\"dynatraceUrl\":\"https://my-dashboard-endpoint.com/\",\"apiEndpointUrl\":\"https://my-api-endpoint.com/\",\"environmentId\":\"my-env-id-1\",\"alias\":\"alias-env\",\"apiToken\":\"my-api-token\"},{\"dynatraceUrl\":\"https://my-dashboard2-endpoint.com/\",\"apiEndpointUrl\":\"https://my-api2-endpoint.com/\",\"environmentId\":\"my-env-id-2\",\"alias\":\"alias-env-2\",\"apiToken\":\"my-api-token-2\"}]" } } } }

Amazon Kirois an agentic IDE, andKiro CLIprovides an interactive chat experience directly in your terminal.

{ "mcpServers": { "dynatrace-managed-mcp": { "command": "npx", "args": ["-y", "@dynatrace-oss/dynatrace-managed-mcp-server@latest"], "env": { "DT_ENVIRONMENT_CONFIGS": "[{\"dynatraceUrl\":\"https://my-dashboard-endpoint.com/\",\"apiEndpointUrl\":\"https://my-api-endpoint.com/\",\"environmentId\":\"my-env-id-1\",\"alias\":\"alias-env\",\"apiToken\":\"my-api-token\"},{\"dynatraceUrl\":\"https://my-dashboard2-endpoint.com/\",\"apiEndpointUrl\":\"https://my-api2-endpoint.com/\",\"environmentId\":\"my-env-id-2\",\"alias\":\"alias-env-2\",\"apiToken\":\"my-api-token-2\"}]" } } } }

This configuration should be stored in<project-root>/.kiro/settings/mcp.json, or in user-level settings (~/.kiro/settings/mcp.json).

TheGoogle Gemini CLIis Google's official command-line AI assistant that supports integration with MCP servers. You can add the Dynatrace MCP server using either the built-in management commands or manual configuration.

gemini extensions install https://github.com/dynatrace-oss/dynatrace-managed-mcp export DT_ENVIRONMENT_CONFIGS="[{\"dynatraceUrl\":\"https://my-dashboard-endpoint.com/\",\"apiEndpointUrl\":\"https://my-api-endpoint.com/\",\"environmentId\":\"my-env-id-1\",\"alias\":\"alias-env\",\"apiToken\":\"my-api-token\"},{\"dynatraceUrl\":\"https://my-dashboard2-endpoint.com/\",\"apiEndpointUrl\":\"https://my-api2-endpoint.com/\",\"environmentId\":\"my-env-id-2\",\"alias\":\"alias-env-2\",\"apiToken\":\"my-api-token-2\"}]"

and verify that the server is running via

Or manually in your~/.gemini/settings.jsonor.gemini/settings.json:

{ "mcpServers": { "dynatrace-managed-mcp": { "command": "npx", "args": ["@dynatrace-oss/dynatrace-managed-mcp-server@latest"], "env": { "DT_ENVIRONMENT_CONFIGS": "[{\"dynatraceUrl\":\"https://my-dashboard-endpoint.com/\",\"apiEndpointUrl\":\"https://my-api-endpoint.com/\",\"environmentId\":\"my-env-id-1\",\"alias\":\"alias-env\",\"apiToken\":\"my-api-token\"},{\"dynatraceUrl\":\"https://my-dashboard2-endpoint.com/\",\"apiEndpointUrl\":\"https://my-api2-endpoint.com/\",\"environmentId\":\"my-env-id-2\",\"alias\":\"alias-env-2\",\"apiToken\":\"my-api-token-2\"}]" }, "timeout": 30000, "trust": false } } }

The default mode for this local MCP uses stdio for transport.

For scenarios where you need to run the MCP server as an HTTP service instead, you can use the HTTP server mode (e.g., for stateful sessions, load balancing, or integration with web clients):

# Get help and see all available options npx -y @dynatrace-oss/dynatrace-managed-mcp-server@latest --help # Run with HTTP server on default port 3000 npx -y @dynatrace-oss/dynatrace-managed-mcp-server@latest --http # Run with custom port npx -y @dynatrace-oss/dynatrace-managed-mcp-server@latest --http --port 3001 # Run with custom host/IP npx -y @dynatrace-oss/dynatrace-mcp-server@latest --http --host 127.0.0.1 # recommended for local computers npx -y @dynatrace-oss/dynatrace-mcp-server@latest --http --host 0.0.0.0 # recommended for container npx -y @dynatrace-oss/dynatrace-mcp-server@latest --http --host 192.168.0.1 # recommended when sharing connection over a local network # Check version npx -y @dynatrace-oss/dynatrace-managed-mcp-server@latest --version

Configuration for MCP clients that support HTTP transport:

{ "mcpServers": { "dynatrace-managed-mcp": { "url": "http://localhost:3000", "transport": "http" } } }

For efficient result retrieval from Dynatrace, please consider creating a rule file (e.g.,.github/copilot-instructions.md,.amazonq/rules/), instructing coding agents on how to get more details for your component/app/service.

Here is an example for someone responsible for theeasytradesystem, who wants to focus on entities and problems related to easytrade.

# Dynatrace We use Dynatrace Managed as our Observability solution. This document provides instructions for retrieving data for the EasyTrade system from Dynatrace using the Dynatrace Managed MCP. ## Best Practices 1. Always use specific time ranges, keeping these narrow (e.g. now-1h, now-24h), to avoid large data queries. 2. For entity selectors, consider using criteria for tags for more precise filtering (if the tagging strategy and naming are understood). ## Entity Selectors for easytrade Consider using these criteria in the entitySelector to filter data for our easytrade application: Services: - type(SERVICE),entityName.contains("easytrade") - type(SERVICE),tag("app:easytrade") Process Groups & Containers: - type(PROCESS_GROUP),entityName.contains("easytrade") - type(CONTAINER_GROUP_INSTANCE),entityName.contains("easytrade") Hosts: - type(HOST),tag("environment:production"),tag("app:easytrade") AWS Lambda Functions: - type(AWS_LAMBDA_FUNCTION),entityName.contains("easytrade") - type(AWS_LAMBDA_FUNCTION),tag("AWS_REGION:us-west-2"),tag("app:easytrade")`

DT_ENVIRONMENT_CONFIGS`(optional): JSON string with environment configurations.Useful for Kubernetes/Docker.