MCP server for Dynatrace Managed to access logs, events, and metrics.
Dynatrace MCP server exists for a simple reason — assistants are far more useful when they can act on Dynatrace directly instead of describing what you should do. MCP server for Dynatrace Managed to access logs, events, and metrics.
The local Dynatrace Managed MCP server allows AI Assistants to interact with one or more self-hosted Dynatrace Managed deployments, bringing observability data directly into your AI-assisted workflow.
Once Dynatrace is connected, these are the calls the assistant has available:
dynatraceUrl — https://my-dashboard.company.com/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 form 01234567-89ab-cdef-abcd-ef0123456789)alias — a friendly/human-readable name for the environmentapiToken — API token with required scopes (see Authentication)Real — time observability** - Fetch production-level data for early detection and proactive monitoringProblems — List and get problem details from your services (for example Kubernetes)Security — List and get security problems / vulnerability detailsEntities — Get more information about a monitored entity, including relationship mappingsSLO — List and get Service Level Objective details, including evaluation and error budgetsExample — DT_CONFIG_FILE=./dt-config.yamlfile — Write logs to a file (default behavior)Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
You will need 6 environment variables: DT_CONFIG_FILE, DT_PROD_TOKEN, DT_STAGING_TOKEN, LOG_LEVEL, DT_ENVIRONMENT_CONFIGS, DT_API_ENDPOINT_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Dynatrace's toolset — dynatraceUrl, apiEndpointUrl, environmentId and 11 more — is a fair guide to whether it matches your workflow. It is maintained by dynatrace-oss; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Dynatrace's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| dynatraceUrl | https://my-dashboard.company.com/ |
| 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 form 01234567-89ab-cdef-abcd-ef0123456789) |
| alias | a friendly/human-readable name for the environment |
| apiToken | API token with required scopes (see [Authentication](#authentication)) |
| Real | time observability** - Fetch production-level data for early detection and proactive monitoring |
| Problems | List and get [problem](https://www.dynatrace.com/hub/detail/problems/) details from your services (for example Kubernetes) |
| Security | List and get security problems / [vulnerability](https://www.dynatrace.com/hub/detail/vulnerabilities/) details |
| Entities | Get more information about a monitored entity, including relationship mappings |
| SLO | List and get Service Level Objective details, including evaluation and error budgets |
| Example | DT_CONFIG_FILE=./dt-config.yaml |
| file | Write logs to a file (default behavior) |
| stderr | Write errors and warnings to standard error (info/debug suppressed) |
| stderr-all | Write all log levels to standard error (✅ **Recommended for VS Code with stdio transport**) |
{
"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"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| DT_CONFIG_FILE | Configuration value read at startup. | Optional |
| DT_PROD_TOKEN | Credential the server authenticates with. | Yes |
| DT_STAGING_TOKEN | Credential the server authenticates with. | Yes |
| LOG_LEVEL | Configuration value read at startup. | Optional |
| DT_ENVIRONMENT_CONFIGS | Configuration value read at startup. | Optional |
| DT_API_ENDPOINT_URL | Endpoint or connection string the server talks to. | Yes |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.