Cursor

Connecting Cursor to analytics.tube lets its agent check analytics while you code — confirming an error fix landed in production, checking traffic to a route before deleting it, or setting up goals and funnels for a new feature.

This page covers client setup only. The MCP overview covers the endpoint, API keys and scopes, the full tool list, and troubleshooting.

Add the server

1. Create an API key in analytics.tube.
2. Add the server to ~/.cursor/mcp.json (global — available in all projects) or .cursor/mcp.json in a project:

{
  "mcpServers": {
    "analytics.tube": {
      "url": "https://app.analytics.tube/api/mcp",
      "headers": {
        "Authorization": "Bearer <RYBBIT_API_KEY>"
      }
    }
  }
}

For a self-hosted installation, replace the host with your configured BASE_URL.

Prefer the global file for a personal key. If you configure the server in a project's .cursor/mcp.json, don't commit the key — give each developer their own, ideally scoped to what the agent needs.

Verify

Open Cursor Settings → MCP: the server should show as connected with its tool list, and can be toggled on and off there. Then ask the agent:

List my analytics.tube sites and summarize last week's traffic for each.