Dynatrace Managed MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 602 installs a week from npm. Last commit 15 Sep 2026.
MCP server for Dynatrace Managed to access logs, events, and metrics.
We read the source, 19 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
COPY --from=build --chown=node:node /app/package.json /app/package-lock.json /app/.npmrc /app/
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add dynatrace-managed-mcp -- npx -y @dynatrace-oss/dynatrace-managed-mcp-server
{
"mcpServers": {
"dynatrace-managed-mcp": {
"args": [
"-y",
"@dynatrace-oss/dynatrace-managed-mcp-server"
],
"command": "npx"
}
}
}
[mcp_servers.dynatrace-managed-mcp]
command = "npx"
args = ["-y", "@dynatrace-oss/dynatrace-managed-mcp-server"]
{
"mcpServers": {
"dynatrace-managed-mcp": {
"args": [
"-y",
"@dynatrace-oss/dynatrace-managed-mcp-server"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"dynatrace-managed-mcp": {
"args": [
"-y",
"@dynatrace-oss/dynatrace-managed-mcp-server"
],
"command": "npx"
}
}
}
This one needs environment variables set before it will start:
DT_MCP_RATE_LIMIT_MAX_CALLS (Maximum number of tool calls allowed per rate limit window. Defaults to 20.), DT_MCP_RATE_LIMIT_WINDOW_MS (Rate limit window size in milliseconds. Defaults to 20000 (20 seconds).), DT_ENVIRONMENT_CONFIGS (An escaped JSON array that defines the Dynatrace Managed environment(s) to connect to. See README file for contents of this.), LOG_LEVEL (Logging level (e.g. debug, info, warning, error)), DT_MCP_DISABLE_TELEMETRY (Disable telemetry).
The author declared them in the registry entry; get the values from the project itself.
SigNoz MCP server: access metrics, traces, logs, alerts, and dashboards via AI assistants
Access New Relic observability data through MCP - query metrics, logs, traces, entities, and more
Monitor infrastructure, manage agents and deployments, track metrics, logs, and events
Read-only Kubernetes MCP server: inspect resources, logs, events, and metrics. Secrets are masked.
Full MCP server for MT5: access trades, logs, compilation, etc..
MCP server providing Prometheus metrics access and PromQL query execution for AI assistants
MCP server for managing Fly.io machines, apps, logs, and Docker images.
MCP server for Cronometer — food logs, macros, fasting, biometrics, and recurring foods
Answers built from our own checks of this server.