> For the complete documentation index, see [llms.txt](https://help.rhythms.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rhythms.ai/connectivity/connectors/connect-dynatrace.md).

# Connect Dynatrace

The Dynatrace connector lets Rhythms read operational, reliability and observability data from your Dynatrace environment as context in chat and documents. Dynatrace's MCP server lives in your own environment, so a Rhythms Admin adds it once with OAuth client credentials created in Dynatrace, and then each person connects their own Dynatrace account.

Rhythms uses Dynatrace's recommended approach for MCP integrations: a confidential OAuth client with the Authorization Code grant. Tokens refresh automatically and each user's access stays scoped to their own Dynatrace permissions. For Dynatrace's own reference, see the [Dynatrace MCP server documentation](https://docs.dynatrace.com/docs/dynatrace-intelligence/dynatrace-mcp).

## Step 1: Create an OAuth client in Dynatrace (admin)

1. In Dynatrace, go to **Account Management › Identity & Access Management › OAuth clients**.
2. Create a **confidential** OAuth client with the **Authorization Code** grant type.
3. Add `https://app.rhythms.ai/mcp/auth/callback` as a redirect URI (Rhythms shows the exact callback URL for your environment in the connector dialog).
4. Set the logout URL to `https://rhythms.ai`.
5. Grant the client the scopes Rhythms requests (listed under Permissions below).
6. Copy the **Client ID** and **Client Secret**.
7. Note your environment's MCP URL. It follows this pattern: `https://‹environment-name›.apps.dynatrace.com/platform-reserved/mcp-gateway/v0.1/servers/dynatrace-mcp/mcp`

## Step 2: Add the connector in Rhythms (admin)

1. Go to **Settings › Workspace › Connectors** and select the **Dynatrace** tile. The **Add Dynatrace connector** dialog opens.
2. Give the connector a name and paste your environment's MCP URL into **Dynatrace MCP URL**.
3. Expand **Advanced settings** and enter the **Client ID** and **Client Secret** from Dynatrace. Both are required for Dynatrace.
4. Click **Connect** and sign in to Dynatrace to authorize.

By default only Rhythms Admins can add connectors of this kind; an admin can allow all members to do so from the Connectors settings page.

## Step 3: Individual users connect

Once the connector exists, each person opens **My connectors**, finds Dynatrace, clicks **Connect** and signs in to Dynatrace with their own account. Nobody else needs the client secret.

## Permissions

Rhythms requests these scopes, so the OAuth client must be allowed to issue them:

`mcp-gateway:servers:invoke`, `mcp-gateway:servers:read`, `ai:operator:execute`, `davis-copilot:conversations:execute`, `davis-copilot:nl2dql:execute`, `davis-copilot:dql2nl:execute`, `davis-copilot:document-search:execute`, `davis:analyzers:read`, `davis:analyzers:execute`, `document:documents:read`, `storage:bizevents:read`, `storage:buckets:read`, `storage:system:read`, `storage:spans:read`, `storage:entities:read`, `storage:user.events:read`, `storage:user.sessions:read`, `storage:user.replays:read`, `storage:smartscape:read`

A user's effective access is the intersection of these scopes and that user's own Dynatrace permissions.

## Troubleshooting

* If the connection fails, first check that the OAuth client allows every scope above and that the redirect URI matches exactly.
* Then check that the Client ID and Client Secret entered under Advanced settings are correct. Wrong scopes and wrong credentials are the two most common causes.

## Related articles

* [Enable Connectors for Your Workspace](/connectivity/manage-connectors-for-your-workspace.md)
* [Shared Connectors](/connectivity/share-a-connector-with-your-team.md)
* [Manage connectors for your workspace](/connectivity/manage-connectors-for-your-workspace.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.rhythms.ai/connectivity/connectors/connect-dynatrace.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.