Skip to content

Use it from Claude Desktop

This tutorial connects Claude Desktop to the Analytics MCP gateway so you can ask questions about Volāre’s analytics in plain language.

  • Claude Desktop installed and signed in.
  • A Google account on byvolare.com or gocimit.com (access is restricted to these domains).
  1. Open Claude Desktop and go to Settings → Connectors (also called Custom connectors / MCP servers).

  2. Click Add custom connector.

  3. Fill in:

    • Name: Volare Analytics (anything you like).

    • URL:

      https://analytics.byvolare.com/mcp/analytics

    This is the aggregated endpoint — it gives Claude every source at once (Google Analytics, Clarity, and the Volāre database). If you only want one source, use /mcp/ga, /mcp/clarity, or /mcp/db instead.

  4. Click Add / Connect.

When you connect, Claude opens a browser window for Sign in with Google:

  1. Choose (or sign in with) your @byvolare.com or @gocimit.com account.
  2. Approve the access request.
  3. The window closes and the connector shows as Connected in Claude Desktop.

Accounts outside the allowed domains are rejected. No token or API key needs to be entered manually — the Google sign-in handles authentication.

Start a new chat and ask anything analytics-related. Claude will pick the right tools automatically. Examples:

  • “How many users visited the site from paid traffic last week, by market?” (Google Analytics)
  • “Show me the longest Clarity session recordings from the last 7 days.” (Microsoft Clarity)
  • “List all active products for Spain, their lead price, and how many active offers each has.” (Volāre database)
  • “For Spain, which active products get paid traffic and what’s their lead price?” (combines Google Analytics + the database)

On the aggregated endpoint the tools are namespaced by source (ga__…, clarity__…, db__…), so you can also tell Claude explicitly which source to use if you want.

The gateway is a standard remote (Streamable HTTP) MCP server with OAuth, so it also works with other MCP clients — for example the Codex CLI:

Terminal window
codex mcp login --url https://analytics.byvolare.com/mcp/analytics

The OAuth callback uses localhost, which the gateway already allows, so the Google sign-in flow works the same way from the CLI.