Connecting Dynatrace to Rhythms

Last updated: August 13, 2026

The Dynatrace connector lets Rhythms pull operational, reliability, and observability data from your Dynatrace tenant.

Rhythms connects using Dynatrace’s recommended approach for MCP integrations: a confidential OAuth client with the Authorization Code grant type. This allows access tokens to refresh automatically, avoids manual token management, and keeps each user’s access scoped to their own Dynatrace permissions.

For additional Dynatrace reference material, see the Dynatrace MCP server documentation.

Setup happens in two stages: a one-time admin setup, followed by individual user connections.

Step 1: Admin setup in Dynatrace

  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.

  4. Set the logout URL to https://rhythms.ai.

  5. Grant the OAuth client the scopes listed in the Dynatrace MCP documentation.

  6. Copy the Client ID and Client Secret.

  7. Confirm your tenant MCP URL. It should follow this format:
    https://{environment-name}.apps.dynatrace.com/platform-reserved/mcp-gateway/v0.1/servers/dynatrace-mcp/mcp

Step 2: Admin setup in Rhythms

  1. In Rhythms, go to Connectors.

  2. Select Dynatrace.

  3. Enter your tenant MCP URL.

  4. Under Advanced settings, enter the Client ID and Client Secret from Dynatrace.

  5. Click Connect and authorize access.

Step 3: Individual users connect

After an admin completes the connector setup, each user can connect their own Dynatrace account through OAuth directly from Rhythms. Users do not need to enter credentials manually.

Permissions

Access is scoped to each user’s own Dynatrace permissions. Users need:

  • mcp-gateway:servers:invoke

  • mcp-gateway:servers:read

  • Read permissions for the data they need to query, such as storage:logs:read for logs

The effective access is the intersection of the OAuth client’s scopes and the individual user’s permissions.

Troubleshooting

If the connection fails or breaks, check the following first:

  • Verify that the OAuth client has the required permission scopes.

  • Double-check that the Client ID and Client Secret entered in Rhythms are correct.

Incorrect scopes or incorrect client credentials are the most common causes of connectivity issues.