Kiwi
Kiwi

Kiwi for Dynatrace

Have the agent on a Kiwi step investigate a Dynatrace problem with DQL queries and cite what it found, through the Dynatrace MCP server.

  • Your agent works in Dynatrace through its own connection. Kiwi does not call Dynatrace and never holds its credentials.
  • A workflow skill can list Dynatrace among the tools it requires. When you supply your agent's available tools to a skill check and Dynatrace is not among them, the check reports SK15-UNSUPPORTED-TOOL.
  • A project Admin can add links to Dynatrace, with notes, under Connections and bind them to the steps that use them. The agent reads them with list_connections.
  • The agent can report the tools and plugins it ran with, including its Dynatrace connection, with report_configuration.
  • The agent submits links to its work in Dynatrace as the step's outputs. People review them, and sign-off stays with the people your workflow names.

What your agent can do in Dynatrace

  • Generate a DQL query from a plain-language question, explain it and run it.
  • Read the problems and security vulnerabilities Dynatrace has detected.
  • Read Kubernetes events for a cluster.
  • Forecast how a timeseries metric will develop.

Set up

  1. Connect your agent to Kiwi

    Add Kiwi's hosted MCP server, https://kiwiflow.io/mcp, to your coding agent.

    Coding agentsQuickstart

  2. Connect your agent to Dynatrace

    Add the Dynatrace MCP server to your agent with this URL. The credentials stay with your agent.

    https://{environment-name}.apps.dynatrace.com/platform-reserved/mcp-gateway/v0.1/servers/dynatrace-mcp/mcp

    Dynatrace documentation

  3. Example skill

    Publish instructions like these as a workflow skill that lists Dynatrace among its required tools.

    Take the Dynatrace problem ID and the affected service from the inputs.
Read the problem in Dynatrace, then write and run DQL queries over the
service's logs and spans for the problem's time range.
Submit the DQL queries and a short summary of the findings as outputs.
If a query still returns no data after 2 attempts, stop and report a blocker.
Leave decisions about the problem to the run's Owner.
Get startedRead the setup guide