Dynatrace Managed MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Log level, writing to dynatrace-managed-mcp.log in the current working directory (e.g. debug, info, warning, error) | |
| HTTP_PROXY | No | HTTP Proxy for corporate environments, to route traffic through (e.g. http://proxy.company.com:8080) | |
| HTTPS_PROXY | No | HTTPS Proxy for corporate environments, to route traffic through (e.g. https://proxy.company.com:8080) | |
| DT_DYNATRACE_URL | No | 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 as DT_API_ENDPOINT_URL. | |
| DT_API_ENDPOINT_URL | Yes | Base url for Dynatrace Managed API, to which the environment id will be appended (e.g. https://abc123.dynatrace-managed.com:9999) | |
| DT_MANAGED_API_TOKEN | Yes | API token with required scopes: auditLogs.read, entities.read, events.read, logs.read, metrics.read, networkZones.read, problems.read, securityProblems.read, slo.read | |
| DT_MANAGED_ENVIRONMENT | Yes | ID of the managed environment, used for constructing URL for API and dashboards (e.g. of the form 01234567-89ab-cdef-abcd-ef0123456789) | |
| DT_MCP_DISABLE_TELEMETRY | No | Disable Telemetry data collection | false |
| DT_MCP_TELEMETRY_DEVICE_ID | No | Device identifier for tracking (auto-generated by default) | |
| DT_MCP_TELEMETRY_ENDPOINT_URL | No | OpenKit endpoint URL for telemetry | |
| DT_MCP_TELEMETRY_APPLICATION_ID | No | Application ID for telemetry tracking | dynatrace-managed-mcp |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
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