Cursor

Overview

Cursor can be connected to Dash0 using our hosted MCP server, allowing it to get context about your telemetry data, navigate and analyze it, while leveraging the same capabilities that human users have access to in the UI.

Authentication

The Dash0 MCP server supports two authentication methods:

• OAuth 2.0 (recommended) — browser-based consent on first connection, no static token to manage. Access tokens refresh automatically every 15 minutes.
• Auth token (Bearer) — best for CI/CD pipelines, scripts, and headless environments where browser-based consent is impractical.

For more details on token lifecycle, audit logs, and revocation, see the Dash0 MCP Server integration.

Configure

Option 1: OAuth 2.0 (Recommended)

1. In the Cursor editor, click on the engine icon to Open Cursor Settings, then navigate to MCP Tools and click on Add Custom MCP

2. Add the configuration for the Dash0 MCP server and save the file:

3. On first use, Cursor opens a browser window where you log in to Dash0 and grant consent. You can review and revoke connected applications under User Settings → Applications in Dash0.

4. Confirm that the Dash0 MCP server has been configured

Option 2: Auth Token

Before configuring the Dash0 MCP server with a Bearer token, create an auth token with the correct permissions:

1. Go to your organization's Auth Tokens settings page
2. Create a new auth token with one of the following permission levels:
   • Full access (*) - Recommended for full MCP functionality
   • Read-only (*:read) - For read-only access to your telemetry data

Then add the configuration with the Authorization header: