Dynatrace Managed MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_FILE | No | Log file path, used when LOG_OUTPUT includes 'file' | dynatrace-managed-mcp.log |
| LOG_LEVEL | No | Log verbosity: debug, info, warn or error | info |
| LOG_OUTPUT | No | Log destination: file, stderr, stderr-all, file+stderr, disabled. Use stderr-all for stdio transport; never stdout/console, which is reserved for the MCP protocol. | file+stderr |
| DT_CONFIG_FILE | No | Alternative to DT_ENVIRONMENT_CONFIGS: path to a JSON or YAML config file (supports ${VAR} interpolation). Takes priority over DT_ENVIRONMENT_CONFIGS when both are set. Rarely usable in hosted deployments. | |
| DT_ENVIRONMENT_CONFIGS | Yes | JSON array of Dynatrace Managed environments. Each entry requires apiEndpointUrl, environmentId, alias and apiToken; dynatraceUrl, httpProxyUrl and httpsProxyUrl are optional. Example: [{"apiEndpointUrl":"https://abc123.dynatrace-managed.com:9999/","environmentId":"01234567-89ab-cdef-abcd-ef0123456789","alias":"production","apiToken":"dt0c01...."}]. The API token needs scopes: auditLogs.read, entities.read, events.read, logs.read, metrics.read, networkZones.read, problems.read, securityProblems.read, slo.read | |
| DT_MCP_DISABLE_TELEMETRY | No | Set to "true" to disable Dynatrace usage telemetry | false |
| DT_MCP_TELEMETRY_DEVICE_ID | No | Device identifier for telemetry (auto-generated by default) | |
| DT_MCP_RATE_LIMIT_MAX_CALLS | No | Maximum tool calls allowed per rate-limit window | 20 |
| DT_MCP_RATE_LIMIT_WINDOW_MS | No | Rate-limit window size in milliseconds | 20000 |
| DT_MCP_TELEMETRY_ENDPOINT_URL | No | OpenKit endpoint URL for telemetry (advanced) | |
| DT_MCP_TELEMETRY_APPLICATION_ID | No | OpenKit application ID for telemetry (advanced) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dynatrace_managed_get_environments_infoA | Get information about all connected Dynatrace Managed clusters and verify the connections and authentication services. |
| dynatrace_managed_list_available_metricsA | List available metrics in the Managed cluster, optionally filtered by entity. Results include aggregation types, dimension definitions, and technical metadata for advanced metric analysis. |
| dynatrace_managed_query_metrics_dataA | Query metric data for a specific time range and metric selector. Must limit the amount of data being retrieved: must use a specific entitySelector, such as using specific entityIds; must use a narrow timerange (with from and to); must use a resolution in line with the timerange, for example if getting data covering several days then the resolution should be hours rather than minutes. |
| dynatrace_managed_get_metric_detailsC | Get detailed information about a specific metric. |
| dynatrace_managed_query_logsA | Search logs using simple text queries. Results include event types, expanded metadata fields (up to 8 fields), and enhanced error detection. Managed clusters support basic text search but not structured syntax like "content:" or "loglevel:". |
| dynatrace_managed_list_eventsB | List events from the Managed cluster within a specified timeframe. Results include event properties, management zones, severity/impact levels, and detailed metadata for comprehensive analysis. |
| dynatrace_managed_get_event_detailsB | Get detailed information about a specific event. |
| dynatrace_managed_list_entity_typesA | List all available entity types in the Managed cluster to understand what types of entities can be monitored. |
| dynatrace_managed_get_entity_type_detailsB | Get details of an entity type. |
| dynatrace_managed_discover_entitiesA | Discover entities in the Managed cluster using EntitySelector syntax. REQUIRED: Must specify entitySelector with exactly ONE entity type only. Results include entity properties, tags, management zones, and relationship counts for comprehensive topology analysis. |
| dynatrace_managed_get_entity_detailsB | Get detailed information about a specific entity. |
| dynatrace_managed_get_entity_relationshipsA | Get relationships that a specific entity has "to" and "from" other entities. |
| dynatrace_managed_list_problemsB | List problems from the Managed cluster with optional filtering. |
| dynatrace_managed_get_problem_detailsA | Get detailed information about a specific problem including evidence details for root cause analysis, affected entities, entity tags, and management zones. Use the problemId (UUID format) from list_problems output, NOT the displayId. |
| dynatrace_managed_list_security_problemsA | List security problems and vulnerabilities from the Managed cluster. Results include package names, technology details, vulnerable components, and comprehensive risk assessment data. |
| dynatrace_managed_get_security_problem_detailsA | Get detailed information about a specific security problem including CVE details, affected entities, vulnerable components, code locations, and comprehensive technical analysis. |
| dynatrace_managed_list_slosA | List Service Level Objectives (SLOs) from the Managed cluster. Results include timeframe details, management zones, error budget burn rates, and comprehensive SLO configuration data. IMPORTANT: When evaluate=true, the query must be limited to 25 or fewer results using the limit parameter. |
| dynatrace_managed_get_slo_detailsA | Get detailed information about a specific SLO. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/dynatrace-oss/dynatrace-managed-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server