TalkO11yToMe: Learning MCP Servers with Dynatrace Integration

Name: TalkO11yToMe: Learning MCP Servers with Dynatrace Integration
Author: chiefnamingofficer

@chiefnamingofficer

Repository

About TalkO11yToMe: Learning MCP Servers with Dynatrace Integration

Learning what it means to use MCP by trying to interact with Dynatrace MCP server.

#mcp #dynatrace #observability

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "TalkO11yToMe": {
      "command": "node",
      "args": [
        "lib/demo-dotenv.js"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is TalkO11yToMe: Learning MCP Servers with Dynatrace Integration?

TalkO11yToMe: Learning MCP Servers with Dynatrace Integration is a learning project that demonstrates how to build and use MCP (Model Context Protocol) servers with Dynatrace observability data. It provides six production-ready tools for querying logs, metrics, problems, and business analytics from Dynatrace tenants, and includes comprehensive documentation for setting up MCP-based AI workflows.

How to use TalkO11yToMe: Learning MCP Servers with Dynatrace Integration?

Prerequisites: Node.js 18+, a Dynatrace tenant, and either an API token or OAuth client credentials. Copy the environment template (cp env/env.template env/.env.dev), edit it with your credentials, then test the configuration with node lib/demo-dotenv.js. Run the appropriate tool for your environment: node tools/grail-log-query.js for Grail tenants or node tools/classic-log-query.js for Classic tenants. Use the test suite (node tests/test-suite.js) to validate all tools.

Key features of TalkO11yToMe: Learning MCP Servers with Dynatrace Integration

Six production-ready Dynatrace tools with shared configuration
DQL Query Polling for async log and event queries
OAuth authentication with 5-minute bearer token lifecycle
Support for both Grail and Classic Dynatrace environments
Clean architecture separating shared infrastructure from tools
Comprehensive test suite with 8 validation tests and history tracking

Use cases of TalkO11yToMe: Learning MCP Servers with Dynatrace Integration

AI-powered incident response: analyze Lambda errors and generate priorities
Production debugging context: search logs and metrics during coding sessions
Daily health monitoring: run morning standup dashboards and Lambda health checks

FAQ from TalkO11yToMe: Learning MCP Servers with Dynatrace Integration

What MCP features does this server cover?

The project demonstrates MCP Tools (functions AI can call), Resources (data sources AI can read), and Prompts (templates for common AI interactions). It uses the MCP protocol to connect AI systems like Claude and Cursor to Dynatrace data.

What Dynatrace environment types are supported?

Both Grail environments (*.apps.dynatrace.com) and Classic environments (*.live.dynatrace.com) are supported. Grail requires OAuth authentication; Classic works with either an API token or OAuth.

What are the runtime requirements?

Node.js 18+ is required (v20.19.2 LTS recommended). You also need access to a Dynatrace tenant and API credentials (token or OAuth client).

How can I verify my setup works?

Run node lib/demo-dotenv.js to test shared configuration, then node tools/dynatrace-monitor.js to verify tool execution. The full test suite (node tests/test-suite.js) runs 8 validation tests including environment detection, authentication, and DQL query polling.

Where do the data and credentials live?

Credentials are stored in a local .env.dev file (template provided in env/). All Dynatrace data is retrieved live from your tenant – no data is stored locally beyond test results saved in tests/results/.