ConvRadar — Conversion Analyst inside Claude

Created By
Pika Ivan22 days ago
Hosted MCP that turns your GA4 property into a conversation. Ask "where's my biggest funnel drop?" or "did mobile conversion drop last week?" in Claude or ChatGPT — ConvRadar pulls the right slice, runs the diagnostic, and answers with numbers and a recommended action. OAuth 2.1, no per-user URLs.
Overview

What ConvRadar does

ConvRadar is your conversion analyst, inside Claude. It's a hosted MCP server that connects to your Google Analytics 4 property over OAuth (read-only) and exposes ~20 conversion-diagnostic tools to any MCP client — Claude, ChatGPT, Cursor, Cline.

  • Runs a full audit on demand — funnel drops, traffic-quality regressions, device gaps, landing-page leaks, product/category performance.
  • Compares segments, periods, and benchmarks. Answers in plain English with the GA4 numbers attached.
  • Records hypotheses so the next conversation picks up where the last one ended.

Try without installing

Open the demo chat at https://convradar.com/chat — 3 free messages, no signup.

Pricing

$9.99 / month flat. 7-day trial, card required. Cancel anytime.

Auth

OAuth 2.1 (Bearer). Scopes: read:metrics, write:hypotheses. Discovery via /.well-known/oauth-protected-resource. No per-user URL — mcp-remote handles the login flow on first run.

First prompts to try

  • Run a full audit of my account.
  • Where's my biggest funnel drop?
  • Did mobile conversion drop last week?
  • What should I A/B test next?

Stack

GA4 Data API (read-only), Claude/ChatGPT MCP, Stripe billing.

Server Config

{
  "mcpServers": {
    "convradar": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.convradar.com/mcp"
      ]
    }
  }
}
Project Info
Created At
22 days ago
Updated At
22 days ago
Author Name
Pika Ivan
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago