[{"_1":2,"_349":-5,"_350":-5},"loaderData",{"_3":4,"_22":23,"_24":25,"_287":288},"root",{"_5":6,"_7":8},"toasts",[],"visitor",{"_9":10,"_11":12},"viewportWidth",1280,"visitorSession",{"_13":14,"_16":17,"_18":-5,"_19":20,"_21":-5},"attributes",[15],"BOT","id",7058884,"membership","referenceId","01971406-43e3-74e8-b880-2f000258007a","userAccount","routes/_public/_layout",{},"routes/_public/mcp/servers/~namespace/~slug/_pages/_layout",{"_26":27,"_81":-5,"_82":40,"_29":83,"_205":206,"_286":157},"availableLocales",[28,40,46,53,60,67,74],{"_29":30,"_33":37,"_38":39},"mcpServer",{"_31":32,"_33":34,"_35":36},"description","Ein Remote-MCP-Server, der eine Echtzeitinteraktion mit der Dynatrace-Beobachtungsplattform ermöglicht und Überwachungsdaten auf Produktionsebene direkt in Entwicklungs-Workflows einbringt.","name","Dynatrace MCP Server","readme","# Dynatrace MCP Server\n\nDieser Remote-MCP-Server ermöglicht die Interaktion mit der [Dynatrace-](https://www.dynatrace.com/) Beobachtungsplattform. Integrieren Sie Echtzeit-Beobachtungsdaten direkt in Ihren Entwicklungsworkflow.\n\n## Anwendungsfälle\n\n* Echtzeit-Beobachtbarkeit, Abrufen von Daten auf Produktionsebene zur Früherkennung.\n* Beheben Sie Probleme im Kontext überwachter Ausnahmen, Protokolle und Anomalien.\n* Mehr Kontext zu Sicherheitsproblemen\n* Natürliche Sprache zum Abfragen von Protokolldaten\n\n## Funktionen\n\n* Listen Sie Ihre Dienste auf und erhalten Sie [Problemdetails](https://www.dynatrace.com/hub/detail/problems/) (z. B. Kubernetes).\n* Auflisten und Abrufen von Sicherheitsproblemen/ [Sicherheitslückendetails](https://www.dynatrace.com/hub/detail/vulnerabilities/)\n* Führen Sie DQL (Dynatrace Query Language) aus, z. B. zum Abrufen von Ereignissen oder Protokollen\n* Slack-Nachrichten senden (über Slack Connector)\n* Benachrichtigungs-Workflow einrichten (über Dynatrace [AutomationEngine](https://docs.dynatrace.com/docs/discover-dynatrace/platform/automationengine) )\n* Besitz einer Entität erhalten\n\n## Schnellstart\n\n**In Arbeit**\n\nSie können diesen MCP-Server (mit STDIO) über das Paket `@dynatrace-oss/dynatrace-mcp-server` zu Ihrem MCP-Client wie VS Code, Claude, Cursor, Windsurf Github Copilot hinzufügen.\n\n**VS Code**\n\n```json\n{\n \"servers\": {\n \"npx-dynatrace-mcp-server\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@dynatrace-oss/dynatrace-mcp-server@latest\"],\n \"envFile\": \"${workspaceFolder}/.env\"\n }\n }\n}\n```\n\nHinweis: In dieser Konfiguration wird [die Variable `${workspaceFolder}`](https://code.visualstudio.com/docs/reference/variables-reference#_predefined-variables) verwendet. Dies funktioniert nur, wenn die Konfiguration in den aktuellen Arbeitsbereichen gespeichert ist, z. B. `/.vscode/mcp.json` . Alternativ kann dies auch in den Benutzereinstellungen gespeichert werden, und Sie können `env` wie folgt definieren:\n\n```json\n{\n \"servers\": {\n \"npx-dynatrace-mcp-server\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@dynatrace-oss/dynatrace-mcp-server@latest\"],\n \"env\": {\n \"OAUTH_CLIENT_ID\": \"\",\n \"OAUTH_CLIENT_SECRET\": \"\",\n \"DT_ENVIRONMENT\": \"\"\n }\n }\n }\n}\n```\n\n**Claude Desktop**\n\n```json\n{\n \"mcpServers\": {\n \"mobile-mcp\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@dynatrace-oss/dynatrace-mcp-server@latest\"],\n \"env\": {\n \"OAUTH_CLIENT_ID\": \"\",\n \"OAUTH_CLIENT_SECRET\": \"\",\n \"DT_ENVIRONMENT\": \"\"\n }\n }\n }\n}\n```\n\n**Amazon Q-Entwickler-CLI**\n\nDie [Amazon Q Developer CLI](https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/command-line-chat.html) bietet eine interaktive Chat-Erfahrung direkt in Ihrem Terminal. Sie können Fragen stellen, Hilfe zu AWS-Services erhalten, Probleme beheben und Codeausschnitte generieren, ohne Ihre Befehlszeilenumgebung zu verlassen.\n\n```json\n{\n \"mcpServers\": {\n \"mobile-mcp\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@dynatrace-oss/dynatrace-mcp-server@latest\"],\n \"env\": {\n \"OAUTH_CLIENT_ID\": \"\",\n \"OAUTH_CLIENT_SECRET\": \"\",\n \"DT_ENVIRONMENT\": \"\"\n }\n }\n }\n}\n```\n\n## Umgebungsvariablen\n\nFür die Kommunikation mit Ihrer Dynatrace-Umgebung ist ein **Dynatrace OAuth-Client** erforderlich. Beachten Sie die Dokumentation zum [Erstellen eines OAuth-Clients in Dynatrace](https://docs.dynatrace.com/docs/manage/identity-access-management/access-tokens-and-oauth-clients/oauth-clients) und richten Sie die folgenden Umgebungsvariablen ein, damit dieser MCP funktioniert:\n\n* `DT_ENVIRONMENT` (Zeichenfolge, z. B. ) – URL zu Ihrer Dynatrace-Plattform\n* `OAUTH_CLIENT_ID` (Zeichenfolge, z. `dt0s02.SAMPLE` ) – Dynatrace OAuth-Client-ID\n* `OAUTH_CLIENT_SECRET` (Zeichenfolge, z. B. `dt0s02.SAMPLE.abcd1234` ) – Dynatrace OAuth-Client-Geheimnis\n* OAuth-Clientbereiche:\n * `app-engine:apps:run` – wird für environmentInformationClient benötigt\n * `app-engine:functions:run` – wird für environmentInformationClient benötigt\n * `hub:catalog:read` – Details zu installierten Apps in der Dynatrace-Umgebung abrufen\n * `environment-api:security-problems:read` – wird zum Lesen von Sicherheitsproblemen benötigt\n * `environment-api:entities:read` – Überwachte Entitäten lesen\n * `environment-api:problems:read` – Probleme abrufen\n * `environment-api:metrics:read` – Metriken lesen\n * `environment-api:slo:read` – SLOs lesen\n * `settings:objects:read` - wird zum Lesen von Eigentümerinformationen und Guardians (SRG) aus den Einstellungen benötigt\n * `storage:buckets:read` – Alle auf Grail gespeicherten Systemdaten lesen\n * `storage:logs:read` – Protokolle für Zuverlässigkeitswächtervalidierungen lesen\n * `storage:metrics:read` – Metriken für Zuverlässigkeitswächtervalidierungen lesen\n * `storage:bizevents:read` – Lesen Sie Bizevents für Zuverlässigkeitswächtervalidierungen\n * `storage:spans:read` – Spans aus Grail lesen\n * `storage:entities:read` – Entitäten aus Grail lesen\n * `storage:events:read` – Ereignisse aus Grail lesen\n * `storage:system:read` – Systemdaten aus Grail lesen\n * `storage:user.events:read` – Benutzerereignisse aus Grail lesen\n * `storage:user.sessions:read` – Benutzersitzungen aus Grail lesen\n\nDarüber hinaus können, abhängig von den von Ihnen genutzten Funktionen, folgende Variablen konfiguriert werden:\n\n* `SLACK_CONNECTION_ID` (Zeichenfolge) – Verbindungs-ID einer [Slack-Verbindung](https://docs.dynatrace.com/docs/analyze-explore-automate/workflows/actions/slack)\n* `USE_APP_SETTINGS` (Boolesch, `true` oder `false` ; Standard: `false` )\n * Erfordert den Bereich `app-settings:objects:read` um Einstellungsobjekte aus den App-Einstellungen zu lesen.\n* `USE_WORKFLOWS` (Boolesch, `true` oder `false` ; Standard: `false` )\n * Erfordert die Bereiche `automation:workflows:read` , `automation:workflows:write` und `automation:workflows:run` zum Lesen, Schreiben und Ausführen von Workflows\n\n## ✨ Beispielaufforderungen ✨\n\nNutzen Sie diese Beispieleingabeaufforderungen als Ausgangspunkt. Kopieren Sie sie einfach in Ihre IDE oder Ihr Agent-Setup, passen Sie sie an Ihre Dienste, Ihren Stack und Ihre Architektur an und erweitern Sie sie nach Bedarf. Sie helfen Ihnen, sich vorzustellen, wie Echtzeit-Beobachtbarkeit und Automatisierung im MCP-Kontext Ihrer IDE zusammenarbeiten.\n\n**Finden Sie offene Schwachstellen in der Produktion und richten Sie eine Warnung ein.**\n\n```\nI have this code snippet here in my IDE, where I get a dependency vulnerability warning for my code.\nCheck if I see any open vulnerability/cve on production.\nAnalyze a specific production problem.\nSetup a workflow that sends Slack alerts to the #devops-alerts channel when availability problems occur.\n```\n\n**Debuggen Sie zeitweise auftretende 503-Fehler.**\n\n```\nOur load balancer is intermittently returning 503 errors during peak traffic.\nPull all recent problems detected for our front-end services and\nrun a query to correlate error rates with service instance health indicators.\nI suspect we have circuit breakers triggering, but need confirmation from the telemetry data.\n```\n\n**Korrelieren Sie Speicherprobleme mit Protokollen.**\n\n```\nThere's a problem with high memory usage on one of our hosts.\nGet the problem details and then fetch related logs to help understand\nwhat's causing the memory spike? Which file in this repo is this related to?\n```\n\n**Trace-Anforderungsflussanalyse.**\n\n```\nOur users are experiencing slow checkout processes.\nCan you execute a DQL query to show me the full request trace for our checkout flow,\nso I can identify which service is causing the bottleneck?\n```\n\n**Analysieren Sie Kubernetes-Clusterereignisse.**\n\n```\nOur application deployments seem to be failing intermittently.\nCan you fetch recent events from our \"production-cluster\"\nto help identify what might be causing these deployment issues?\n```\n\n## Entwicklung\n\nFür Entwicklungszwecke können Sie VSCode und GitHub Copilot verwenden.\n\nAktivieren Sie zunächst Copilot für Ihren Arbeitsbereich `.vscode/settings.json` :\n\n```json\n{\n \"github.copilot.enable\": {\n \"*\": true\n }\n}\n\n```\n\nZweitens fügen Sie das MCP zu `.vscode/mcp.json` hinzu:\n\n```json\n{\n \"servers\": {\n \"my-dynatrace-mcp-server\": {\n \"command\": \"node\",\n \"args\": [\n \"${workspaceFolder}/dist/index.js\"\n ],\n \"envFile\": \"${workspaceFolder}/.env\"\n }\n }\n}\n```\n\nDrittens: Erstellen Sie in diesem Repository eine `.env` Datei (Sie können sie aus `.env.template` kopieren) und konfigurieren Sie die Umgebungsvariablen wie [oben beschrieben](#environment-variables) .\n\nZu guter Letzt wechseln Sie in CoPilot in den Agentenmodus und laden Sie die Tools neu.\n\n## Hinweise\n\nDieses Produkt wird von Dynatrace nicht offiziell unterstützt. Bitte kontaktieren Sie uns über [GitHub Issues](https://github.com/dynatrace-oss/dynatrace-mcp/issues) , wenn Sie Funktionswünsche haben, Fragen haben oder Hilfe benötigen.","German","tag","de-DE",{"_29":41,"_33":44,"_38":45},{"_31":42,"_33":34,"_35":43},"A remote MCP server that enables real-time interaction with the Dynatrace observability platform, bringing production-level monitoring data directly into development workflows.","# Dynatrace MCP Server\n\nThis remote MCP server allows interaction with the [Dynatrace](https://www.dynatrace.com/) observability platform.\nBring real-time observability data directly into your development workflow.\n\n $\"image\"$ \n\n## Use cases\n\n- Real-time observability, fetch production-level data for early detection.\n- Fix issues in the context from monitored exceptions, logs, and anomalies.\n- More context on security level issues\n- Natural language to query log data\n\n## Capabilities\n\n- List and get [problem](https://www.dynatrace.com/hub/detail/problems/) details from your services (for example Kubernetes)\n- List and get security problems / [vulnerability](https://www.dynatrace.com/hub/detail/vulnerabilities/) details\n- Execute DQL(Dynatrace Query Language) like getting events or logs\n- Send Slack messages (via Slack Connector)\n- Set up notification Workflow (via Dynatrace [AutomationEngine](https://docs.dynatrace.com/docs/discover-dynatrace/platform/automationengine))\n- Get Ownership of an entity\n\n## Quickstart\n\n**Work in progress**\n\nYou 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`.\n\n**VS Code**\n\n```json\n{\n \"servers\": {\n \"npx-dynatrace-mcp-server\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@dynatrace-oss/dynatrace-mcp-server@latest\"],\n \"envFile\": \"${workspaceFolder}/.env\"\n }\n }\n}\n```\n\nPlease note: In this config, [the `${workspaceFolder}` variable](https://code.visualstudio.com/docs/reference/variables-reference#_predefined-variables) is used.\nThis only works if the config is stored in the current workspaces, e.g., `/.vscode/mcp.json`. Alternatively, this can also be stored in user-settings, and you can define `env` as follows:\n\n```json\n{\n \"servers\": {\n \"npx-dynatrace-mcp-server\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@dynatrace-oss/dynatrace-mcp-server@latest\"],\n \"env\": {\n \"OAUTH_CLIENT_ID\": \"\",\n \"OAUTH_CLIENT_SECRET\": \"\",\n \"DT_ENVIRONMENT\": \"\"\n }\n }\n }\n}\n```\n\n**Claude Desktop**\n```json\n{\n \"mcpServers\": {\n \"mobile-mcp\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@dynatrace-oss/dynatrace-mcp-server@latest\"],\n \"env\": {\n \"OAUTH_CLIENT_ID\": \"\",\n \"OAUTH_CLIENT_SECRET\": \"\",\n \"DT_ENVIRONMENT\": \"\"\n }\n }\n }\n}\n```\n\n**Amazon Q Developer CLI**\n\nThe [Amazon Q Developer CLI](https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/command-line-chat.html) provides an interactive chat experience directly in your terminal. You can ask questions, get help with AWS services, troubleshoot issues, and generate code snippets without leaving your command line environment.\n```json\n{\n \"mcpServers\": {\n \"mobile-mcp\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@dynatrace-oss/dynatrace-mcp-server@latest\"],\n \"env\": {\n \"OAUTH_CLIENT_ID\": \"\",\n \"OAUTH_CLIENT_SECRET\": \"\",\n \"DT_ENVIRONMENT\": \"\"\n }\n }\n }\n}\n```\n\n## Environment Variables\n\nA **Dynatrace OAuth Client** is needed to communicate with your Dynatrace Environment. Please follow the documentation about\n[creating an Oauth Client in Dynatrace](https://docs.dynatrace.com/docs/manage/identity-access-management/access-tokens-and-oauth-clients/oauth-clients),\nand set up the following environment variables in order for this MCP to work:\n\n* `DT_ENVIRONMENT` (string, e.g., https://abcd1234.apps.dynatrace.com) - URL to your Dynatrace Platform\n* `OAUTH_CLIENT_ID` (string, e.g., `dt0s02.SAMPLE`) - Dynatrace OAuth Client ID\n* `OAUTH_CLIENT_SECRET` (string, e.g., `dt0s02.SAMPLE.abcd1234`) - Dynatrace OAuth Client Secret\n* OAuth Client Scopes:\n * `app-engine:apps:run` - needed for environmentInformationClient\n * `app-engine:functions:run` - needed for environmentInformationClient\n * `hub:catalog:read` - get details about installed Apps on Dynatrace Environment\n * `environment-api:security-problems:read` - needed for reading security problems\n * `environment-api:entities:read` - read monitored entities\n * `environment-api:problems:read` - get problems\n * `environment-api:metrics:read` - read metrics\n * `environment-api:slo:read` - read SLOs\n * `settings:objects:read` - needed for reading ownership information and Guardians (SRG) from settings\n * `storage:buckets:read` - Read all system data stored on Grail\n * `storage:logs:read` - Read logs for reliability guardian validations\n * `storage:metrics:read` - Read metrics for reliability guardian validations\n * `storage:bizevents:read` - Read bizevents for reliability guardian validations\n * `storage:spans:read` - Read spans from Grail\n * `storage:entities:read` - Read Entities from Grail\n * `storage:events:read` - Read Events from Grail\n * `storage:system:read` - Read System Data from Grail\n * `storage:user.events:read` - Read User events from Grail\n * `storage:user.sessions:read` - Read User sessions from Grail\n\nIn addition, depending on the features you use, the following variables can be configured:\n\n* `SLACK_CONNECTION_ID` (string) - connection ID of a [Slack Connection](https://docs.dynatrace.com/docs/analyze-explore-automate/workflows/actions/slack)\n* `USE_APP_SETTINGS` (boolean, `true` or `false`; default: `false`)\n * Requires scope `app-settings:objects:read` to read settings-objects from app settings\n* `USE_WORKFLOWS` (boolean, `true` or `false`; default: `false`)\n * Requires scopes `automation:workflows:read`, `automation:workflows:write` and `automation:workflows:run` to read, write and execute Workflows\n\n## ✨ Example prompts ✨\n\nUse these example prompts as a starting point. Just copy them into your IDE or agent setup, adapt them to your services/stack/architecture,\nand 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.\n\n**Find open vulnerabilities on production, setup alert.**\n```\nI have this code snippet here in my IDE, where I get a dependency vulnerability warning for my code.\nCheck if I see any open vulnerability/cve on production.\nAnalyze a specific production problem.\nSetup a workflow that sends Slack alerts to the #devops-alerts channel when availability problems occur.\n```\n**Debug intermittent 503 errors.**\n```\nOur load balancer is intermittently returning 503 errors during peak traffic.\nPull all recent problems detected for our front-end services and\nrun a query to correlate error rates with service instance health indicators.\nI suspect we have circuit breakers triggering, but need confirmation from the telemetry data.\n```\n**Correlate memory issue with logs.**\n```\nThere's a problem with high memory usage on one of our hosts.\nGet the problem details and then fetch related logs to help understand\nwhat's causing the memory spike? Which file in this repo is this related to?\n```\n**Trace request flow analysis.**\n```\nOur users are experiencing slow checkout processes.\nCan you execute a DQL query to show me the full request trace for our checkout flow,\nso I can identify which service is causing the bottleneck?\n```\n**Analyze Kubernetes cluster events.**\n```\nOur application deployments seem to be failing intermittently.\nCan you fetch recent events from our \"production-cluster\"\nto help identify what might be causing these deployment issues?\n```\n\n## Development\n\nFor development purposes, you can use VSCode and GitHub Copilot.\n\nFirst, enable Copilot for your Workspace `.vscode/settings.json`:\n```json\n{\n \"github.copilot.enable\": {\n \"*\": true\n }\n}\n\n```\n\nSecond, add the MCP to `.vscode/mcp.json`:\n```json\n{\n \"servers\": {\n \"my-dynatrace-mcp-server\": {\n \"command\": \"node\",\n \"args\": [\n \"${workspaceFolder}/dist/index.js\"\n ],\n \"envFile\": \"${workspaceFolder}/.env\"\n }\n }\n}\n```\n\nThird, create a `.env` file in this repository (you can copy from `.env.template`) and configure environment variables as [described above](#environment-variables).\n\nLast but not least, switch to Agent Mode in CoPilot and reload tools.\n\n\n## Notes\nThis product is not officially supported by Dynatrace.\nPlease contact us via [GitHub Issues](https://github.com/dynatrace-oss/dynatrace-mcp/issues) if you have feature requests, questions, or need help.\n","English","en-US",{"_29":47,"_33":51,"_38":52},{"_31":48,"_33":49,"_35":50},"Un servidor MCP remoto que permite la interacción en tiempo real con la plataforma de observación Dynatrace, llevando datos de monitoreo de nivel de producción directamente a los flujos de trabajo de desarrollo.","Servidor Dynatrace MCP","# Servidor Dynatrace MCP\n\nEste servidor MCP remoto permite la interacción con la plataforma de observabilidad [Dynatrace](https://www.dynatrace.com/) . Incorpore datos de observabilidad en tiempo real directamente a su flujo de trabajo de desarrollo.\n\n## Casos de uso\n\n* Observabilidad en tiempo real, obtención de datos a nivel de producción para detección temprana.\n* Solucione problemas en el contexto a partir de excepciones, registros y anomalías monitoreadas.\n* Más contexto sobre cuestiones de nivel de seguridad\n* Lenguaje natural para consultar datos de registro\n\n## Capacidades\n\n* Enumere y obtenga detalles [de los problemas](https://www.dynatrace.com/hub/detail/problems/) de sus servicios (por ejemplo, Kubernetes)\n* Enumere y obtenga problemas de seguridad/detalles [de vulnerabilidad](https://www.dynatrace.com/hub/detail/vulnerabilities/)\n* Ejecutar DQL (lenguaje de consulta Dynatrace) como si se tratase de obtener eventos o registros\n* Enviar mensajes de Slack (a través del conector de Slack)\n* Configurar el flujo de trabajo de notificaciones (a través de Dynatrace [AutomationEngine](https://docs.dynatrace.com/docs/discover-dynatrace/platform/automationengine) )\n* Obtener la propiedad de una entidad\n\n## Inicio rápido\n\n**Trabajo en progreso**\n\nPuede agregar este servidor MCP (usando STDIO) a su cliente MCP como VS Code, Claude, Cursor, Windsurf Github Copilot a través del paquete `@dynatrace-oss/dynatrace-mcp-server` .\n\n**Código VS**\n\n```json\n{\n \"servers\": {\n \"npx-dynatrace-mcp-server\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@dynatrace-oss/dynatrace-mcp-server@latest\"],\n \"envFile\": \"${workspaceFolder}/.env\"\n }\n }\n}\n```\n\nNota: En esta configuración, se usa [la variable `${workspaceFolder}`](https://code.visualstudio.com/docs/reference/variables-reference#_predefined-variables) . Esto solo funciona si la configuración se almacena en los espacios de trabajo actuales, por ejemplo, `/.vscode/mcp.json` . También se puede almacenar en la configuración del usuario y definir `env` de la siguiente manera:\n\n```json\n{\n \"servers\": {\n \"npx-dynatrace-mcp-server\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@dynatrace-oss/dynatrace-mcp-server@latest\"],\n \"env\": {\n \"OAUTH_CLIENT_ID\": \"\",\n \"OAUTH_CLIENT_SECRET\": \"\",\n \"DT_ENVIRONMENT\": \"\"\n }\n }\n }\n}\n```\n\n**Escritorio de Claude**\n\n```json\n{\n \"mcpServers\": {\n \"mobile-mcp\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@dynatrace-oss/dynatrace-mcp-server@latest\"],\n \"env\": {\n \"OAUTH_CLIENT_ID\": \"\",\n \"OAUTH_CLIENT_SECRET\": \"\",\n \"DT_ENVIRONMENT\": \"\"\n }\n }\n }\n}\n```\n\n**CLI para desarrolladores de Amazon Q**\n\nLa [CLI para desarrolladores de Amazon Q](https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/command-line-chat.html) ofrece una experiencia de chat interactiva directamente en tu terminal. Puedes hacer preguntas, obtener ayuda con los servicios de AWS, solucionar problemas y generar fragmentos de código sin salir de tu entorno de línea de comandos.\n\n```json\n{\n \"mcpServers\": {\n \"mobile-mcp\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@dynatrace-oss/dynatrace-mcp-server@latest\"],\n \"env\": {\n \"OAUTH_CLIENT_ID\": \"\",\n \"OAUTH_CLIENT_SECRET\": \"\",\n \"DT_ENVIRONMENT\": \"\"\n }\n }\n }\n}\n```\n\n## Variables de entorno\n\nSe necesita un **cliente OAuth de Dynatrace** para comunicarse con su entorno de Dynatrace. Siga la documentación sobre [cómo crear un cliente OAuth en Dynatrace](https://docs.dynatrace.com/docs/manage/identity-access-management/access-tokens-and-oauth-clients/oauth-clients) y configure las siguientes variables de entorno para que este MCP funcione:\n\n* `DT_ENVIRONMENT` (cadena, p. ej., ): URL a su plataforma Dynatrace\n* `OAUTH_CLIENT_ID` (cadena, p. ej., `dt0s02.SAMPLE` ): ID de cliente OAuth de Dynatrace\n* `OAUTH_CLIENT_SECRET` (cadena, p. ej., `dt0s02.SAMPLE.abcd1234` ): secreto de cliente OAuth de Dynatrace\n* Ámbitos del cliente OAuth:\n * `app-engine:apps:run` - necesario para environmentInformationClient\n * `app-engine:functions:run` - necesario para environmentInformationClient\n * `hub:catalog:read` : obtener detalles sobre las aplicaciones instaladas en el entorno Dynatrace\n * `environment-api:security-problems:read` - necesario para leer problemas de seguridad\n * `environment-api:entities:read` - leer entidades monitoreadas\n * `environment-api:problems:read` - obtener problemas\n * `environment-api:metrics:read` - leer métricas\n * `environment-api:slo:read` - leer SLO\n * `settings:objects:read` - necesario para leer información de propiedad y Guardianes (SRG) desde la configuración\n * `storage:buckets:read` - Leer todos los datos del sistema almacenados en Grail\n * `storage:logs:read` : leer registros para validaciones del guardián de confiabilidad\n * `storage:metrics:read` - Leer métricas para validaciones de guardianes de confiabilidad\n * `storage:bizevents:read` - Leer bizevents para validaciones de guardianes de confiabilidad\n * `storage:spans:read` - Lectura de intervalos de Grail\n * `storage:entities:read` - Leer entidades de Grail\n * `storage:events:read` - Leer eventos de Grail\n * `storage:system:read` - Leer datos del sistema desde Grail\n * `storage:user.events:read` - Leer eventos de usuario desde Grail\n * `storage:user.sessions:read` - Leer sesiones de usuario desde Grail\n\nAdemás, dependiendo de las funciones que utilices, se pueden configurar las siguientes variables:\n\n* `SLACK_CONNECTION_ID` (cadena): ID de conexión de una [conexión de Slack](https://docs.dynatrace.com/docs/analyze-explore-automate/workflows/actions/slack)\n* `USE_APP_SETTINGS` (booleano, `true` o `false` ; valor predeterminado: `false` )\n * Requiere el ámbito `app-settings:objects:read` para leer settings-objects desde la configuración de la aplicación\n* `USE_WORKFLOWS` (booleano, `true` o `false` ; predeterminado: `false` )\n * Requiere los ámbitos `automation:workflows:read` , `automation:workflows:write` y `automation:workflows:run` para leer, escribir y ejecutar flujos de trabajo.\n\n## ✨ Ejemplos de indicaciones ✨\n\nUtilice estos ejemplos de indicaciones como punto de partida. Simplemente cópielos en su IDE o configuración del agente, adáptelos a sus servicios, pila o arquitectura y amplíelos según sea necesario. Le ayudarán a imaginar cómo la observabilidad en tiempo real y la automatización funcionan juntas en el contexto de MCP de su IDE.\n\n**Encuentre vulnerabilidades abiertas en producción, configure alertas.**\n\n```\nI have this code snippet here in my IDE, where I get a dependency vulnerability warning for my code.\nCheck if I see any open vulnerability/cve on production.\nAnalyze a specific production problem.\nSetup a workflow that sends Slack alerts to the #devops-alerts channel when availability problems occur.\n```\n\n**Depurar errores intermitentes 503.**\n\n```\nOur load balancer is intermittently returning 503 errors during peak traffic.\nPull all recent problems detected for our front-end services and\nrun a query to correlate error rates with service instance health indicators.\nI suspect we have circuit breakers triggering, but need confirmation from the telemetry data.\n```\n\n**Correlacionar el problema de memoria con los registros.**\n\n```\nThere's a problem with high memory usage on one of our hosts.\nGet the problem details and then fetch related logs to help understand\nwhat's causing the memory spike? Which file in this repo is this related to?\n```\n\n**Análisis del flujo de solicitud de seguimiento.**\n\n```\nOur users are experiencing slow checkout processes.\nCan you execute a DQL query to show me the full request trace for our checkout flow,\nso I can identify which service is causing the bottleneck?\n```\n\n**Analizar eventos del clúster de Kubernetes.**\n\n```\nOur application deployments seem to be failing intermittently.\nCan you fetch recent events from our \"production-cluster\"\nto help identify what might be causing these deployment issues?\n```\n\n## Desarrollo\n\nPara fines de desarrollo, puede utilizar VSCode y GitHub Copilot.\n\nPrimero, habilita Copilot para tu espacio de trabajo `.vscode/settings.json` :\n\n```json\n{\n \"github.copilot.enable\": {\n \"*\": true\n }\n}\n\n```\n\nEn segundo lugar, agregue el MCP a `.vscode/mcp.json` :\n\n```json\n{\n \"servers\": {\n \"my-dynatrace-mcp-server\": {\n \"command\": \"node\",\n \"args\": [\n \"${workspaceFolder}/dist/index.js\"\n ],\n \"envFile\": \"${workspaceFolder}/.env\"\n }\n }\n}\n```\n\nEn tercer lugar, cree un archivo `.env` en este repositorio (puede copiarlo desde `.env.template` ) y configure las variables de entorno como [se describe anteriormente](#environment-variables) .\n\nPor último, pero no menos importante, cambie al modo Agente en CoPilot y vuelva a cargar las herramientas.\n\n## Notas\n\nEste producto no cuenta con soporte oficial de Dynatrace. Contáctanos a través de [GitHub Issues](https://github.com/dynatrace-oss/dynatrace-mcp/issues) si tienes alguna solicitud de funciones, preguntas o necesitas ayuda.","Spanish","es-ES",{"_29":54,"_33":58,"_38":59},{"_31":55,"_33":56,"_35":57},"Dynatrace の可観測性プラットフォームとのリアルタイムのやり取りを可能にし、運用レベルの監視データを開発ワークフローに直接取り込むリモート MCP サーバー。","Dynatrace MCP サーバー","# Dynatrace MCP サーバー\n\nこのリモートMCPサーバーは、 [Dynatraceの](https://www.dynatrace.com/)可観測性プラットフォームとの連携を可能にします。リアルタイムの可観測性データを開発ワークフローに直接取り込むことができます。\n\n## ユースケース\n\n* リアルタイムの観測性により、早期検出のために本番レベルのデータを取得します。\n* 監視対象の例外、ログ、異常からコンテキスト内の問題を修正します。\n* セキュリティレベルの問題に関する詳細なコンテキスト\n* ログデータをクエリするための自然言語\n\n## 機能\n\n* サービス（Kubernetes など）から[問題の](https://www.dynatrace.com/hub/detail/problems/)詳細を一覧表示して取得する\n* セキュリティ上の問題や[脆弱性の](https://www.dynatrace.com/hub/detail/vulnerabilities/)詳細を一覧表示して取得する\n* イベントやログを取得するなどのDQL(Dynatrace Query Language)を実行する\n* Slack メッセージを送信する (Slack コネクタ経由)\n* 通知ワークフローを設定する（Dynatrace [AutomationEngine](https://docs.dynatrace.com/docs/discover-dynatrace/platform/automationengine)経由）\n* エンティティの所有権を取得する\n\n## クイックスタート\n\n**進行中**\n\nこの MCP サーバー (STDIO を使用) は、パッケージ`@dynatrace-oss/dynatrace-mcp-server`を介して、VS Code、Claude、Cursor、Windsurf Github Copilot などの MCP クライアントに追加できます。\n\n**VSコード**\n\n```json\n{\n \"servers\": {\n \"npx-dynatrace-mcp-server\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@dynatrace-oss/dynatrace-mcp-server@latest\"],\n \"envFile\": \"${workspaceFolder}/.env\"\n }\n }\n}\n```\n\n注意：この設定では、 [`${workspaceFolder}`変数](https://code.visualstudio.com/docs/reference/variables-reference#_predefined-variables)が使用されています。これは、設定が現在のワークスペース（例： `/.vscode/mcp.json` ）に保存されている場合にのみ機能します。あるいは、ユーザー設定に保存し、 `env`以下のように定義することもできます。\n\n```json\n{\n \"servers\": {\n \"npx-dynatrace-mcp-server\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@dynatrace-oss/dynatrace-mcp-server@latest\"],\n \"env\": {\n \"OAUTH_CLIENT_ID\": \"\",\n \"OAUTH_CLIENT_SECRET\": \"\",\n \"DT_ENVIRONMENT\": \"\"\n }\n }\n }\n}\n```\n\n**クロードデスクトップ**\n\n```json\n{\n \"mcpServers\": {\n \"mobile-mcp\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@dynatrace-oss/dynatrace-mcp-server@latest\"],\n \"env\": {\n \"OAUTH_CLIENT_ID\": \"\",\n \"OAUTH_CLIENT_SECRET\": \"\",\n \"DT_ENVIRONMENT\": \"\"\n }\n }\n }\n}\n```\n\n**Amazon Q 開発者 CLI**\n\n[Amazon Q 開発者 CLI は、](https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/command-line-chat.html)ターミナル内で直接インタラクティブなチャットエクスペリエンスを提供します。コマンドライン環境を離れることなく、質問したり、AWS サービスに関するサポートを受けたり、問題をトラブルシューティングしたり、コードスニペットを生成したりできます。\n\n```json\n{\n \"mcpServers\": {\n \"mobile-mcp\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@dynatrace-oss/dynatrace-mcp-server@latest\"],\n \"env\": {\n \"OAUTH_CLIENT_ID\": \"\",\n \"OAUTH_CLIENT_SECRET\": \"\",\n \"DT_ENVIRONMENT\": \"\"\n }\n }\n }\n}\n```\n\n## 環境変数\n\nDynatrace 環境と通信するには、 **Dynatrace OAuth クライアントが**必要です。Dynatrace [で OAuth クライアントを作成する](https://docs.dynatrace.com/docs/manage/identity-access-management/access-tokens-and-oauth-clients/oauth-clients)方法についてはドキュメントを参照し、この MCP が機能するように以下の環境変数を設定してください。\n\n* `DT_ENVIRONMENT` (文字列、例: ) - Dynatrace プラットフォームへの URL\n* `OAUTH_CLIENT_ID` (文字列、例： `dt0s02.SAMPLE` ) - Dynatrace OAuth クライアント ID\n* `OAUTH_CLIENT_SECRET` (文字列、例: `dt0s02.SAMPLE.abcd1234` ) - Dynatrace OAuthクライアントシークレット\n* OAuth クライアントスコープ:\n * `app-engine:apps:run` - environmentInformationClient に必要\n * `app-engine:functions:run` - environmentInformationClient に必要\n * `hub:catalog:read` - Dynatrace 環境にインストールされているアプリの詳細を取得します\n * `environment-api:security-problems:read` - セキュリティ問題の読み取りに必要\n * `environment-api:entities:read` - 監視対象エンティティを読み取る\n * `environment-api:problems:read` - 問題を取得する\n * `environment-api:metrics:read` - メトリックを読み取る\n * `environment-api:slo:read` - SLO を読み取る\n * `settings:objects:read` - 設定から所有権情報とガーディアン (SRG) を読み取るために必要\n * `storage:buckets:read` - Grailに保存されているすべてのシステムデータを読み取る\n * `storage:logs:read` - 信頼性ガーディアン検証のログを読み取ります\n * `storage:metrics:read` - 信頼性ガーディアン検証のメトリクスを読み取る\n * `storage:bizevents:read` - 信頼性ガーディアン検証のためにbizeventsを読み取ります\n * `storage:spans:read` - Grailからスパンを読み取る\n * `storage:entities:read` - Grail からエンティティを読み取る\n * `storage:events:read` - Grail からイベントを読み取る\n * `storage:system:read` - Grail からシステムデータを読み取る\n * `storage:user.events:read` - Grail からユーザーイベントを読み取る\n * `storage:user.sessions:read` - Grail からユーザーセッションを読み取る\n\nさらに、使用する機能に応じて、次の変数を設定できます。\n\n* `SLACK_CONNECTION_ID` (文字列) - [Slack接続](https://docs.dynatrace.com/docs/analyze-explore-automate/workflows/actions/slack)の接続ID\n* `USE_APP_SETTINGS` (ブール値、 `true`または`false` ; デフォルト: `false` )\n * アプリ設定から設定オブジェクトを読み取るには、スコープ`app-settings:objects:read`必要です\n* `USE_WORKFLOWS` (ブール値、 `true`または`false` ; デフォルト: `false` )\n * ワークフローの読み取り、書き込み、実行には、スコープの`automation:workflows:read` 、 `automation:workflows:write` 、 `automation:workflows:run`必要です。\n\n## ✨ プロンプト例 ✨\n\nこれらのサンプルプロンプトを出発点としてご利用ください。IDEまたはエージェント設定にコピーし、サービス／スタック／アーキテクチャに合わせて調整し、必要に応じて拡張してください。これらのサンプルプロンプトは、IDEのMCPコンテキストにおいて、リアルタイムオブザーバビリティと自動化がどのように連携するかをイメージするのに役立ちます。\n\n**運用環境で未解決の脆弱性を見つけ、アラートを設定します。**\n\n```\nI have this code snippet here in my IDE, where I get a dependency vulnerability warning for my code.\nCheck if I see any open vulnerability/cve on production.\nAnalyze a specific production problem.\nSetup a workflow that sends Slack alerts to the #devops-alerts channel when availability problems occur.\n```\n\n**断続的に発生する 503 エラーをデバッグします。**\n\n```\nOur load balancer is intermittently returning 503 errors during peak traffic.\nPull all recent problems detected for our front-end services and\nrun a query to correlate error rates with service instance health indicators.\nI suspect we have circuit breakers triggering, but need confirmation from the telemetry data.\n```\n\n**メモリの問題をログと関連付けます。**\n\n```\nThere's a problem with high memory usage on one of our hosts.\nGet the problem details and then fetch related logs to help understand\nwhat's causing the memory spike? Which file in this repo is this related to?\n```\n\n**要求フローの分析をトレースします。**\n\n```\nOur users are experiencing slow checkout processes.\nCan you execute a DQL query to show me the full request trace for our checkout flow,\nso I can identify which service is causing the bottleneck?\n```\n\n**Kubernetes クラスターのイベントを分析します。**\n\n```\nOur application deployments seem to be failing intermittently.\nCan you fetch recent events from our \"production-cluster\"\nto help identify what might be causing these deployment issues?\n```\n\n## 発達\n\n開発目的では、VSCode と GitHub Copilot を使用できます。\n\nまず、ワークスペース`.vscode/settings.json`で Copilot を有効にします。\n\n```json\n{\n \"github.copilot.enable\": {\n \"*\": true\n }\n}\n\n```\n\n次に、MCP を`.vscode/mcp.json`に追加します。\n\n```json\n{\n \"servers\": {\n \"my-dynatrace-mcp-server\": {\n \"command\": \"node\",\n \"args\": [\n \"${workspaceFolder}/dist/index.js\"\n ],\n \"envFile\": \"${workspaceFolder}/.env\"\n }\n }\n}\n```\n\n3 番目に、このリポジトリに`.env`ファイルを作成し ( `.env.template`からコピーできます)、[上記の](#environment-variables)ように環境変数を構成します。\n\n最後に、CoPilot でエージェントモードに切り替えて、ツールをリロードします。\n\n## 注記\n\nこの製品はDynatraceによる公式サポート対象外です。機能のご要望、ご質問、またはサポートが必要な場合は、 [GitHub Issues](https://github.com/dynatrace-oss/dynatrace-mcp/issues)からお問い合わせください。","Japanese","ja-JP",{"_29":61,"_33":65,"_38":66},{"_31":62,"_33":63,"_35":64},"Dynatrace 관찰 플랫폼과 실시간 상호작용을 가능하게 하는 원격 MCP 서버로, 프로덕션 수준의 모니터링 데이터를 개발 워크플로에 직접 제공합니다.","Dynatrace MCP 서버","# Dynatrace MCP 서버\n\n이 원격 MCP 서버를 통해 [Dynatrace](https://www.dynatrace.com/) 관측 플랫폼과 상호 작용할 수 있습니다. 실시간 관측 데이터를 개발 워크플로에 직접 가져오세요.\n\n## 사용 사례\n\n* 실시간 관찰이 가능하며, 조기 감지를 위해 생산 수준의 데이터를 가져옵니다.\n* 모니터링된 예외, 로그 및 이상 현상으로 인해 발생하는 컨텍스트의 문제를 해결합니다.\n* 보안 수준 문제에 대한 더 많은 맥락\n* 로그 데이터를 쿼리하기 위한 자연어\n\n## 역량\n\n* 서비스(예: Kubernetes)에서 [문제](https://www.dynatrace.com/hub/detail/problems/) 세부 정보를 나열하고 가져옵니다.\n* 보안 문제/ [취약점](https://www.dynatrace.com/hub/detail/vulnerabilities/) 세부 정보를 나열하고 가져옵니다.\n* 이벤트나 로그를 가져오는 것과 같은 DQL(Dynatrace Query Language)을 실행합니다.\n* Slack 메시지 보내기(Slack 커넥터를 통해)\n* 알림 워크플로 설정(Dynatrace [AutomationEngine을](https://docs.dynatrace.com/docs/discover-dynatrace/platform/automationengine) 통해)\n* 엔터티의 소유권 얻기\n\n## 빠른 시작\n\n**진행 중인 작업**\n\nVS Code, Claude, Cursor, Windsurf Github Copilot과 같은 MCP 클라이언트에 `@dynatrace-oss/dynatrace-mcp-server` 패키지를 통해 이 MCP 서버를 추가할 수 있습니다(STDIO 사용).\n\n**VS 코드**\n\n지엑스피1\n\n참고: 이 구성에서는 [`${workspaceFolder}` 변수가](https://code.visualstudio.com/docs/reference/variables-reference#_predefined-variables) 사용됩니다. 이 설정은 구성이 현재 작업 공간(예: `/.vscode/mcp.json` )에 저장된 경우에만 작동합니다. 또는 사용자 설정에 저장할 수도 있으며, 다음과 같이 `env` 정의할 수 있습니다.\n\n```json\n{\n \"servers\": {\n \"npx-dynatrace-mcp-server\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@dynatrace-oss/dynatrace-mcp-server@latest\"],\n \"env\": {\n \"OAUTH_CLIENT_ID\": \"\",\n \"OAUTH_CLIENT_SECRET\": \"\",\n \"DT_ENVIRONMENT\": \"\"\n }\n }\n }\n}\n```\n\n**클로드 데스크탑**\n\n```json\n{\n \"mcpServers\": {\n \"mobile-mcp\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@dynatrace-oss/dynatrace-mcp-server@latest\"],\n \"env\": {\n \"OAUTH_CLIENT_ID\": \"\",\n \"OAUTH_CLIENT_SECRET\": \"\",\n \"DT_ENVIRONMENT\": \"\"\n }\n }\n }\n}\n```\n\n**Amazon Q 개발자 CLI**\n\n[Amazon Q Developer CLI는](https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/command-line-chat.html) 터미널에서 바로 대화형 채팅 환경을 제공합니다. 명령줄 환경을 벗어나지 않고도 질문을 하고, AWS 서비스 관련 도움을 받고, 문제를 해결하고, 코드 조각을 생성할 수 있습니다.\n\n```json\n{\n \"mcpServers\": {\n \"mobile-mcp\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@dynatrace-oss/dynatrace-mcp-server@latest\"],\n \"env\": {\n \"OAUTH_CLIENT_ID\": \"\",\n \"OAUTH_CLIENT_SECRET\": \"\",\n \"DT_ENVIRONMENT\": \"\"\n }\n }\n }\n}\n```\n\n## 환경 변수\n\nDynatrace 환경과 통신하려면 **Dynatrace OAuth 클라이언트가** 필요합니다. [Dynatrace에서 OAuth 클라이언트를 생성하는 방법](https://docs.dynatrace.com/docs/manage/identity-access-management/access-tokens-and-oauth-clients/oauth-clients) 에 대한 설명서를 참고하고, 이 MCP가 작동하도록 다음 환경 변수를 설정하세요.\n\n* `DT_ENVIRONMENT` (문자열, 예: ) - Dynatrace 플랫폼의 URL\n* `OAUTH_CLIENT_ID` (문자열, 예: `dt0s02.SAMPLE` ) - Dynatrace OAuth 클라이언트 ID\n* `OAUTH_CLIENT_SECRET` (문자열, 예: `dt0s02.SAMPLE.abcd1234` ) - Dynatrace OAuth 클라이언트 비밀번호\n* OAuth 클라이언트 범위:\n * `app-engine:apps:run` - environmentInformationClient에 필요함\n * `app-engine:functions:run` - environmentInformationClient에 필요함\n * `hub:catalog:read` - Dynatrace 환경에 설치된 앱에 대한 세부 정보 가져오기\n * `environment-api:security-problems:read` - 보안 문제를 읽는 데 필요함\n * `environment-api:entities:read` - 모니터링되는 엔티티 읽기\n * `environment-api:problems:read` - 문제 가져오기\n * `environment-api:metrics:read` - 메트릭 읽기\n * `environment-api:slo:read` - SLO 읽기\n * `settings:objects:read` - 설정에서 소유권 정보 및 보호자(SRG)를 읽는 데 필요합니다.\n * `storage:buckets:read` - Grail에 저장된 모든 시스템 데이터를 읽습니다.\n * `storage:logs:read` - 신뢰성 보호자 검증을 위한 로그 읽기\n * `storage:metrics:read` - 신뢰성 보호자 검증을 위한 메트릭 읽기\n * `storage:bizevents:read` - 신뢰성 보호자 검증을 위해 bizevents를 읽습니다.\n * `storage:spans:read` - Grail에서 span 읽기\n * `storage:entities:read` - Grail에서 엔티티 읽기\n * `storage:events:read` - Grail에서 이벤트 읽기\n * `storage:system:read` - Grail에서 시스템 데이터 읽기\n * `storage:user.events:read` - Grail에서 사용자 이벤트를 읽습니다.\n * `storage:user.sessions:read` - Grail에서 사용자 세션 읽기\n\n또한, 사용하는 기능에 따라 다음 변수를 구성할 수 있습니다.\n\n* `SLACK_CONNECTION_ID` (문자열) - [Slack 연결](https://docs.dynatrace.com/docs/analyze-explore-automate/workflows/actions/slack) 의 연결 ID\n* `USE_APP_SETTINGS` (부울, `true` 또는 `false` ; 기본값: `false` )\n * 앱 설정에서 설정 객체를 읽으려면 범위 `app-settings:objects:read` 필요합니다.\n* `USE_WORKFLOWS` (부울, `true` 또는 `false` ; 기본값: `false` )\n * Workflows를 읽고 쓰고 실행하려면 범위 `automation:workflows:read` , `automation:workflows:write` 및 `automation:workflows:run` 필요합니다.\n\n## ✨ 예시 프롬프트 ✨\n\n이 예시 프롬프트를 시작점으로 활용하세요. IDE 또는 에이전트 설정에 복사하고 서비스/스택/아키텍처에 맞게 조정한 후 필요에 따라 확장하기만 하면 됩니다. IDE의 MCP 환경에서 실시간 관측 가능성과 자동화가 어떻게 함께 작동하는지 상상하는 데 도움이 될 것입니다.\n\n**프로덕션 환경에서 열려 있는 취약점을 찾아 알림을 설정합니다.**\n\n```\nI have this code snippet here in my IDE, where I get a dependency vulnerability warning for my code.\nCheck if I see any open vulnerability/cve on production.\nAnalyze a specific production problem.\nSetup a workflow that sends Slack alerts to the #devops-alerts channel when availability problems occur.\n```\n\n**간헐적으로 발생하는 503 오류를 디버깅합니다.**\n\n```\nOur load balancer is intermittently returning 503 errors during peak traffic.\nPull all recent problems detected for our front-end services and\nrun a query to correlate error rates with service instance health indicators.\nI suspect we have circuit breakers triggering, but need confirmation from the telemetry data.\n```\n\n**메모리 문제를 로그와 연관시킵니다.**\n\n```\nThere's a problem with high memory usage on one of our hosts.\nGet the problem details and then fetch related logs to help understand\nwhat's causing the memory spike? Which file in this repo is this related to?\n```\n\n**추적 요청 흐름 분석.**\n\n```\nOur users are experiencing slow checkout processes.\nCan you execute a DQL query to show me the full request trace for our checkout flow,\nso I can identify which service is causing the bottleneck?\n```\n\n**Kubernetes 클러스터 이벤트를 분석합니다.**\n\n```\nOur application deployments seem to be failing intermittently.\nCan you fetch recent events from our \"production-cluster\"\nto help identify what might be causing these deployment issues?\n```\n\n## 개발\n\n개발 목적으로는 VSCode와 GitHub Copilot을 사용할 수 있습니다.\n\n먼저 Workspace `.vscode/settings.json` 에 대해 Copilot을 활성화합니다.\n\n```json\n{\n \"github.copilot.enable\": {\n \"*\": true\n }\n}\n\n```\n\n둘째, `.vscode/mcp.json` 에 MCP를 추가합니다.\n\n```json\n{\n \"servers\": {\n \"my-dynatrace-mcp-server\": {\n \"command\": \"node\",\n \"args\": [\n \"${workspaceFolder}/dist/index.js\"\n ],\n \"envFile\": \"${workspaceFolder}/.env\"\n }\n }\n}\n```\n\n셋째, 이 저장소에 `.env` 파일을 만들고( `.env.template` 에서 복사 가능) [위에서 설명한](#environment-variables) 대로 환경 변수를 구성합니다.\n\n마지막으로 CoPilot에서 에이전트 모드로 전환하고 도구를 다시 로드하세요.\n\n## 노트\n\n이 제품은 Dynatrace에서 공식적으로 지원하지 않습니다. 기능 요청, 질문 또는 도움이 필요하시면 [GitHub Issues를](https://github.com/dynatrace-oss/dynatrace-mcp/issues) 통해 문의해 주세요.","Korean","ko-KR",{"_29":68,"_33":72,"_38":73},{"_31":69,"_33":70,"_35":71},"Удаленный сервер MCP, который обеспечивает взаимодействие в режиме реального времени с платформой наблюдения Dynatrace, перенося данные мониторинга на уровне производства непосредственно в рабочие процессы разработки.","Сервер MCP Dynatrace","# Сервер MCP Dynatrace\n\nЭтот удаленный сервер MCP позволяет взаимодействовать с платформой наблюдения [Dynatrace](https://www.dynatrace.com/) . Вносите данные наблюдения в реальном времени непосредственно в рабочий процесс разработки.\n\n## Варианты использования\n\n* Возможность наблюдения в режиме реального времени, получение данных на уровне производства для раннего обнаружения.\n* Устраняйте проблемы в контексте отслеживаемых исключений, журналов и аномалий.\n* Дополнительный контекст по вопросам уровня безопасности\n* Естественный язык для запроса данных журнала\n\n## Возможности\n\n* Перечислите и получите подробную информацию о [проблемах](https://www.dynatrace.com/hub/detail/problems/) в ваших сервисах (например, Kubernetes)\n* Перечислите и получите сведения о проблемах безопасности/ [уязвимостях](https://www.dynatrace.com/hub/detail/vulnerabilities/)\n* Выполнить DQL (Dynatrace Query Language), например, получить события или журналы\n* Отправка сообщений Slack (через Slack Connector)\n* Настройка рабочего процесса уведомлений (через Dynatrace [AutomationEngine](https://docs.dynatrace.com/docs/discover-dynatrace/platform/automationengine) )\n* Получить право собственности на объект\n\n## Быстрый старт\n\n**Работа в процессе**\n\nВы можете добавить этот сервер MCP (используя STDIO) к своему клиенту MCP, например VS Code, Claude, Cursor, Windsurf Github Copilot, через пакет `@dynatrace-oss/dynatrace-mcp-server` .\n\n**Код VS**\n\n```json\n{\n \"servers\": {\n \"npx-dynatrace-mcp-server\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@dynatrace-oss/dynatrace-mcp-server@latest\"],\n \"envFile\": \"${workspaceFolder}/.env\"\n }\n }\n}\n```\n\nОбратите внимание: в этой конфигурации используется [переменная `${workspaceFolder}`](https://code.visualstudio.com/docs/reference/variables-reference#_predefined-variables) . Это работает только в том случае, если конфигурация хранится в текущих рабочих пространствах, например, `/.vscode/mcp.json` . В качестве альтернативы, это также может храниться в user-settings, и вы можете определить `env` следующим образом:\n\n```json\n{\n \"servers\": {\n \"npx-dynatrace-mcp-server\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@dynatrace-oss/dynatrace-mcp-server@latest\"],\n \"env\": {\n \"OAUTH_CLIENT_ID\": \"\",\n \"OAUTH_CLIENT_SECRET\": \"\",\n \"DT_ENVIRONMENT\": \"\"\n }\n }\n }\n}\n```\n\n**Клод Десктоп**\n\n```json\n{\n \"mcpServers\": {\n \"mobile-mcp\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@dynatrace-oss/dynatrace-mcp-server@latest\"],\n \"env\": {\n \"OAUTH_CLIENT_ID\": \"\",\n \"OAUTH_CLIENT_SECRET\": \"\",\n \"DT_ENVIRONMENT\": \"\"\n }\n }\n }\n}\n```\n\n**Интерфейс командной строки Amazon Q Developer**\n\n[Amazon Q Developer CLI](https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/command-line-chat.html) обеспечивает интерактивный чат прямо в вашем терминале. Вы можете задавать вопросы, получать помощь по сервисам AWS, устранять неполадки и генерировать фрагменты кода, не покидая среду командной строки.\n\n```json\n{\n \"mcpServers\": {\n \"mobile-mcp\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@dynatrace-oss/dynatrace-mcp-server@latest\"],\n \"env\": {\n \"OAUTH_CLIENT_ID\": \"\",\n \"OAUTH_CLIENT_SECRET\": \"\",\n \"DT_ENVIRONMENT\": \"\"\n }\n }\n }\n}\n```\n\n## Переменные среды\n\nДля связи с вашей средой **Dynatrace необходим клиент OAuth от** Dynatrace. Пожалуйста, следуйте документации по [созданию клиента OAuth в Dynatrace](https://docs.dynatrace.com/docs/manage/identity-access-management/access-tokens-and-oauth-clients/oauth-clients) и настройте следующие переменные среды, чтобы этот MCP работал:\n\n* `DT_ENVIRONMENT` (строка, например, ) — URL-адрес вашей платформы Dynatrace\n* `OAUTH_CLIENT_ID` (строка, например, `dt0s02.SAMPLE` ) — идентификатор клиента Dynatrace OAuth\n* `OAUTH_CLIENT_SECRET` (строка, например, `dt0s02.SAMPLE.abcd1234` ) — секрет клиента Dynatrace OAuth\n* Области действия клиента OAuth:\n * `app-engine:apps:run` - требуется для environmentInformationClient\n * `app-engine:functions:run` - требуется для environmentInformationClient\n * `hub:catalog:read` — получение сведений об установленных приложениях в среде Dynatrace\n * `environment-api:security-problems:read` - необходим для чтения проблем безопасности\n * `environment-api:entities:read` - чтение отслеживаемых сущностей\n * `environment-api:problems:read` - получить проблемы\n * `environment-api:metrics:read` - чтение метрик\n * `environment-api:slo:read` - чтение SLO\n * `settings:objects:read` - необходимо для чтения информации о владельце и хранителях (SRG) из настроек\n * `storage:buckets:read` — чтение всех системных данных, хранящихся на Grail\n * `storage:logs:read` - Чтение журналов для проверки надежности Guardian\n * `storage:metrics:read` - Чтение метрик для проверки надежности хранителя\n * `storage:bizevents:read` - Чтение bizevents для проверки надежности Guardian\n * `storage:spans:read` - Чтение spans из Grail\n * `storage:entities:read` - Чтение сущностей из Грааля\n * `storage:events:read` - Чтение событий из Grail\n * `storage:system:read` — Чтение системных данных из Grail\n * `storage:user.events:read` - Чтение пользовательских событий из Grail\n * `storage:user.sessions:read` - Чтение сеансов пользователя из Grail\n\nКроме того, в зависимости от используемых вами функций можно настроить следующие переменные:\n\n* `SLACK_CONNECTION_ID` (строка) — идентификатор [соединения Slack](https://docs.dynatrace.com/docs/analyze-explore-automate/workflows/actions/slack)\n* `USE_APP_SETTINGS` (логическое значение, `true` или `false` ; по умолчанию: `false` )\n * Требуется область действия `app-settings:objects:read` для чтения settings-objects из настроек приложения\n* `USE_WORKFLOWS` (логическое значение, `true` или `false` ; по умолчанию: `false` )\n * Требуются области `automation:workflows:read` , `automation:workflows:write` и `automation:workflows:run` для чтения, записи и выполнения рабочих процессов.\n\n## ✨ Примеры подсказок ✨\n\nИспользуйте эти примеры подсказок в качестве отправной точки. Просто скопируйте их в свою IDE или настройку агента, адаптируйте их к своим сервисам/стеку/архитектуре и расширяйте их по мере необходимости. Они здесь, чтобы помочь вам представить, как наблюдение в реальном времени и автоматизация работают вместе в контексте MCP в вашей IDE.\n\n**Найти открытые уязвимости на производстве, настроить оповещение.**\n\n```\nI have this code snippet here in my IDE, where I get a dependency vulnerability warning for my code.\nCheck if I see any open vulnerability/cve on production.\nAnalyze a specific production problem.\nSetup a workflow that sends Slack alerts to the #devops-alerts channel when availability problems occur.\n```\n\n**Отладка периодически возникающих ошибок 503.**\n\n```\nOur load balancer is intermittently returning 503 errors during peak traffic.\nPull all recent problems detected for our front-end services and\nrun a query to correlate error rates with service instance health indicators.\nI suspect we have circuit breakers triggering, but need confirmation from the telemetry data.\n```\n\n**Соотнесите проблемы с памятью с журналами.**\n\n```\nThere's a problem with high memory usage on one of our hosts.\nGet the problem details and then fetch related logs to help understand\nwhat's causing the memory spike? Which file in this repo is this related to?\n```\n\n**Анализ потока трассировочных запросов.**\n\n```\nOur users are experiencing slow checkout processes.\nCan you execute a DQL query to show me the full request trace for our checkout flow,\nso I can identify which service is causing the bottleneck?\n```\n\n**Анализируйте события кластера Kubernetes.**\n\n```\nOur application deployments seem to be failing intermittently.\nCan you fetch recent events from our \"production-cluster\"\nto help identify what might be causing these deployment issues?\n```\n\n## Разработка\n\nДля разработки вы можете использовать VSCode и GitHub Copilot.\n\nСначала включите Copilot для вашего рабочего пространства `.vscode/settings.json` :\n\n```json\n{\n \"github.copilot.enable\": {\n \"*\": true\n }\n}\n\n```\n\nВо-вторых, добавьте MCP в `.vscode/mcp.json` :\n\n```json\n{\n \"servers\": {\n \"my-dynatrace-mcp-server\": {\n \"command\": \"node\",\n \"args\": [\n \"${workspaceFolder}/dist/index.js\"\n ],\n \"envFile\": \"${workspaceFolder}/.env\"\n }\n }\n}\n```\n\nВ-третьих, создайте файл `.env` в этом репозитории (можно скопировать из `.env.template` ) и настройте переменные среды, как [описано выше](#environment-variables) .\n\nИ последнее, но не менее важное: переключитесь в режим агента в CoPilot и перезагрузите инструменты.\n\n## Примечания\n\nЭтот продукт официально не поддерживается Dynatrace. Пожалуйста, свяжитесь с нами через [GitHub Issues,](https://github.com/dynatrace-oss/dynatrace-mcp/issues) если у вас есть запросы на функции, вопросы или вам нужна помощь.","Russian","ru-RU",{"_29":75,"_33":79,"_38":80},{"_31":76,"_33":77,"_35":78},"远程 MCP 服务器可与 Dynatrace 可观察性平台进行实时交互，将生产级监控数据直接引入开发工作流程。","Dynatrace MCP 服务器","# Dynatrace MCP 服务器\n\n此远程 MCP 服务器允许与[Dynatrace](https://www.dynatrace.com/)可观测性平台进行交互。将实时可观测性数据直接引入您的开发工作流程。\n\n## 用例\n\n* 实时可观察性，获取生产级数据以便早期检测。\n* 从监控的异常、日志和异常中修复上下文中的问题。\n* 有关安全级别问题的更多背景信息\n* 使用自然语言查询日志数据\n\n## 功能\n\n* 列出并获取服务（例如 Kubernetes）的[问题](https://www.dynatrace.com/hub/detail/problems/)详细信息\n* 列出并获取安全问题/[漏洞](https://www.dynatrace.com/hub/detail/vulnerabilities/)详细信息\n* 执行 DQL（Dynatrace 查询语言），例如获取事件或日志\n* 发送 Slack 消息（通过 Slack Connector）\n* 设置通知工作流（通过 Dynatrace [AutomationEngine](https://docs.dynatrace.com/docs/discover-dynatrace/platform/automationengine) ）\n* 获取实体的所有权\n\n## 快速入门\n\n**正在进行中**\n\n您可以通过包`@dynatrace-oss/dynatrace-mcp-server`将此 MCP 服务器（使用 STDIO）添加到您的 MCP 客户端，如 VS Code、Claude、Cursor、Windsurf Github Copilot。\n\n**VS 代码**\n\n```json\n{\n \"servers\": {\n \"npx-dynatrace-mcp-server\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@dynatrace-oss/dynatrace-mcp-server@latest\"],\n \"envFile\": \"${workspaceFolder}/.env\"\n }\n }\n}\n```\n\n请注意：此配置中使用了[`${workspaceFolder}`变量](https://code.visualstudio.com/docs/reference/variables-reference#_predefined-variables)。此方法仅当配置存储在当前工作区中时有效，例如`/.vscode/mcp.json` 。或者，也可以将其存储在用户设置中，您可以按如下方式定义`env` ：\n\n```json\n{\n \"servers\": {\n \"npx-dynatrace-mcp-server\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@dynatrace-oss/dynatrace-mcp-server@latest\"],\n \"env\": {\n \"OAUTH_CLIENT_ID\": \"\",\n \"OAUTH_CLIENT_SECRET\": \"\",\n \"DT_ENVIRONMENT\": \"\"\n }\n }\n }\n}\n```\n\n**克劳德桌面**\n\n```json\n{\n \"mcpServers\": {\n \"mobile-mcp\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@dynatrace-oss/dynatrace-mcp-server@latest\"],\n \"env\": {\n \"OAUTH_CLIENT_ID\": \"\",\n \"OAUTH_CLIENT_SECRET\": \"\",\n \"DT_ENVIRONMENT\": \"\"\n }\n }\n }\n}\n```\n\n**Amazon Q 开发人员 CLI**\n\n[Amazon Q 开发人员 CLI](https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/command-line-chat.html)可直接在您的终端中提供交互式聊天体验。您无需离开命令行环境即可提出问题、获取 AWS 服务帮助、解决问题以及生成代码片段。\n\n```json\n{\n \"mcpServers\": {\n \"mobile-mcp\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@dynatrace-oss/dynatrace-mcp-server@latest\"],\n \"env\": {\n \"OAUTH_CLIENT_ID\": \"\",\n \"OAUTH_CLIENT_SECRET\": \"\",\n \"DT_ENVIRONMENT\": \"\"\n }\n }\n }\n}\n```\n\n## 环境变量\n\n您需要一个**Dynatrace OAuth 客户端**才能与您的 Dynatrace 环境进行通信。请参考[Dynatrace OAuth 客户端](https://docs.dynatrace.com/docs/manage/identity-access-management/access-tokens-and-oauth-clients/oauth-clients)文档，并设置以下环境变量以确保此 MCP 正常工作：\n\n* `DT_ENVIRONMENT` （字符串，例如）- 您的 Dynatrace 平台的 URL\n* `OAUTH_CLIENT_ID` （字符串，例如`dt0s02.SAMPLE` ）- Dynatrace OAuth 客户端 ID\n* `OAUTH_CLIENT_SECRET` （字符串，例如`dt0s02.SAMPLE.abcd1234` ）- Dynatrace OAuth 客户端密钥\n* OAuth 客户端范围：\n * `app-engine:apps:run` - environmentInformationClient 所需\n * `app-engine:functions:run` - environmentInformationClient 所需\n * `hub:catalog:read` - 获取有关 Dynatrace 环境中已安装应用程序的详细信息\n * `environment-api:security-problems:read` - 需要读取安全问题\n * `environment-api:entities:read` - 读取受监控的实体\n * `environment-api:problems:read` - 获取问题\n * `environment-api:metrics:read` - 读取指标\n * `environment-api:slo:read` - 读取 SLO\n * `settings:objects:read` - 需要从设置中读取所有权信息和守护者（SRG）\n * `storage:buckets:read` - 读取存储在 Grail 上的所有系统数据\n * `storage:logs:read` - 读取日志以进行可靠性守护验证\n * `storage:metrics:read` - 读取可靠性守护验证的指标\n * `storage:bizevents:read` - 读取 bizevents 以进行可靠性守护验证\n * `storage:spans:read` - 从 Grail 读取跨度\n * `storage:entities:read` - 从 Grail 读取实体\n * `storage:events:read` - 从 Grail 读取事件\n * `storage:system:read` - 从 Grail 读取系统数据\n * `storage:user.events:read` - 从 Grail 读取用户事件\n * `storage:user.sessions:read` - 从 Grail 读取用户会话\n\n此外，根据您使用的功能，可以配置以下变量：\n\n* `SLACK_CONNECTION_ID` (字符串) - [Slack 连接](https://docs.dynatrace.com/docs/analyze-explore-automate/workflows/actions/slack)的连接 ID\n* `USE_APP_SETTINGS` （布尔值， `true`或`false` ；默认值： `false` ）\n * 需要范围`app-settings:objects:read`从应用程序设置中读取设置对象\n* `USE_WORKFLOWS` （布尔值， `true`或`false` ；默认值： `false` ）\n * 需要范围`automation:workflows:read` 、 `automation:workflows:write`和`automation:workflows:run`来读取、写入和执行工作流\n\n## ✨ 示例提示 ✨\n\n使用这些示例提示作为起点。只需将它们复制到您的 IDE 或代理设置中，使其适应您的服务/堆栈/架构，并根据需要进行扩展即可。它们可以帮助您想象实时可观察性和自动化如何在 IDE 中的 MCP 环境中协同工作。\n\n**查找生产中的开放漏洞，设置警报。**\n\n```\nI have this code snippet here in my IDE, where I get a dependency vulnerability warning for my code.\nCheck if I see any open vulnerability/cve on production.\nAnalyze a specific production problem.\nSetup a workflow that sends Slack alerts to the #devops-alerts channel when availability problems occur.\n```\n\n**调试间歇性 503 错误。**\n\n```\nOur load balancer is intermittently returning 503 errors during peak traffic.\nPull all recent problems detected for our front-end services and\nrun a query to correlate error rates with service instance health indicators.\nI suspect we have circuit breakers triggering, but need confirmation from the telemetry data.\n```\n\n**将内存问题与日志关联起来。**\n\n```\nThere's a problem with high memory usage on one of our hosts.\nGet the problem details and then fetch related logs to help understand\nwhat's causing the memory spike? Which file in this repo is this related to?\n```\n\n**跟踪请求流程分析。**\n\n```\nOur users are experiencing slow checkout processes.\nCan you execute a DQL query to show me the full request trace for our checkout flow,\nso I can identify which service is causing the bottleneck?\n```\n\n**分析 Kubernetes 集群事件。**\n\n```\nOur application deployments seem to be failing intermittently.\nCan you fetch recent events from our \"production-cluster\"\nto help identify what might be causing these deployment issues?\n```\n\n## 发展\n\n出于开发目的，您可以使用 VSCode 和 GitHub Copilot。\n\n首先，为您的工作区`.vscode/settings.json`启用 Copilot：\n\n```json\n{\n \"github.copilot.enable\": {\n \"*\": true\n }\n}\n\n```\n\n其次，将 MCP 添加到`.vscode/mcp.json` ：\n\n```json\n{\n \"servers\": {\n \"my-dynatrace-mcp-server\": {\n \"command\": \"node\",\n \"args\": [\n \"${workspaceFolder}/dist/index.js\"\n ],\n \"envFile\": \"${workspaceFolder}/.env\"\n }\n }\n}\n```\n\n第三，在此存储库中创建一个`.env`文件（您可以从`.env.template`复制）并按照[上述说明](#environment-variables)配置环境变量。\n\n最后但同样重要的是，切换到 CoPilot 中的代理模式并重新加载工具。\n\n## 笔记\n\nDynatrace 未正式支持此产品。如果您有功能请求、疑问或需要帮助，请通过[GitHub Issues](https://github.com/dynatrace-oss/dynatrace-mcp/issues)联系我们。","Chinese","zh-CN","githubUser","locale",{"_84":85,"_86":87,"_13":115,"_123":42,"_124":42,"_125":126,"_130":131,"_154":-5,"_16":155,"_156":157,"_158":159,"_33":34,"_184":144,"_185":186,"_190":-5,"_191":-5,"_192":-5,"_193":194,"_199":-5,"_166":140,"_200":-5,"_201":-5,"_145":202,"_203":204},"addedAt","2025-05-05T20:02:38.567567651Z","argumentsJsonSchema",{"_88":89,"_112":113,"_95":114},"properties",{"_90":91,"_97":98,"_100":101,"_103":104,"_106":107,"_109":110},"USE_WORKFLOWS",{"_92":93,"_31":94,"_95":96},"default","false","Enable workflows (true or false; default: false). Requires scopes automation:workflows:read, automation:workflows:write and automation:workflows:run","type","string","DT_ENVIRONMENT",{"_31":99,"_95":96},"URL to your Dynatrace Platform (e.g., https://abcd1234.apps.dynatrace.com)","OAUTH_CLIENT_ID",{"_31":102,"_95":96},"Dynatrace OAuth Client ID (e.g., dt0s02.SAMPLE)","USE_APP_SETTINGS",{"_92":93,"_31":105,"_95":96},"Enable app settings (true or false; default: false). Requires scope app-settings:objects:read","OAUTH_CLIENT_SECRET",{"_31":108,"_95":96},"Dynatrace OAuth Client Secret (e.g., dt0s02.SAMPLE.abcd1234)","SLACK_CONNECTION_ID",{"_31":111,"_95":96},"Connection ID of a Slack Connection","required",[97,100,106],"object",[116,117,118,119,120,121,122],"author:official","category:monitoring","category:observability","environment:network","hosting:remote-capable","language:javascript","license_grade:a","descriptionMarkdown","descriptionPlainText","githubProject",{"_35":127,"_128":129},"# Dynatrace MCP Server\n\nThis remote MCP server allows interaction with the [Dynatrace](https://www.dynatrace.com/) observability platform.\nBring real-time observability data directly into your development workflow.\n\n $\"image\"$ \n\n## Use cases\n\n- Real-time observability, fetch production-level data for early detection.\n- Fix issues in the context from monitored exceptions, logs, and anomalies.\n- More context on security level issues\n- Natural language to query log data\n\n## Capabilities\n\n- List and get [problem](https://www.dynatrace.com/hub/detail/problems/) details from your services (for example Kubernetes)\n- List and get security problems / [vulnerability](https://www.dynatrace.com/hub/detail/vulnerabilities/) details\n- Execute DQL(Dynatrace Query Language) like getting events or logs\n- Send Slack messages (via Slack Connector)\n- Set up notification Workflow (via Dynatrace [AutomationEngine](https://docs.dynatrace.com/docs/discover-dynatrace/platform/automationengine))\n- Get Ownership of an entity\n\n## Quickstart\n\n**Work in progress**\n\nYou can add this MCP server (using STDIO) to your MCP Client like VS Code, Claude, Cursor, Amazon Q Developer CLI, Windsurf Github Copilot via the package `@dynatrace-oss/dynatrace-mcp-server`.\n\n**VS Code**\n\n```json\n{\n \"servers\": {\n \"npx-dynatrace-mcp-server\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@dynatrace-oss/dynatrace-mcp-server@latest\"],\n \"envFile\": \"${workspaceFolder}/.env\"\n }\n }\n}\n```\n\nPlease note: In this config, [the `${workspaceFolder}` variable](https://code.visualstudio.com/docs/reference/variables-reference#_predefined-variables) is used.\nThis only works if the config is stored in the current workspaces, e.g., `/.vscode/mcp.json`. Alternatively, this can also be stored in user-settings, and you can define `env` as follows:\n\n```json\n{\n \"servers\": {\n \"npx-dynatrace-mcp-server\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@dynatrace-oss/dynatrace-mcp-server@latest\"],\n \"env\": {\n \"OAUTH_CLIENT_ID\": \"\",\n \"OAUTH_CLIENT_SECRET\": \"\",\n \"DT_ENVIRONMENT\": \"\"\n }\n }\n }\n}\n```\n\n**Claude Desktop**\n```json\n{\n \"mcpServers\": {\n \"mobile-mcp\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@dynatrace-oss/dynatrace-mcp-server@latest\"],\n \"env\": {\n \"OAUTH_CLIENT_ID\": \"\",\n \"OAUTH_CLIENT_SECRET\": \"\",\n \"DT_ENVIRONMENT\": \"\"\n }\n }\n }\n}\n```\n\n**Amazon Q Developer CLI**\n\nThe [Amazon Q Developer CLI](https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/command-line-mcp-configuration.html) provides an interactive chat experience directly in your terminal. You can ask questions, get help with AWS services, troubleshoot issues, and generate code snippets without leaving your command line environment.\n```json\n{\n \"mcpServers\": {\n \"mobile-mcp\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@dynatrace-oss/dynatrace-mcp-server@latest\"],\n \"env\": {\n \"OAUTH_CLIENT_ID\": \"\",\n \"OAUTH_CLIENT_SECRET\": \"\",\n \"DT_ENVIRONMENT\": \"\"\n }\n }\n }\n}\n```\n\n## Environment Variables\n\nA **Dynatrace OAuth Client** is needed to communicate with your Dynatrace Environment. Please follow the documentation about\n[creating an Oauth Client in Dynatrace](https://docs.dynatrace.com/docs/manage/identity-access-management/access-tokens-and-oauth-clients/oauth-clients),\nand set up the following environment variables in order for this MCP to work:\n\n* `DT_ENVIRONMENT` (string, e.g., https://abcd1234.apps.dynatrace.com) - URL to your Dynatrace Platform\n* `OAUTH_CLIENT_ID` (string, e.g., `dt0s02.SAMPLE`) - Dynatrace OAuth Client ID\n* `OAUTH_CLIENT_SECRET` (string, e.g., `dt0s02.SAMPLE.abcd1234`) - Dynatrace OAuth Client Secret\n* OAuth Client Scopes:\n * `app-engine:apps:run` - needed for environmentInformationClient\n * `app-engine:functions:run` - needed for environmentInformationClient\n * `hub:catalog:read` - get details about installed Apps on Dynatrace Environment\n * `environment-api:security-problems:read` - needed for reading security problems\n * `environment-api:entities:read` - read monitored entities\n * `environment-api:problems:read` - get problems\n * `environment-api:metrics:read` - read metrics\n * `environment-api:slo:read` - read SLOs\n * `settings:objects:read` - needed for reading ownership information and Guardians (SRG) from settings\n * `storage:buckets:read` - Read all system data stored on Grail\n * `storage:logs:read` - Read logs for reliability guardian validations\n * `storage:metrics:read` - Read metrics for reliability guardian validations\n * `storage:bizevents:read` - Read bizevents for reliability guardian validations\n * `storage:spans:read` - Read spans from Grail\n * `storage:entities:read` - Read Entities from Grail\n * `storage:events:read` - Read Events from Grail\n * `storage:system:read` - Read System Data from Grail\n * `storage:user.events:read` - Read User events from Grail\n * `storage:user.sessions:read` - Read User sessions from Grail\n\nIn addition, depending on the features you use, the following variables can be configured:\n\n* `SLACK_CONNECTION_ID` (string) - connection ID of a [Slack Connection](https://docs.dynatrace.com/docs/analyze-explore-automate/workflows/actions/slack)\n* `USE_APP_SETTINGS` (boolean, `true` or `false`; default: `false`)\n * Requires scope `app-settings:objects:read` to read settings-objects from app settings\n* `USE_WORKFLOWS` (boolean, `true` or `false`; default: `false`)\n * Requires scopes `automation:workflows:read`, `automation:workflows:write` and `automation:workflows:run` to read, write and execute Workflows\n\n## ✨ Example prompts ✨\n\nUse these example prompts as a starting point. Just copy them into your IDE or agent setup, adapt them to your services/stack/architecture,\nand 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.\n\n**Find open vulnerabilities on production, setup alert.**\n```\nI have this code snippet here in my IDE, where I get a dependency vulnerability warning for my code.\nCheck if I see any open vulnerability/cve on production.\nAnalyze a specific production problem.\nSetup a workflow that sends Slack alerts to the #devops-alerts channel when availability problems occur.\n```\n**Debug intermittent 503 errors.**\n```\nOur load balancer is intermittently returning 503 errors during peak traffic.\nPull all recent problems detected for our front-end services and\nrun a query to correlate error rates with service instance health indicators.\nI suspect we have circuit breakers triggering, but need confirmation from the telemetry data.\n```\n**Correlate memory issue with logs.**\n```\nThere's a problem with high memory usage on one of our hosts.\nGet the problem details and then fetch related logs to help understand\nwhat's causing the memory spike? Which file in this repo is this related to?\n```\n**Trace request flow analysis.**\n```\nOur users are experiencing slow checkout processes.\nCan you execute a DQL query to show me the full request trace for our checkout flow,\nso I can identify which service is causing the bottleneck?\n```\n**Analyze Kubernetes cluster events.**\n```\nOur application deployments seem to be failing intermittently.\nCan you fetch recent events from our \"production-cluster\"\nto help identify what might be causing these deployment issues?\n```\n\n## Development\n\nFor development purposes, you can use VSCode and GitHub Copilot.\n\nFirst, enable Copilot for your Workspace `.vscode/settings.json`:\n```json\n{\n \"github.copilot.enable\": {\n \"*\": true\n }\n}\n\n```\n\nSecond, add the MCP to `.vscode/mcp.json`:\n```json\n{\n \"servers\": {\n \"my-dynatrace-mcp-server\": {\n \"command\": \"node\",\n \"args\": [\n \"${workspaceFolder}/dist/index.js\"\n ],\n \"envFile\": \"${workspaceFolder}/.env\"\n }\n }\n}\n```\n\nThird, create a `.env` file in this repository (you can copy from `.env.template`) and configure environment variables as [described above](#environment-variables).\n\nLast but not least, switch to Agent Mode in CoPilot and reload tools.\n\n\n## Notes\nThis product is not officially supported by Dynatrace.\nPlease contact us via [GitHub Issues](https://github.com/dynatrace-oss/dynatrace-mcp/issues) if you have feature requests, questions, or need help.\n","url","https://github.com/dynatrace-oss/dynatrace-mcp","githubRepository",{"_132":133,"_134":135,"_136":137,"_138":139,"_33":140,"_141":142,"_147":148,"_149":150,"_152":153},"defaultBranch","main","fullName","dynatrace-oss/dynatrace-mcp","githubTreeId",122911,"language","JavaScript","dynatrace-mcp","owner",{"_143":144,"_145":146},"login","dynatrace-oss","uid","JxS4F64oCx","recentStargazers",4,"spdxLicense",{"_33":151},"MIT License","stargazers",56,"glamaJson",6331,"inspectable",false,"integrations",[160,170,177],{"_161":162,"_31":168,"_145":169},"brand",{"_163":164,"_33":165,"_166":167},"logoSvgPath","M9.372 0c-.31.006-.93.09-1.521.654-.872.824-5.225 4.957-6.973 6.617-.79.754-.72 1.595-.72 1.664v.377c.067-.292.187-.5.427-.825.496-.616 1.3-.788 1.627-.822a64.238 64.238 0 01.002 0 64.238 64.238 0 016.528-.55c4.335-.136 7.197.226 7.197.226l6.085-5.794s-3.188-.6-6.82-1.027a93.4 93.4 0 00-5.64-.514c-.02 0-.09-.008-.192-.006zm13.56 2.508l-6.066 5.79s.222 2.881-.137 7.2c-.189 2.45-.584 4.866-.875 6.494-.052.326-.256 1.114-.925 1.594-.29.198-.49.295-.748.363 1.546-.51 1.091-7.047 1.091-7.047-4.335.137-7.214-.223-7.214-.223l-6.085 5.793s3.223.634 6.856 1.045c2.056.24 4.833.429 5.227.463.023 0 .045-.007.068-.012-.013.003-.022.009-.035.012.138 0 .26.015.38.015.084 0 .924.105 1.712-.648 1.748-1.663 6.084-5.81 6.94-6.634.789-.754.72-1.594.72-1.68a81.846 81.846 0 00-.206-5.654 101.75 101.75 0 00-.701-6.872zM3.855 8.306c-1.73.002-3.508.208-3.696 1.021.017 1.216.05 3.137.205 5.28.24 3.65.703 6.887.703 6.887l6.083-5.79c-.017.016-.24-2.88.12-7.2 0 0-1.684-.201-3.416-.2z","Dynatrace","slug","dynatrace","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.","fjgdm3fij1",{"_161":171,"_31":175,"_145":176},{"_163":172,"_33":173,"_166":174},"M10.204 14.35l.007.01-.999 2.413a5.171 5.171 0 0 1-2.075-2.597l2.578-.437.004.005a.44.44 0 0 1 .484.606zm-.833-2.129a.44.44 0 0 0 .173-.756l.002-.011L7.585 9.7a5.143 5.143 0 0 0-.73 3.255l2.514-.725.002-.009zm1.145-1.98a.44.44 0 0 0 .699-.337l.01-.005.15-2.62a5.144 5.144 0 0 0-3.01 1.442l2.147 1.523.004-.002zm.76 2.75l.723.349.722-.347.18-.78-.5-.623h-.804l-.5.623.179.779zm1.5-3.095a.44.44 0 0 0 .7.336l.008.003 2.134-1.513a5.188 5.188 0 0 0-2.992-1.442l.148 2.615.002.001zm10.876 5.97l-5.773 7.181a1.6 1.6 0 0 1-1.248.594l-9.261.003a1.6 1.6 0 0 1-1.247-.596l-5.776-7.18a1.583 1.583 0 0 1-.307-1.34L2.1 5.573c.108-.47.425-.864.863-1.073L11.305.513a1.606 1.606 0 0 1 1.385 0l8.345 3.985c.438.209.755.604.863 1.073l2.062 8.955c.108.47-.005.963-.308 1.34zm-3.289-2.057c-.042-.01-.103-.026-.145-.034-.174-.033-.315-.025-.479-.038-.35-.037-.638-.067-.895-.148-.105-.04-.18-.165-.216-.216l-.201-.059a6.45 6.45 0 0 0-.105-2.332 6.465 6.465 0 0 0-.936-2.163c.052-.047.15-.133.177-.159.008-.09.001-.183.094-.282.197-.185.444-.338.743-.522.142-.084.273-.137.415-.242.032-.024.076-.062.11-.089.24-.191.295-.52.123-.736-.172-.216-.506-.236-.745-.045-.034.027-.08.062-.111.088-.134.116-.217.23-.33.35-.246.25-.45.458-.673.609-.097.056-.239.037-.303.033l-.19.135a6.545 6.545 0 0 0-4.146-2.003l-.012-.223c-.065-.062-.143-.115-.163-.25-.022-.268.015-.557.057-.905.023-.163.061-.298.068-.475.001-.04-.001-.099-.001-.142 0-.306-.224-.555-.5-.555-.275 0-.499.249-.499.555l.001.014c0 .041-.002.092 0 .128.006.177.044.312.067.475.042.348.078.637.056.906a.545.545 0 0 1-.162.258l-.012.211a6.424 6.424 0 0 0-4.166 2.003 8.373 8.373 0 0 1-.18-.128c-.09.012-.18.04-.297-.029-.223-.15-.427-.358-.673-.608-.113-.12-.195-.234-.329-.349-.03-.026-.077-.062-.111-.088a.594.594 0 0 0-.348-.132.481.481 0 0 0-.398.176c-.172.216-.117.546.123.737l.007.005.104.083c.142.105.272.159.414.242.299.185.546.338.743.522.076.082.09.226.1.288l.16.143a6.462 6.462 0 0 0-1.02 4.506l-.208.06c-.055.072-.133.184-.215.217-.257.081-.546.11-.895.147-.164.014-.305.006-.48.039-.037.007-.09.02-.133.03l-.004.002-.007.002c-.295.071-.484.342-.423.608.061.267.349.429.645.365l.007-.001.01-.003.129-.029c.17-.046.294-.113.448-.172.33-.118.604-.217.87-.256.112-.009.23.069.288.101l.217-.037a6.5 6.5 0 0 0 2.88 3.596l-.09.218c.033.084.069.199.044.282-.097.252-.263.517-.452.813-.091.136-.185.242-.268.399-.02.037-.045.095-.064.134-.128.275-.034.591.213.71.248.12.556-.007.69-.282v-.002c.02-.039.046-.09.062-.127.07-.162.094-.301.144-.458.132-.332.205-.68.387-.897.05-.06.13-.082.215-.105l.113-.205a6.453 6.453 0 0 0 4.609.012l.106.192c.086.028.18.042.256.155.136.232.229.507.342.84.05.156.074.295.145.457.016.037.043.09.062.129.133.276.442.402.69.282.247-.118.341-.435.213-.71-.02-.039-.045-.096-.065-.134-.083-.156-.177-.261-.268-.398-.19-.296-.346-.541-.443-.793-.04-.13.007-.21.038-.294-.018-.022-.059-.144-.083-.202a6.499 6.499 0 0 0 2.88-3.622c.064.01.176.03.213.038.075-.05.144-.114.28-.104.266.039.54.138.87.256.154.06.277.128.448.173.036.01.088.019.13.028l.009.003.007.001c.297.064.584-.098.645-.365.06-.266-.128-.537-.423-.608zM16.4 9.701l-1.95 1.746v.005a.44.44 0 0 0 .173.757l.003.01 2.526.728a5.199 5.199 0 0 0-.108-1.674A5.208 5.208 0 0 0 16.4 9.7zm-4.013 5.325a.437.437 0 0 0-.404-.232.44.44 0 0 0-.372.233h-.002l-1.268 2.292a5.164 5.164 0 0 0 3.326.003l-1.27-2.296h-.01zm1.888-1.293a.44.44 0 0 0-.27.036.44.44 0 0 0-.214.572l-.003.004 1.01 2.438a5.15 5.15 0 0 0 2.081-2.615l-2.6-.44-.004.005z","Kubernetes","kubernetes","Provides tools for monitoring Kubernetes clusters, retrieving problem details from services, and analyzing cluster events to troubleshoot deployment issues.","z0rdeipqh0",{"_161":178,"_31":182,"_145":183},{"_163":179,"_33":180,"_166":181},"M5.042 15.165a2.528 2.528 0 0 1-2.52 2.523A2.528 2.528 0 0 1 0 15.165a2.527 2.527 0 0 1 2.522-2.52h2.52v2.52zM6.313 15.165a2.527 2.527 0 0 1 2.521-2.52 2.527 2.527 0 0 1 2.521 2.52v6.313A2.528 2.528 0 0 1 8.834 24a2.528 2.528 0 0 1-2.521-2.522v-6.313zM8.834 5.042a2.528 2.528 0 0 1-2.521-2.52A2.528 2.528 0 0 1 8.834 0a2.528 2.528 0 0 1 2.521 2.522v2.52H8.834zM8.834 6.313a2.528 2.528 0 0 1 2.521 2.521 2.528 2.528 0 0 1-2.521 2.521H2.522A2.528 2.528 0 0 1 0 8.834a2.528 2.528 0 0 1 2.522-2.521h6.312zM18.956 8.834a2.528 2.528 0 0 1 2.522-2.521A2.528 2.528 0 0 1 24 8.834a2.528 2.528 0 0 1-2.522 2.521h-2.522V8.834zM17.688 8.834a2.528 2.528 0 0 1-2.523 2.521 2.527 2.527 0 0 1-2.52-2.521V2.522A2.527 2.527 0 0 1 15.165 0a2.528 2.528 0 0 1 2.523 2.522v6.312zM15.165 18.956a2.528 2.528 0 0 1 2.523 2.522A2.528 2.528 0 0 1 15.165 24a2.527 2.527 0 0 1-2.52-2.522v-2.522h2.52zM15.165 17.688a2.527 2.527 0 0 1-2.52-2.523 2.526 2.526 0 0 1 2.52-2.52h6.313A2.527 2.527 0 0 1 24 15.165a2.528 2.528 0 0 1-2.522 2.523h-6.313z","Slack","slack","Allows sending notification messages to Slack channels via a Slack Connector, supporting features like alerting on availability problems and security vulnerabilities.","9m5db3cpff","namespace","npmPackage",{"_33":187,"_188":189},"@dynatrace-oss/dynatrace-mcp-server","weeklyDownloads",90,"prompts","redditPostForeignId","resources","scores",{"_195":196,"_197":-5,"_198":-5},"license",100,"quality","security","simpleIcon","supportedPlatforms","tools","3pwqt25s6z","updatedAt","2025-05-30T19:02:52.658658018Z","meta",[207,210,212,219,222,224,227,230,233,236,239,241,244,247,249,251,253,255,257],{"_208":209},"title","Dynatrace MCP Server | Glama",{"_211":42,"_33":31},"content",{"_213":214,"_215":216,"_217":218},"href","https://glama.ai/mcp/servers/@dynatrace-oss/dynatrace-mcp","rel","canonical","tagName","link",{"_211":34,"_220":221},"property","og:title",{"_211":42,"_220":223},"og:description",{"_211":225,"_220":226},"https://glama.ai/logo.png","og:logo",{"_211":228,"_220":229},"https://glama.ai/mcp/servers/@dynatrace-oss/dynatrace-mcp/og-image","og:image",{"_211":231,"_220":232},"630","og:image:height",{"_211":234,"_220":235},"1200","og:image:width",{"_211":237,"_220":238},"website","og:type",{"_211":214,"_220":240},"og:url",{"_211":242,"_220":243},"Glama – MCP Hosting Platform","og:site_name",{"_211":245,"_33":246},"summary_large_image","twitter:card",{"_211":242,"_33":248},"twitter:title",{"_211":42,"_33":250},"twitter:description",{"_211":228,"_33":252},"twitter:image",{"_211":231,"_33":254},"twitter:image:height",{"_211":234,"_33":256},"twitter:image:width",{"_258":259},"script:ld+json",{"_260":261,"_262":263},"@context","http://schema.org","@graph",[264],{"_260":265,"_266":267,"_268":269},"https://schema.org","@type","BreadcrumbList","itemListElement",[270,277,281,285],{"_266":271,"_272":273,"_33":274,"_275":276},"ListItem","item","https://glama.ai/","Glama","position",1,{"_266":271,"_272":278,"_33":279,"_275":280},"https://glama.ai/mcp","MCP",2,{"_266":271,"_272":282,"_33":283,"_275":284},"https://glama.ai/mcp/servers","Servers",3,{"_266":271,"_272":214,"_33":34,"_275":148},"visitorIsMaintainer","routes/_public/mcp/servers/~namespace/~slug/_pages/reviews/_route",{"_81":-5,"_29":289,"_205":313,"_348":-5},{"_84":85,"_86":290,"_13":299,"_123":42,"_124":42,"_125":300,"_130":301,"_154":-5,"_16":155,"_156":157,"_158":304,"_33":34,"_184":144,"_185":311,"_190":-5,"_191":-5,"_192":-5,"_193":312,"_199":-5,"_166":140,"_200":-5,"_201":-5,"_145":202,"_203":204},{"_88":291,"_112":298,"_95":114},{"_90":292,"_97":293,"_100":294,"_103":295,"_106":296,"_109":297},{"_92":93,"_31":94,"_95":96},{"_31":99,"_95":96},{"_31":102,"_95":96},{"_92":93,"_31":105,"_95":96},{"_31":108,"_95":96},{"_31":111,"_95":96},[97,100,106],[116,117,118,119,120,121,122],{"_35":127,"_128":129},{"_132":133,"_134":135,"_136":137,"_138":139,"_33":140,"_141":302,"_147":148,"_149":303,"_152":153},{"_143":144,"_145":146},{"_33":151},[305,307,309],{"_161":306,"_31":168,"_145":169},{"_163":164,"_33":165,"_166":167},{"_161":308,"_31":175,"_145":176},{"_163":172,"_33":173,"_166":174},{"_161":310,"_31":182,"_145":183},{"_163":179,"_33":180,"_166":181},{"_33":187,"_188":189},{"_195":196,"_197":-5,"_198":-5},[314,316,318,320,322,323,324,325,326,327,328,329,330,331,332,333,334,335,336],{"_208":315},"Reviews | Dynatrace MCP Server | Glama",{"_211":317,"_33":31},"Read community reviews and feedback for Dynatrace MCP Server. Discover user experiences, ratings, strengths, and potential limitations of this MCP implementation from actual users.",{"_213":319,"_215":216,"_217":218},"https://glama.ai/mcp/servers/@dynatrace-oss/dynatrace-mcp/reviews",{"_211":321,"_220":221},"Reviews | Dynatrace MCP Server",{"_211":317,"_220":223},{"_211":225,"_220":226},{"_211":228,"_220":229},{"_211":231,"_220":232},{"_211":234,"_220":235},{"_211":237,"_220":238},{"_211":319,"_220":240},{"_211":242,"_220":243},{"_211":245,"_33":246},{"_211":242,"_33":248},{"_211":317,"_33":250},{"_211":228,"_33":252},{"_211":231,"_33":254},{"_211":234,"_33":256},{"_258":337},{"_260":261,"_262":338},[339],{"_260":265,"_266":267,"_268":340},[341,342,343,344,345],{"_266":271,"_272":273,"_33":274,"_275":276},{"_266":271,"_272":278,"_33":279,"_275":280},{"_266":271,"_272":282,"_33":283,"_275":284},{"_266":271,"_272":214,"_33":34,"_275":148},{"_266":271,"_272":319,"_33":346,"_275":347},"Reviews",5,"review","actionData","errors"]

Rate & Review

MCP directory API