MCP Documentation

ConvRadar uses OAuth 2.1 with PKCE. There are no per-user URLs and no manual API key — the client walks the discovery handshake on the protected resource and is redirected to the authorization server on first call.

The two scopes the server requests:

• read:metrics — read GA4 metrics, dimensions, funnel data and traffic breakdowns. Required for every diagnostic tool.
• write:hypotheses — store and retrieve hypotheses tied to the account so future conversations resume where the last one ended.

The downstream OAuth to Google asks only for read-only GA4 access. ConvRadar cannot modify your analytics data.

Stdio-only clients (Claude Desktop, Cursor, Cline, Continue) connect through mcp-remote, which handles the OAuth handshake the first time you call a tool. Add this block to the client's MCP config:

{
  "mcpServers": {
    "convradar": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.convradar.com/mcp"]
    }
  }
}

Web clients use a native connector menu:

• Claude.ai — Settings → Connectors → Add custom connector. URL: https://mcp.convradar.com/mcp. OAuth is handled automatically.
• ChatGPT (Plus / Pro) — Settings → Connectors → Add custom MCP connector with the same URL.
• Glama, Smithery — add the connector through the registry UI; both walk the OAuth flow for you.

On first tool call a browser window opens to authorize the Google account that owns your GA4 property. The token is stored by the client and refreshed automatically.