Dynatrace
This MCP Server allows interaction with the Dynatrace observability platform, brining real-time observability data directly into your development workflow.
100K+
18 Tools
Packaged by
Requires Secrets
Add to Docker Desktop
Version 4.43 or later needs to be installed to add the server automatically
Tools
| Name | Description |
|---|---|
chat_with_davis_copilot | Use this tool to ask any Dynatrace related question, in case no other more specific tool is available. |
create_dynatrace_notebook | Create a new notebook in the Dynatrace platform (NOT a Jupyter notebook) to share your analysis and findings with colleagues. |
execute_davis_analyzer | Execute a Davis Analyzer with custom input parameters. Use "list_davis_analyzers" first to see available analyzers and their names. |
execute_dql | Get data like Logs, Metrics, Spans, Events, or Entity Data from Dynatrace Grail by executing a Dynatrace Query Language (DQL) statement. Use the "generate_dql_from_natural_language" tool upfront to generate or refine a DQL statement based on your request. To learn about possible fields available for filtering, use the query "fetch dt.semantic_dictionary.models | filter data_object == \"logs\"". IMPORTANT: The MCP App UI will automatically render the query results as an interactive table and chart. Do NOT generate Mermaid diagrams, ASCII charts, markdown tables, or any other visual representation of the data — the MCP App is solely responsible for rendering. |
explain_dql_in_natural_language | Explain Dynatrace Query Language (DQL) statements in natural language using Davis CoPilot AI. |
find_entity_by_name | Find the entityId and type of a monitored entity (service, host, process-group, application, kubernetes-node, custom-app, ...) within the topology on Dynatrace, based on the name of the entity. Run this before querying data like logs, metrics, problems, events. If no entity name is known, make an educated guess with common identifiers like package.json `id`/`name`, helm chart names, kubernetes manifest names, and alike. |
generate_dql_from_natural_language | Convert natural language queries to Dynatrace Query Language (DQL) using Davis CoPilot AI. You can ask for problem events, security issues, logs, metrics, spans, and custom data. |
get_environment_info | Get information about the connected Dynatrace Environment (Tenant) and verify the connection and authentication. |
get_kubernetes_events | Get all events from a specific Kubernetes (K8s) cluster |
list_davis_analyzers | List all available Davis Analyzers in Dynatrace (forecast, anomaly detection, correlation analyzers, and more) |
list_exceptions | List all exceptions known on Dynatrace starting with the most recent. |
list_problems | List all problems (based on "fetch dt.davis.problems") known on Dynatrace, sorted by their recency. |
list_vulnerabilities | Retrieve all active (non-muted) vulnerabilities from Dynatrace. An additional filter can be provided using DQL filter (filter for a specific entity type and id). |
reset_grail_budget | Reset the Grail query budget after it was exhausted, allowing new queries to be executed. This clears all tracked bytes scanned in the current session. |
send_email | Send an email using the Dynatrace Email API. The sender will be [email protected]. Maximum 10 recipients total across TO, CC, and BCC. |
send_event | Send a custom event to Dynatrace using the Events API v2. Use this to ingest custom events for alerting, tracking deployments, configuration changes, or any custom business events. |
send_slack_message | Sends a Slack message to a dedicated Slack Channel via Slack Connector on Dynatrace |
verify_dql | Syntactically verify a Dynatrace Query Language (DQL) statement on Dynatrace GRAIL before executing it. Recommended for generated DQL statements. Skip for statements created by `generate_dql_from_natural_language` tool, as well as from documentation. |