Dynatrace MCP Server

Dynatrace mcp mcp server lets Claude, Cursor and other MCP clients work with Dynatrace MCP directly. [DEPRECATED] Model Context Protocol (MCP) server for Dynatrace. Migrate to dynatrace-for-ai + dtctl or the Dynatrace Remote MCP Server.

What Dynatrace MCP does

Please migrate to one of the actively maintained alternatives:

Key capabilities

• Observability & Problem Management (e.g., list_problems, list_vulnerabilities, list_exceptions, get_kubernetes_events)
• Querying Data from Grail (e.g., execute_dql, verify_dql, generate_dql_from_natural_language, explain_dql_in_natural_language)
• Entity Discovery (e.g., find_entity_by_name)
• Dynatrace Intelligence (e.g., chat_with_davis_copilot, list_davis_analyzers, execute_davis_analyzer)
• Automation & Notifications (e.g., send_slack_message, send_email, send_event)
• Share results (e.g., create_dynatrace_notebook)

Tools it exposes

Once connected, the assistant can call these 14 tools directly:

• Real — time observability** - Fetch production-level data for early detection and proactive monitoring
• Multi — phase incident investigation** - Systematic 4-phase approach with automated impact assessment
• Cross — data source correlation** - Connect problems → spans → logs with trace ID correlation
• server.type — node
• server.entry_point — dist/index.js
• mcp_config.command — node
• mcp_config.args — ["${__dirname}/dist/index.js"]
• app-engine — apps:run - needed for almost all tools
• app-settings — objects:read - read app-settings - needed for send_slack_message tool to read connection details from App-Settings
• storage — buckets:read - needed for execute_dql tool to read all system data stored on Grail
• davis-copilot — conversations:execute - execute conversational skill (chat with Copilot)
• davis — analyzers:read - needed for listing and getting Davis analyzer definitions
• email — emails:send - needed for send_email tool to send emails
• document — documents:read - needed for list_documents and read_document tools to list and read Dynatrace documents (Notebooks, Dashboards, Launchpads, etc.)

Installing the dynatrace mcp mcp server

The server is distributed via npm as @dynatrace-oss/dynatrace-mcp-server, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Configuration

Before the server will start you need to supply 8 environment variables: DT_ENVIRONMENT, DT_PLATFORM_TOKEN, MCP_BEARER_TOKEN, HTTPS_PROXY, NO_PROXY, OAUTH_CLIENT_ID, OAUTH_CLIENT_SECRET, DT_SSO_URL. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

• Node.js v24 or newer is required to run the Dynatrace MCP Server.

Where it fits

Monitoring servers replace the paste-the-stack-trace ritual with an assistant that reads the real event, with all its surrounding context intact. Dynatrace MCP sits in that group, and the shape of its toolset — Real, Multi, Cross among others — tells you what it is really for. Worth comparing against the other monitoring security servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• With 14 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use Dynatrace MCP.
• Maintained by dynatrace-oss, written in Go.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the dynatrace mcp mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.