# shashivj/dynatrace-mcp architecture

> Architecture diagram of the GitHub repository shashivj/dynatrace-mcp, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-05-22). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/shashivj/dynatrace-mcp
- Repository: https://github.com/shashivj/dynatrace-mcp

## Overview

##### Project type and purpose
- This is a Node.js/TypeScript based “MCP server” that exposes Dynatrace observability data and automation workflows to MCP-aware clients (VS Code, Claude, Amazon Q CLI, etc.) over STDIO.
- It implements a small command-line microservice that routes incoming MCP requests to capability handlers, invokes the Dynatrace REST APIs (and optionally Slack) and returns results in the MCP protocol.

##### File structure
- Top-level files:
- package.json / tsconfig.json → Node/TypeScript config & dependencies
- .env.template → lists required OAuth and feature flags
- src/index.ts → main entrypoint that wires MCP server, parses STDIO messages, dispatches to handlers
- src/dynatrace-clients.ts → HTTP clients for Dynatrace APIs (authentication, fetch, execute DQL, workflows, etc.)
- src/capabilities/*.ts → one file per capability (list-problems, get-logs, send-slack-message, etc.)
- No database, no frontend – it’s purely a CLI microservice interacting with external APIs.

##### Key insights from README
- The project’s core responsibilities:
- Authenticate with Dynatrace OAuth
- Provide capabilities (problem/vulnerability listing, DQL queries, Slack notifications, workflow automation, ownership info)
- Integrate with Slack Connector and Dynatrace AutomationEngine
- Target environment: any MCP-aware client over STDIO.
- Environment variables control authentication and feature flags.

##### Main components
a. MCP Client (e.g., VS Code, Claude, Amazon Q CLI)
b. Dynatrace MCP Server
- Index.ts – MCP protocol handler
- Capability Handlers – individual modules under src/capabilities
- Dynatrace Clients – under src/dynatrace-clients.ts
c. External Services
- Dynatrace Platform APIs
- Slack API (optional, via Slack Connector)
- Dynatrace AutomationEngine (for workflows)
d. Configuration
- .env environment variables (OAuth credentials, DT_ENVIRONMENT, feature flags)

##### Relationships & data flow
- MCP Server → dispatch to Capability Handler → use Dynatrace Client
- Dynatrace Client ↔ Dynatrace Platform over HTTPS (OAuth token)
- If needed, Dynatrace Client → Slack Connector API or → AutomationEngine API
- Responses flow back up: Dynatrace → Capability Handler → MCP Server → STDIO → MCP Client

##### Architectural patterns and design principles
- Modular “Capability” pattern: one handler per feature, single-responsibility
- Adapter layer (dynatrace-clients.ts) isolates API calls & auth from business logic
- Environment-driven configuration keeps secrets outside code
- Thin protocol layer in index.ts – just routing and error handling

2. Inside, place:
- A “MCP Protocol Adapter (index.ts)” rectangle at the top
- Below it, a “Capability Handlers” cluster: show small rectangles for each handler file (list-problems, get-logs, send-slack-message, etc.)
- A shared “Dynatrace HTTP Clients” rectangle on the side

## Diagram (Mermaid)

```mermaid
flowchart TD
    MCPClient["MCP Client"]:::external
    MCPClient -->|"STDIO"| Protocol

    subgraph "Dynatrace MCP Server"
        Protocol["MCP Protocol Adapter (index.ts)"]:::internal
        Protocol -->|"dispatch"| Capabilities

        subgraph "Capability Handlers"
            direction TB
            C1["create-workflow-for-problem-notification"]:::internal
            C2["execute-dql"]:::internal
            C3["get-events-for-cluster"]:::internal
            C4["get-logs-for-entity"]:::internal
            C5["get-monitored-entity-details"]:::internal
            C6["get-ownership-information"]:::internal
            C7["get-problem-details"]:::internal
            C8["get-vulnerability-details"]:::internal
            C9["list-problems"]:::internal
            C10["list-vulnerabilities"]:::internal
            C11["send-slack-message"]:::internal
            C12["update-workflow"]:::internal
        end

        Capabilities --> C1
        Capabilities --> C2
        Capabilities --> C3
        Capabilities --> C4
        Capabilities --> C5
        Capabilities --> C6
        Capabilities --> C7
        Capabilities --> C8
        Capabilities --> C9
        Capabilities --> C10
        Capabilities --> C11
        Capabilities --> C12

        C1 -->|"use client"| DynatraceClients
        C2 -->|"use client"| DynatraceClients
        C3 -->|"use client"| DynatraceClients
        C4 -->|"use client"| DynatraceClients
        C5 -->|"use client"| DynatraceClients
        C6 -->|"use client"| DynatraceClients
        C7 -->|"use client"| DynatraceClients
        C8 -->|"use client"| DynatraceClients
        C9 -->|"use client"| DynatraceClients
        C10 -->|"use client"| DynatraceClients
        C11 -->|"use client"| DynatraceClients
        C12 -->|"use client"| DynatraceClients

        DynatraceClients["Dynatrace HTTP Clients"]:::internal
        Config[".env Config"]:::config
        Config --> DynatraceClients
    end

    DynatraceClients -->|"requests/responses\n(OAuth Token)"| DynatraceAPI[("Dynatrace\nPlatform API")]:::extServ
    DynatraceClients -.->|"optional"| SlackAPI[("Slack API")]:::extServ
    DynatraceClients -.->|"optional"| AutoEngine[("AutomationEngine API")]:::extServ

    click Protocol "https://github.com/shashivj/dynatrace-mcp/blob/main/src/index.ts"
    click DynatraceClients "https://github.com/shashivj/dynatrace-mcp/blob/main/src/dynatrace-clients.ts"
    click Config "https://github.com/shashivj/dynatrace-mcp/blob/main/.env.template"
    click C1 "https://github.com/shashivj/dynatrace-mcp/blob/main/src/capabilities/create-workflow-for-problem-notification.ts"
    click C2 "https://github.com/shashivj/dynatrace-mcp/blob/main/src/capabilities/execute-dql.ts"
    click C3 "https://github.com/shashivj/dynatrace-mcp/blob/main/src/capabilities/get-events-for-cluster.ts"
    click C4 "https://github.com/shashivj/dynatrace-mcp/blob/main/src/capabilities/get-logs-for-entity.ts"
    click C5 "https://github.com/shashivj/dynatrace-mcp/blob/main/src/capabilities/get-monitored-entity-details.ts"
    click C6 "https://github.com/shashivj/dynatrace-mcp/blob/main/src/capabilities/get-ownership-information.ts"
    click C7 "https://github.com/shashivj/dynatrace-mcp/blob/main/src/capabilities/get-problem-details.ts"
    click C8 "https://github.com/shashivj/dynatrace-mcp/blob/main/src/capabilities/get-vulnerability-details.ts"
    click C9 "https://github.com/shashivj/dynatrace-mcp/blob/main/src/capabilities/list-problems.ts"
    click C10 "https://github.com/shashivj/dynatrace-mcp/blob/main/src/capabilities/list-vulnerabilities.ts"
    click C11 "https://github.com/shashivj/dynatrace-mcp/blob/main/src/capabilities/send-slack-message.ts"
    click C12 "https://github.com/shashivj/dynatrace-mcp/blob/main/src/capabilities/update-workflow.ts"

    classDef internal fill:#74c0fc,stroke:#228be6,color:#000;
    classDef external fill:#b2f2bb,stroke:#2f9e44,color:#000;
    classDef extServ fill:#d3f9d8,stroke:#40c057,color:#000;
    classDef config fill:#ffd43b,stroke:#f08c00,color:#000;
```
