dynatrace-managed-mcp: Instructions file for GitHub Copilot

Dynatrace Managed MCP Server

You are a Developer working on the Dynatrace Managed Model-Context-Protocol (MCP) Server project.

This is a TypeScript/Node.js MCP server that connects AI assistants to self-hosted Dynatrace Managed deployments. It uses the MCP SDK (https://www.npmjs.com/package/@modelcontextprotocol/sdk) to expose Dynatrace observability data as MCP tools and resources.

Build, Test, and Lint Commands

# Build
npm run build              # Compile TypeScript to dist/

# Test
npm test                   # Run all tests
npm run test:unit          # Unit tests only (src/**/__tests__/*.test.ts)
npm run test:integration   # Integration tests (tests/**/*.integration.test.ts)
npm run coverage           # Generate coverage report (coverage/lcov-report/index.html)

# Run specific test file
npm test -- tests/integration/capabilities.integration.test.ts

# Formatting
npm run prettier           # Check formatting
npm run prettier:fix       # Auto-fix formatting

# Run server
npm run serve              # Run HTTP server on port 8080
node --env-file=.env ./dist/index.js        # Run with stdio transport
node --env-file=.env ./dist/index.js --http # Run with HTTP transport

# Development tools
npx @modelcontextprotocol/inspector node --env-file=.env ./dist/index.js  # MCP Inspector

Integration tests require a .env file with real Dynatrace Managed credentials (see .env.template). Tests expect two environments: one with alias testAlias (valid) and one with alias invalidApiToken (wrong token for error testing).

Architecture

High-Level Structure

MCP Client (AI Assistant)
    ↓
MCP Server (src/index.ts)
    ↓
Capability Clients (src/capabilities/*.ts)
    ↓
Auth Client Manager (src/authentication/managed-auth-client.ts)
    ↓
Dynatrace Managed API (multiple environments)

The MCP server supports multi-environment setups via DT_ENVIRONMENT_CONFIGS, allowing queries across multiple Dynatrace Managed instances.

Key Components