Dynatrace MCP server

What the model can do

Dynatrace observability: problems with root cause, affected entities and comments, events, monitored hosts and services, metric queries and SLO status for one environment. Can comment on a problem, edit or delete a comment, close a problem with a closing comment, and record an annotation, deployment, configuration or info event on entities.

Reads

• dynatrace_list_problemsDynatrace problems in a time window (default the last 24 hours), newest first: display id (P-…), title, status, severity, impact, start and end…
• dynatrace_get_problemOne Dynatrace problem by its id (the long id from dynatrace_list_problems, not the P-number): everything in the list plus evidence…
• dynatrace_problem_commentsThe comments on one Dynatrace problem, with author and time.
• dynatrace_list_eventsDynatrace events in a time window (default the last 24 hours): deployments, configuration changes, availability and error events and the like…
• dynatrace_list_entitiesMonitored Dynatrace entities of one type (HOST, SERVICE, APPLICATION, PROCESS_GROUP, KUBERNETES_CLUSTER…) seen in the last 3 days by default…
• dynatrace_query_metricsQuery Dynatrace metrics over a window (default the last 2 hours): a metric selector such as builtin:host.cpu.usage or…
• dynatrace_list_slosDynatrace service-level objectives, evaluated over their own timeframe: name, target, warning threshold, current percentage, error budget, status…

Acts, when you ask

These change something in Dynatrace. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• dynatrace_add_problem_commentAdd a comment to a Dynatrace problem.
• dynatrace_edit_problem_commentReplaces the text (and optionally the context label) of a comment on a Dynatrace problem.
• dynatrace_delete_problem_commentPermanently deletes a comment from a Dynatrace problem.
• dynatrace_close_problemCloses a Dynatrace problem and adds the closing comment, which everyone who can see the problem sees.
• dynatrace_record_eventRecords a custom event in Dynatrace on the given entities (or on the environment itself if none are given): an annotation, a deployment…

Connect it

First connect Dynatrace on Dashboard → Connections, then add Memtro to your client once. The Dynatrace tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Dynatrace connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › What caused the alert on the checkout service last night?
• › Which Dynatrace problems are still open, and what is the root cause of each?
• › Was there a deployment on the payments service before the error rate went up?
• › Which SLOs are in warning or failing, and how much error budget is left?
• › Record a deployment event on the checkout service for release 4.2

Questions

Is this an official Dynatrace MCP server?

No. It is Memtro's MCP server with Memtro's Dynatrace connector behind it: the connector reads Dynatrace through its API with the credentials you connect on Dashboard → Connections, and Dynatrace publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Dynatrace?

Only when you ask, and only what it has been granted: add a comment to a problem; edit a comment on a problem; delete a comment from a problem (permanent); close a problem with a closing comment; record an annotation, deployment, configuration or info event on entities (consumes Davis Data Units). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server