dt-app-mcp

dt-app-mcp

Dynatrace Apps MCP Server – provides Strato component documentation, SDK documentation, DQL knowledge base, and experience standards to AI coding assistants via the Model Context Protocol (MCP).

What it does

The dt-app-mcp server exposes the following tools to any MCP-compatible AI client:

Tool	Description
list_strato_components	List Strato components by name or keyword
get_strato_component	Get detailed component docs, props, and examples
get_strato_usecases	Get full code for Strato component use cases
list_sdks	List available Dynatrace SDK documentation packages
get_sdk	Get complete documentation for a specific SDK package
get_dql_knowledgebase	Get Semantic search over the DQL knowledge base
get_experience_standard	Get app experience standards by keywords

Installation

npm install -g dt-app-mcp

Or use it directly with npx:

npx dt-app-mcp

Usage with Claude Code

Option 1: Add via CLI

claude mcp add dt-app-mcp -- npx -y dt-app-mcp

Option 2: Add to project config

Create or edit .mcp.json in your project root:

{
  "mcpServers": {
    "dt-app-mcp": {
      "command": "npx",
      "args": ["-y", "dt-app-mcp"]
    }
  }
}

Option 3: Add to global Claude config

Add to ~/.claude.json:

{
  "mcpServers": {
    "dt-app-mcp": {
      "command": "npx",
      "args": ["-y", "dt-app-mcp"]
    }
  }
}

Usage with VS Code (GitHub Copilot)

If you have the Dynatrace Apps VS Code extension installed, the MCP server is automatically registered with GitHub Copilot. No additional configuration is needed.

Usage with other MCP clients

The server communicates over stdio using the MCP JSON-RPC protocol. You can integrate it with any MCP-compatible client by running:

npx dt-app-mcp

HTTP transport

The server also supports the MCP Streamable HTTP transport. This is useful when you want a long-running server that can be shared across multiple clients, or when your MCP client connects over HTTP rather than spawning a subprocess.

Start in HTTP mode

npx dt-app-mcp --http                 # listens on http://127.0.0.1:7421/mcp
npx dt-app-mcp --http -- port 8080    # custom port
npx dt-app-mcp --http --host 0.0.0.0  # bind all interfaces (use with caution)

Environment variables

Variable	Description	Default
DT_APP_MCP_TRANSPORT	Set to http to enable HTTP mode	stdio
DT_APP_MCP_PORT	HTTP port	7421
DT_APP_MCP_HOST	HTTP host	127.0.0.1

Endpoints

Endpoint	Method	Description
/mcp	POST	JSON-RPC requests
/mcp	GET	Server-sent events stream
/mcp	DELETE	Explicit session termination
/healthz	GET	Liveness probe — returns { "status": "ok" }

Client configuration example (HTTP)

{
  "mcpServers": {
    "dt-app-mcp": {
      "type": "http",
      "url": "http://127.0.0.1:7421/mcp"
    }
  }
}

Notes

• Stdio remains the default and the recommended transport for IDE integrations (Claude Code, VS Code Copilot).
• HTTP mode uses stateless mode — each request is independent. This matches the read-only nature of all available tools.
• DNS rebinding protection is enabled automatically when the server binds to 127.0.0.1 or localhost.
• For production deployments, place an authenticated reverse proxy (nginx, Caddy) in front of the server rather than binding to a public interface directly.