Dynatrace MCP Server
[DEPRECATED] Access Dynatrace observability data: logs, metrics, problems, vulnerabilities via DQL and Dynatrace Intelligence
- Category
- Developer Tools
- Primary Subcategory
- Observability, Monitoring & Incident Response
Integration details
Description
⚠️ This package is deprecated and no longer maintained. For local development (VS Code, Cursor, Claude Code, IntelliJ, …), migrate to Dynatrace-for-AI + dtctl: https://github.com/Dynatrace/dynatrace-for-ai/. For agent-to-agent use cases (Atlassian Rovo, GitHub Coding Agent, …), use the Dynatrace Remote MCP Server: https://www.dynatrace.com/hub/detail/dynatrace-mcp-server/
- Integration type
- Connector
- Verification status
Verified connector- Platform
- Claude
- Primary Subcategory
- Observability, Monitoring & Incident Response
- Secondary Subcategories
- None listed
- Brand
- Dynatrace
- Access
- Unknown
- First tracked
- 2026-08-12
- Tool count
- 18
- Geography
- US
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Claude Discoverability Score
Dynatrace MCP Server isn’t discoverable through Claude’s Connector picker
It runs as a local Claude Desktop Extension, so Claude cannot surface or score it there today.
No spam. Unsubscribe any time.
No spam. Unsubscribe any time.
What the current score measures

Remote Connectors Claude can surface from the Connector picker.
About Claude's Discoverability Score
Your Connector now competes to appear for users’ prompts
18 tools agents can invoke
How do I improve a Verified connector's discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.
