Technology
Cursor
Enhance your AI coding assistant by connecting Cursor to your data on Dash0.
Overview
Cursor
Cursor is an AI-powered code editor that integrates advanced AI capabilities directly into your development workflow, enabling intelligent code completion, generation, and editing with natural language instructions. With support to MCP server, Cursor can access your telemetry data on Dash0 to enhance its coding capabilities.
Use Cases
- Telemetry-aware coding: Cursor can identify issues and performance bottlenecks in your cloud infrastructure and address them directly in the codebase.
- Incident-to-code correlation: Cursor can analyze your application code and latest commits and correlate them with logs, traces and metrics to provide deeper root-cause analysis.
Setup
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)
-
In the Cursor editor, click on the engine icon to
Open Cursor Settings, then navigate toMCP Toolsand click onAdd Custom MCP
-
Add the configuration for the Dash0 MCP server and save the file:
json{ "mcpServers": { "dash0": { "url": "{{endpoint_mcp}}" } } } -
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.
-
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:
- Go to your organization's Auth Tokens settings page
- 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
- Full access (
Tokens with limited permissions (e.g., scoped to specific datasets or with only "Ingesting" permissions) will not work with the MCP server. The MCP server requires organization-wide read access to query your telemetry data.
Then add the configuration with the Authorization header:
{
"mcpServers": {
"dash0": {
"url": "{{endpoint_mcp}}",
"headers": {
"Authorization": "Bearer {{token}}"
}
}
}
}