Dynatrace SaaS MCP Server
Related Servers
Alternatives to Dynatrace SaaS MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables interaction with Dynatrace Grail and API endpoints by executing DQL queries, retrieving logs, reporting active problems, and querying metrics.-
- AlicenseAqualityBmaintenanceEnables AI assistants to interact with self-hosted Dynatrace Managed environments to retrieve observability data, security insights, and performance metrics. It allows users to query problems, logs, events, and SLOs through natural language interfaces in both local and remote modes.181,223 npm35Apache 2.0
- AlicenseBqualityCmaintenanceEnables Cursor's agent to query Dynatrace Managed and SaaS through the classic API v2 using API-token authentication, with read-only-by-default tools for logs, problems, events, entities, metrics, security problems, and SLOs. It also provides composite root-cause-analysis and service-debugging workflows, with optional opt-in write and Grail DQL tools.23MIT
- FlicenseNot gradedqualityAmaintenanceProvides Model Context Protocol access to the Dynatrace platform API, letting AI agents run live queries against observability, security, and platform data and manage a Dynatrace environment. It is hosted remotely by Dynatrace, so MCP hosts can add it by name from the official registry without installing anything.-
- FlicenseBqualityDmaintenanceEnables AI assistants to interact with Datadog APIs for querying metrics, logs, events, monitors, and APM traces.164-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Datadog's observability platform via natural language, covering metrics, logs, APM, monitors, dashboards, incidents, and infrastructure.1MIT
TDQS
Scored across 152 tools
Most tools target a distinct resource and action, with clear descriptions naming API versions and scopes. Some confusion is possible between generic execute_dql and purpose-built search_logs/search_spans/query_metric, and between v1/v2 notification tools, but these boundaries are mostly explained.
The vast majority follow a consistent snake_case verb_noun pattern (list/get/create/update/delete/ingest/execute). Minor deviations include get_extension actually listing versions, non-verb-noun names like check_api_spec_drift, and mixing verb families (validate/verify/check/preview) for similar safety operations.
152 tools is an extreme count for a single MCP server, far beyond the 25+ threshold for 'too many'. Even for a broad platform like Dynatrace, this creates a heavy selection burden and suggests the server is a dumping ground of many APIs rather than a coherent toolset.
Many resources have full CRUD (dashboards, SLOs, settings, monitors, workflows, buckets, feature flags, IAM). However there are notable dead ends: problems and vulnerabilities are read-only, custom services only list/get, and extensions lack create/delete for the extension itself.