What is the key difference between Dynatrace MCP and Scherlok?

Dynatrace MCP belongs to the Monitoring category with local stdio execution, while Scherlok belongs to the Monitoring category with local stdio execution.

How do I install Dynatrace MCP or Scherlok in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Dynatrace MCP and Scherlok free or paid?

Dynatrace MCP operates under a Free / Open Source model (OAuth 2.0). Scherlok operates under a Free / Open Source model (API Key required).

Which MCP server has more tools and community activity?

Dynatrace MCP lists 6 tools with 3 views and 138 GitHub stars. Scherlok lists 6 tools with 2 views and 9 GitHub stars.

Can I use both Dynatrace MCP and Scherlok together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Dynatrace MCP vs Scherlok

In-depth architectural comparison of the Dynatrace MCP and Scherlok MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Dynatrace MCP

Monitoring · Local stdio

Quality: 37/100 (Fair) | Auth: OAuth 2.0

Scherlok

Monitoring · Local stdio

Quality: 55/100 (Good) | Auth: API Key required

Verdict Summary: Choose Dynatrace MCP if you need specialized Monitoring tools running via a local process. Choose Scherlok if your workspace requires Monitoring integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Dynatrace MCP when:

You need dedicated capabilities in the Monitoring domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (Free / Open Source).
You have access to required keys: DT_ENVIRONMENT, DT_MCP_TOKEN_STORAGE, DT_GRAIL_QUERY_BUDGET_GB.
Primary tools included: Execute and validate Dynatrace DQL, Search Dynatrace entities and observability problems, Query vulnerabilities, exceptions, and Kubernetes events.

Explore Dynatrace MCP Details

Choose Scherlok when:

You need dedicated capabilities in the Monitoring domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: SCHERLOK_CONNECTION, ANTHROPIC_API_KEY.

Feature & Specification Comparison

Specification	Dynatrace MCP dynatrace-oss Monitoring	Scherlok rbmuller Monitoring
Summary	Leverage AI-driven observability, security, and automation to analyze anomalies, logs, traces, events, metrics.	Zero-config data quality monitoring across Postgres, BigQuery, Snowflake, MySQL, and DuckDB. Profile a warehouse, detect anomalies (volume, schema drift, freshness, NULLs, distribution, cardinality), with optional dbt manifest lineage. Read-only — connection resolved server-side, never passed via the model.
Category & Scope

Tools & Capabilities Breakdown

Dynatrace MCP Tools (6)

Execute and validate Dynatrace DQL

Search Dynatrace entities and observability problems

Query vulnerabilities, exceptions, and Kubernetes events

Use Davis Copilot and Davis analyzers

Send notifications and create notebooks

Track Grail query budget consumption

Scherlok Tools (6)

Zero-config anomaly detection without manual rules

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Dynatrace MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "dynatrace-oss-dynatrace-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@dynatrace-oss/dynatrace-mcp-server"
      ],
      "env": {
        "DT_ENVIRONMENT": "YOUR_DT_ENVIRONMENT_HERE",
        "DT_MCP_TOKEN_STORAGE": "YOUR_DT_MCP_TOKEN_STORAGE_HERE",
        "DT_GRAIL_QUERY_BUDGET_GB": "YOUR_DT_GRAIL_QUERY_BUDGET_GB_HERE"
      }
    }
  }
}

Scherlok Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "rbmuller-scherlok": {
      "command": "uvx",
      "args": [
        "scherlok"
      ],
      "env": {
        "SCHERLOK_CONNECTION": "YOUR_SCHERLOK_CONNECTION_HERE",
        "ANTHROPIC_API_KEY": "YOUR_ANTHROPIC_API_KEY_HERE"
      }
    }
  }
}

Frequently Asked Questions

Dynatrace MCP is categorized under Monitoring and uses a local stdio subprocess. In contrast, Scherlok belongs to Monitoring using local stdio subprocess. Select Dynatrace MCP when you need capabilities focused on monitoring and Scherlok when you require tools for monitoring.

More alternatives to Dynatrace MCP More alternatives to Scherlok Monitoring category hub