Dynatrace Managed MCP Server

MCP安全风控

提供方 dynatrace-oss

安全风控 HTTP · 远程 Token 社区 / 第三方
查看接入方式

Enables AI assistants to interact with self-hosted Dynatrace Managed environments to retrieve observability data, security insights, and performance metrics. It allows users to query problems, logs, events, and SLOs through natural language interfaces in both local and remote modes.

一句话选型结论

按资料字段整理

Dynatrace Managed MCP Server 属于安全风控类 MCP 服务器,HTTP · 远程,Token,有可直接复制的远程端点配置。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类安全风控 传输方式HTTP · 远程 鉴权Token 部署方式远程部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

安全风控
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

安装与配置

HTTP · 远程 Token
连远程 HTTPS 端点,通常为 Streamable HTTP
npx @dynatrace-oss/dynatrace-managed-mcp-server@latest

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
资产与漏洞排查

盘点资产、扫漏洞、看暴露面。

日志与审计

汇总日志、查异常行为。

合规检查

按规则检查配置与权限是否合规。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 使用前要准备好Token对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在安全风控场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Dynatrace Managed MCP Server当前 未标注 HTTP · 远程 远程部署 有 2026-05-17
Cyber Strike AI 75 未标注 未标注 无 2026-05-17
mcp-for-beginners 未标注 stdio · 本地进程 本地部署 有 2026-04-13
casdoor 未标注 stdio · 本地进程 本地部署 有 2026-04-12
kubeshark 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Modelcontextprotocol C22988b0 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

安全风控
字段来自项目仓库与公开索引,中文说明由本站标注
提供方dynatrace-oss上游标注的维护方 dynatrace-oss
分类安全风控本站按上游分类展示
连接方式HTTP · 远程连远程 HTTPS 端点,通常为 Streamable HTTP
鉴权方式Token远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Node.js本地安装时用到的包标识与运行时
部署类型远程部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

17.9 KB
来自项目仓库与上游目录的原文,未做删改

Dynatrace Managed MCP Server

Use cases

> 1. Your Dynatrace Managed environment(s) is/are the primary Observability system, containing all live data; or
> 2. There has been a migration from a Dynatrace Managed environment to a Dynatrace Saas environment; however, historical observability data has not been migrated and can still be accessed via a Dynatrace Managed environment.
> The Dynatrace Managed MCP is used to access historical data, and a separate Dynatrace SaaS MCP is used to access live and more recent data.

> Specific use cases for the Dynatrace Managed MCP include:
>
> - Real-time observability - Fetch production-level data for early detection and proactive monitoring
> - Contextual debugging - Fix issues with full context from monitored exceptions, logs, and anomalies
> - Security insights - Get detailed vulnerability analysis and security problem tracking. This can include multicloud compliance assessment with evidence-based investigation.
> - Natural language queries - Queries are mapped to MCP tool usage, and thus API queries, with guidance for the next step
> - Multiphase incident investigation - Systematic impact assessment and troubleshooting
> - Multienvironment support - Query multiple Dynatrace Managed environments from the same MCP server

Capabilities

> - Problems - List and get problem details from your services (for example Kubernetes)
> - Security - List and get security problems / vulnerability 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
> - 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

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.

This MCP server supports two modes:

  • Local mode: Runs on your machine for development and testing.
  • Remote mode: Connects over HTTP/SSE for distributed or production-like setups.

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

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

Quickstart in stdio (local) mode

You can add this MCP server to your AI Assistant, such as VSCode, Claude, Cursor, Kiro, Windsurf, ChatGPT, or GitHub Copilot.

To run this MCP server, you to have to configure four things:

  • Dynatrace Managed API token
  • Configuration file: dt-config.yaml or dt-config.json file which is responsible for defining list of environments you intend to use
  • MCP Server connection configuration file: local mcp configuration, which is dependent on tools you are using
  • Set DT_CONFIG_FILE to the path of your dt-config.yaml or dt-config.json file in the MCP server environment.

Dynatrace Managed API token

For information about creating API tokens in Managed deployments, refer to the Dynatrace Managed documentation.
Your API token must include the following scopes for full functionality:

  • Access problem and event feed, metrics, and topology (DataExport)
  • Read entities (entities.read)
  • Read events (events.read)
  • Read logs (logs.read)
  • Read metrics (metrics.read)
  • Read problems (problems.read)
  • Read security problems (securityProblems.read)
  • Read SLO (slo.read)

Configuration File

Configuration parameters

Parameter Required Description Example value
apiEndpointUrl Yes Base URL for Dynatrace Managed cluster API https://dmz123.dynatrace-managed.com
environmentId Yes ID of the managed environment 01234567-89ab-cdef-abcd-ef0123456789
alias Yes Human-friendly name of the environment MyEnvironment
apiToken Only in stdio mode API token of the cluster with required scopes created using the instruction above dt0s01.ABCDEFGHIJK0123
httpProxyUrl No URL of proxy server for requests. Do not use with the other proxy parameter http://proxy.company.com:8080
httpsProxyUrl No URL of proxy server for requests. Do not use with the other proxy parameter https://proxy.company.com:8080

There are two ways to configure your Dynatrace Managed environments.

Method 1: Configuration File (Recommended for Local Development)

Example: `dt-config.yaml````yaml

Production environment

  • apiEndpointUrl: https://my-api.company.com/
    environmentId: abc-123
    alias: production
    # Token is injected from an environment variable at runtime
    apiToken: ${DT_PROD_TOKEN}
    # You can also use the token directly
    # apiToken: dt0s01.ABCDEFGHIJK0123

Staging environment

  • apiEndpointUrl: https://staging-api.company.com/
    environmentId: xyz-789
    alias: staging
    apiToken: ${DT_STAGING_TOKEN}

Example: `dt-config.json````json
[
  {
    "apiEndpointUrl": "https://my-api.company.com/",
    "environmentId": "abc-123",
    "alias": "production",
    "apiToken": "${DT_PROD_TOKEN}"
  }
]

Method 2: Environment Variable (Docker/Kubernetes)

For Kubernetes deployments or if you prefer environment variables, you can set DT_ENVIRONMENT_CONFIGS with a JSON string in either your .env file or directly in MCP Server connection configuration file```shell
DT_ENVIRONMENT_CONFIGS='[{"apiEndpointUrl":"https://api.example.com/","environmentId":"abc-123","alias":"production","apiToken":"dt0s01.ABCDEFGHIJK0123"}]'


### MCP Server connection configuration file

To actually connect to the MCP server you have to configure your MCP connection in your AI Assistant

We recommend always setting it up for your current workspace instead of using it globally.

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

Alternatively, this can also be stored in user settings, and you can define env as follows:```json
{
"servers": {
"npx-dynatrace-managed-mcp": {
"command": "npx",
"args": ["-y", "@dynatrace-oss/dynatrace-managed-mcp-server@latest"],
"env": {
"DT_PROD_TOKEN": "dt0s01.ABCDEFGHIJK0123",
"DT_CONFIG_FILE": "dt-config.yaml"
}
}
}
}


#### Claude Code

Claude Code can install this server as a plugin, which
skips the manual MCP configuration below and adds a skill covering environment selection and entity
selectors. It is published through Anthropic's community plugin marketplace:```shell
/plugin marketplace add anthropics/claude-plugins-community
/plugin install dynatrace-managed-mcp@claude-community

> [!IMPORTANT]
> The community marketplace listing is pending review. Until it is approved, the install above
> reports Plugin "dynatrace-managed-mcp" not found in marketplace "claude-community" - use the
> instructions under Installing straight from this repository below in the meantime.

Claude Code prompts for the cluster configuration during install - either the JSON array for a
single cluster, or a path to a dt-config.yaml / dt-config.json file for several. See
docs/claude-code-plugin.md for details.

> [!NOTE]
> Third-party marketplaces do not auto-update by default. Run
> /plugin marketplace update claude-community to pick up a new plugin version.

Installing straight from this repository instead

This repository is also a plugin marketplace in its own right, which is how you install the plugin
before the community listing is approved, try an unreleased change, or pin to a specific branch:```shell
/plugin marketplace add dynatrace-oss/dynatrace-managed-mcp
/plugin install dynatrace-managed-mcp@dynatrace


To configure the server by hand instead, use the Claude Desktop snippet below - it applies to Claude
Code's `.mcp.json` as well.

#### Claude Desktop```json
{
  "mcpServers": {
    "dynatrace-managed-mcp": {
      "command": "npx",
      "args": ["-y", "@dynatrace-oss/dynatrace-managed-mcp-server@latest"],
      "env": {
        "DT_PROD_TOKEN": "dt0s01.ABCDEFGHIJK0123",
        "DT_CONFIG_FILE": "dt-config.yaml"
      }
    }
  }
}

Kiro```json

{
"mcpServers": {
"dynatrace-managed-mcp": {
"command": "npx",
"args": ["-y", "@dynatrace-oss/dynatrace-managed-mcp-server@latest"],
"env": {
"DT_PROD_TOKEN": "dt0s01.ABCDEFGHIJK0123",
"DT_CONFIG_FILE": "dt-config.yaml"
}
}
}
}


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

#### Google Gemini CLI

Using `gemini` CLI directly (recommended):```bash
gemini extensions install https://github.com/dynatrace-oss/dynatrace-managed-mcp
export DT_ENVIRONMENT_CONFIGS="[{\"apiEndpointUrl\":\"https://my-api-endpoint.com/\",\"environmentId\":\"my-env-id-1\",\"alias\":\"alias-env\",\"apiToken\":\"my-api-token\"},{\"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```bash
gemini mcp list


Or manually in your `~/.gemini/settings.json` or `.gemini/settings.json`:```json
{
  "mcpServers": {
    "dynatrace-managed-mcp": {
      "command": "npx",
      "args": ["@dynatrace-oss/dynatrace-managed-mcp-server@latest"],
      "env": {
        "DT_ENVIRONMENT_CONFIGS": "[{\"apiEndpointUrl\":\"https://my-api-endpoint.com/\",\"environmentId\":\"my-env-id-1\",\"alias\":\"alias-env\",\"apiToken\":\"my-api-token\"},{\"apiEndpointUrl\":\"https://my-api2-endpoint.com/\",\"environmentId\":\"my-env-id-2\",\"alias\":\"alias-env-2\",\"apiToken\":\"my-api-token-2\"}]",
        "DT_CONFIG_FILE": "dt-config.yaml"
      },
      "timeout": 30000,
      "trust": false
    }
  }
}

HTTP Server Mode (Alternative)

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 load balancing or integration with web clients):

Running as HTTP server

Make sure you have the Configuration File in the same folder. You do not have to define API tokens for configurations ran in HTTP mode.```bash

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


> [!WARNING]
> In HTTP mode the server validates the `Host` header to protect against DNS rebinding attacks. With `--host 0.0.0.0` (or `--host ::`) only **loopback** hostnames are accepted by default, so remote clients receive `403 Forbidden` until you set `DT_MCP_ALLOWED_HOSTS` to the hostnames they use. See DNS Rebinding Protection.

#### MCP Server connection configuration file:

As explained earlier, HTTP mode does not store API tokens in its configuration. Authentication is done by the user by filling the `X-Dynatrace-Tokens` header.```json
{
  "mcpServers": {
    "dynatrace-managed-mcp": {
      "url": "http://localhost:3000",
      "transport": "http",
      "headers": {
        "Content-Type": "application/json",
        "Accept": "application/json,text/event-stream",
        "X-Dynatrace-Tokens": "alias1=token1;alias2=token2"
      }
    }
  }
}

Performance Considerations

Important: This MCP server makes API calls to the Dynatrace Managed environment(s). It is designed for efficient usage (e.g., limiting the response sizes), but care should be taken not to overload the Dynatrace Managed environment(s) with large queries.

Best Practices:

  1. Use specific time ranges (e.g., 1-2 hours) rather than large historical queries.
  2. Use specific filters to limit the scope of queries as much as possible, for example, entity selectors that specify the entity ID.
  3. If using multiple environments, be specific about which one to query, where applicable. If querying multiple at once, be mindful of how much data will be returned to the LLM, e.g. top 10 problems from 2 envs = 20 problems, versus top 10 problems from 10 envs = 100 problems.

DNS Rebinding Protection (HTTP mode)

  • DT_MCP_ALLOWED_HOSTS (optional): Comma-separated list of hostnames the server accepts in the Host header. Ports are ignored, so list hostnames only (use the bracketed form for IPv6, e.g. [::1]).

When this variable is not set, the allowlist is derived from --host: the bound address plus localhost, 127.0.0.1 and [::1]. Requests whose Host header is not on the list are rejected with 403 Forbidden, as are requests carrying an Origin header for a hostname that is not on the list. This is what prevents DNS rebinding attacks.

Validation is always active: there is no configuration in which it is silently skipped.

> [!IMPORTANT]
> When bound to a wildcard address (--host 0.0.0.0 or --host ::), the bound address does not identify which hostnames are legitimate, so the server accepts loopback hostnames only and logs a warning at startup. DNS rebinding is blocked in this mode, but so is every remote client. If you run in a container or expose the server on a network, you must set DT_MCP_ALLOWED_HOSTS to the hostnames your clients use, or they will receive 403 Forbidden.

Example: container bound to all interfaces, reached as mcp.internal.example.com:```bash
DT_MCP_ALLOWED_HOSTS=mcp.internal.example.com node dist/index.js --http --host 0.0.0.0


`DT_MCP_ALLOWED_HOSTS` **replaces** the derived list rather than extending it, so include loopback names explicitly if you also need local access:```bash
DT_MCP_ALLOWED_HOSTS=mcp.internal.example.com,localhost,127.0.0.1

Troubleshooting

Authentication Issues

In most cases, authentication issues stem from missing scopes or invalid tokens. Please ensure that you have added all required scopes as listed above.

When experiencing errors, you can ask the AI Assistant for the exact error returned by the MCP. For startup issues, check the AI Assistant logs.

You can also try running the MCP directly to see if it reports errors on startup:bash npx @dynatrace-oss/dynatrace-managed-mcp-server@latest

Header size limits is too small

The X-Dynatrace-Tokens header grows with the number of environments. Each entry is roughly
alias=dt0s01.ABCDEFGHIJK0123 (~110 characters). Node.js enforces a default HTTP header size limit of
16 KB, which accommodates approximately 140–150 environments before requests are rejected.

If you need more environments, increase the limit at server startup with the --max-http-header-size
flag:```bash
node --max-http-header-size=65536 ./dist/index.js --http


If you are running a **reverse proxy** (such as nginx) in front of the MCP server, the proxy also
enforces its own limit. nginx defaults to 8 KB (`large_client_header_buffers`), which fits roughly
70 environments. Raise it in your nginx configuration:```nginx
large_client_header_buffers 4 32k;

Telemetry

The Dynatrace MCP Server includes sending Telemetry Data via Dynatrace OpenKit to help improve the product. This includes:

  • Server start events
  • Tool usage (which tools are called, success/failure, execution duration)
  • Error tracking for debugging and improvement

Privacy and Opt-out:

  • Telemetry is disabled by default but can be enabled by setting DT_MCP_ENABLE_TELEMETRY=true
  • No sensitive data from your Dynatrace environment is tracked
  • Only anonymous usage statistics and error information are collected
  • Usage statistics and error data is transmitted to Dynatrace’s analytics endpoint

Configuration options:

  • DT_MCP_ENABLE_TELEMETRY (boolean, default: false) - Enable Telemetry
  • DT_MCP_TELEMETRY_APPLICATION_ID (string, default: dynatrace-managed-mcp) - Application ID for tracking
  • DT_MCP_TELEMETRY_ENDPOINT_URL (string, default: Dynatrace endpoint) - OpenKit endpoint URL
  • DT_MCP_TELEMETRY_DEVICE_ID (string, default: auto-generated) - Device identifier for tracking

Additional documentation

MCP Server usage

  • API token scopes - table containing information about available tools, endpoints they are calling and required API token scopes to properly access them
  • Architecture - detailed diagrams representing architecture of Dynatrace environment while using MCP server in either stdio or http mode
  • Environment variables - detailed information about available environment variables
  • Rule file - determine rules for your AI Assistant to ensure smooth usage of the Managed cluster

Development

  • Changelog format - instruction for developers on how to write consistent and structured changelogs
  • Development - general information about running the project and its contents

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Dynatrace Managed MCP Server 怎么安装?

在客户端按下面的安装命令接入:npx @dynatrace-oss/dynatrace-managed-mcp-server@latest。装完在客户端配置里引用同一个包或端点。

Dynatrace Managed MCP Server 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

Dynatrace Managed MCP Server 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Dynatrace Managed MCP Server 需要 API Key 吗?

资料标注需要Token认证,使用前准备好对应凭据,并按最小权限配置。

Dynatrace Managed MCP Server 能提供哪些能力?

资料显示能力标签包括 可观测性、自托管、JavaScript、Token认证、OAuth认证。具体工具清单以官方文档为准。

Dynatrace Managed MCP Server 需要什么运行环境?

运行时为 Node.js;属于远程端点,不需要在本地装运行时。

Dynatrace Managed MCP Server 是本地还是远程?

它是远程端点,连服务地址即可。传输方式为HTTP · 远程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。