Integrations
Enables real-time observability data access from Dynatrace, allowing users to fetch problem details, security vulnerabilities, execute DQL queries, retrieve logs and metrics, analyze Kubernetes cluster events, and set up notifications via Slack and Dynatrace AutomationEngine.
Provides tools for monitoring Kubernetes clusters, retrieving problem details from services, and analyzing cluster events to troubleshoot deployment issues.
Allows sending notification messages to Slack channels via a Slack Connector, supporting features like alerting on availability problems and security vulnerabilities.
Dynatrace MCP Server
This remote MCP server allows interaction with the Dynatrace observability platform. Bring real-time observability data directly into your development workflow.
Use cases
- Real-time observability, fetch production-level data for early detection.
- Fix issues in the context from monitored exceptions, logs, and anomalies.
- More context on security level issues
- Natural language to query log data
Capabilities
- List and get problem details from your services (for example Kubernetes)
- List and get security problems / vulnerability details
- Execute DQL(Dynatrace Query Language) like getting events or logs
- Send Slack messages (via Slack Connector)
- Set up notification Workflow (via Dynatrace AutomationEngine)
- Get Ownership of an entity
Quickstart
Work in progress
You can add this MCP server (using STDIO) to your MCP Client like VS Code, Claude, Cursor, Windsurf Github Copilot via the package @dynatrace-oss/dynatrace-mcp-server
.
VS Code
Claude Desktop
Environment Variables
A Dynatrace OAuth Client is needed to communicate with your Dynatrace Environment. Please follow the documentation about creating an Oauth Client in Dynatrace, and set up the following environment variables in order for this MCP to work:
DT_ENVIRONMENT
(string, e.g., https://abcd1234.apps.dynatrace.com) - URL to your Dynatrace PlatformOAUTH_CLIENT_ID
(string, e.g.,dt0s02.SAMPLE
) - Dynatrace OAuth Client IDOAUTH_CLIENT_SECRET
(string, e.g.,dt0s02.SAMPLE.abcd1234
) - Dynatrace OAuth Client Secret- OAuth Client Scopes:
app-engine:apps:run
- needed for environmentInformationClientapp-engine:functions:run
- needed for environmentInformationClienthub:catalog:read
- get details about installed Apps on Dynatrace Environmentenvironment-api:security-problems:read
- needed for reading security problemsenvironment-api:entities:read
- read monitored entitiesenvironment-api:problems:read
- get problemsenvironment-api:metrics:read
- read metricsenvironment-api:slo:read
- read SLOssettings:objects:read
- needed for reading ownership information and Guardians (SRG) from settingsstorage:buckets:read
- Read all system data stored on Grailstorage:logs:read
- Read logs for reliability guardian validationsstorage:metrics:read
- Read metrics for reliability guardian validationsstorage:bizevents:read
- Read bizevents for reliability guardian validationsstorage:spans:read
- Read spans from Grailstorage:entities:read
- Read Entities from Grailstorage:system:read
- Read System Data from Grailstorage:user.events:read
- Read User events from Grailstorage:user.sessions:read
- Read User sessions from Grail
In addition, depending on the features you use, the following variables can be configured:
SLACK_CONNECTION_ID
(string) - connection ID of a Slack ConnectionUSE_APP_SETTINGS
(boolean,true
orfalse
; default:false
)- Requires scope
app-settings:objects:read
to read settings-objects from app settings
- Requires scope
USE_WORKFLOWS
(boolean,true
orfalse
; default:false
)- Requires scopes
automation:workflows:read
,automation:workflows:write
andautomation:workflows:run
to read, write and execute Workflows
- Requires scopes
✨ Example prompts ✨
Use these example prompts as a starting point. Just copy them into your IDE or agent setup, adapt them to your services/stack/architecture, and extend them as needed. They’re here to help you imagine how real-time observability and automation work together in the MCP context in your IDE.
Find open vulnerabilities on production, setup alert.
Debug intermittent 503 errors.
Correlate memory issue with logs.
Trace request flow analysis.
Analyze Kubernetes cluster events.
Development
For development purposes, you can use VSCode and GitHub Copilot.
First, enable Copilot for your Workspace .vscode/settings.json
:
Second, add the MCP to .vscode/mcp.json
:
Third, create a .env
file in this repository (you can copy from .env.template
) and configure environment variables as described above.
Last but not least, switch to Agent Mode in CoPilot and reload tools.
Notes
This product is not officially supported by Dynatrace. Please contact us via GitHub Issues if you have feature requests, questions, or need help.
This server cannot be installed
A remote MCP server that enables real-time interaction with the Dynatrace observability platform, bringing production-level monitoring data directly into development workflows.
Related MCP Servers
- -securityAlicense-qualityMCP server for interacting with Prometheus metrics and data.Last updated -8JavaScriptMIT License
- -securityFlicense-qualityA configurable MCP server that dynamically loads capabilities from a remote configuration to bridge MCP clients with remote APIs for executing actions, accessing resources, and utilizing prompt templates.Last updated -1,2614TypeScript
- AsecurityAlicenseAqualityThe MCP server provides an interface to the Datadog API, enabling seamless management of incidents, monitoring, logs, dashboards, metrics, traces, and hosts. Its extensible design allows easy integration of additional Datadog APIs for future expansions.Last updated -1432236TypeScriptApache 2.0
- AsecurityFlicenseAqualityAn MCP server implementation that enables interaction with the Unstructured API, providing tools to list, create, update, and manage sources, destinations, and workflows.Last updated -3925