Connect to Claude, ChatGPT & other AI assistants (MCP)

CrunchJunkie ships a Model Context Protocol (MCP) connector, so AI assistants can read your workspace data directly in a chat — your clients, connected data sources, reports and report data, and AI-visibility metrics. You can ask "summarise last month's Google Ads report for Acme" or "which prompts is Acme invisible for in ChatGPT?" and the assistant pulls the answer from your live CrunchJunkie data instead of you exporting anything. It's one server, not a set of per-vendor integrations. The same connector URL works with claude.ai, with ChatGPT (including Deep Research, which is what the connector's built-in search and fetch tools exist for) and with any other MCP-compatible client — same tools, same scopes, same safeguards, whichever one you use. Two things are true by design. It's scoped to your team: an assistant only ever sees the workspace of the account that signed in. And reading never changes anything — the read tools fetch and search, full stop. The connector can also create things for you — draft a report, add a widget, schedule a report, start tracking an AI-visibility prompt — but only after a workspace owner switches that on, and even then every change is preview-and-confirm (see "Letting an assistant take actions" below). Nothing is ever deleted, and billing, plan and account settings are out of reach entirely. The connector is available on paid plans.

Open Settings → Connect AI assistants (MCP) to find your connector URL (it looks like https://app.crunchjunkie.io/api/mcp/mcp). Add that URL as a remote MCP server in your client: • Claude (claude.ai or desktop) — Settings → Connectors → Add custom connector → paste the URL. • ChatGPT — Settings → Connectors → Add (available on Pro/Team/Enterprise), or add it as a source in Deep Research → paste the URL. • Anything else that speaks MCP — add it wherever that client takes a remote MCP server URL. There's nothing vendor-specific to configure. One ChatGPT-specific note: in a normal ChatGPT conversation, only the read tools are visible — ChatGPT hides write-capable tools unless Developer Mode is enabled (Settings → Apps & Connectors → Advanced → Developer mode; on Business workspaces an admin may need to switch it on). That's ChatGPT's policy, not a connector limitation: the same connector exposes all 20 tools in Claude. Write actions additionally require the workspace opt-in below and confirm every change with a preview first — three independent switches, so nothing can write by surprise. When you add it, the client sends you to a CrunchJunkie sign-in screen to authorise access — the same OAuth flow everywhere. You log in exactly as you do to the app, approve the access, and you're connected — no API keys to copy or manage. Because authorisation rides on your normal login, the assistant acts as you and sees only what your account can see. You can revoke access at any time from the client's connector settings. Five scopes can be requested, and you can see which were granted on the consent screen: • read:reports — list and open your reports and pull their data • read:visibility — read AI-visibility and product shopping-visibility metrics • read:clients — list your clients and their connected data sources • write:reports — create a report, add a widget, schedule a report • write:visibility — start tracking an AI-visibility prompt If you connected before the write scopes existed, your connection keeps working: tokens are only reissued when you reconnect, not when we deploy, so a write tool still accepts the read scope it originally required. Reconnect when convenient and your token picks up the accurate scope names. Either way, scope alone never changes anything — see the three gates below.

The read tools are: list your clients, list a client's connected data sources, list and open reports, pull a report's data, read AI-visibility metrics, read product-level shopping visibility (recommendation rate, head-to-head win rate and competitor products), and a general search/fetch over your workspace. A deeper analysis layer reads the per-prompt data underneath those metrics: list your tracked prompts with pooled per-prompt visibility, drill into one prompt's per-engine results and the competitors the AI actually named, see which domains the engines cite (with genuinely-cited and retrieved-only counted separately), find content gaps — prompts where your brand is absent from every recent answer while competitors are named, the same definition the Content Brief generator uses — read your Signals inbox, and pull the latest GEO Audit score with its findings. Reading is always available on a paid plan and never alters your data — there is no billing access, and no ability to change your plan, team or settings from a chat. If a tool ever returns "missing scope" or "forbidden", it usually means the signed-in account isn't on a paid plan or isn't a member of the team that owns the data. Sign in with an account that has access to the workspace you're asking about.

Reading your data is only half of what an assistant can do. If you want it to also make changes for you — "draft a Google Ads report for Acme", "schedule Acme's report every Monday at 9am", "start tracking the prompt 'best CRM for agencies' for Acme", or "add a conversions-by-device table to that report" — the connector has four action tools: create_report, add_widget and schedule_report (covered by write:reports) and add_tracking_prompt (covered by write:visibility). Every one of them is gated three times over, and all three must hold: 1. Scope — the token must carry the matching write scope (or, for connections made before those scopes existed, the read scope that tool used to require). 2. Workspace setting — "Allow write actions" must be on under Settings → Connect AI assistants (MCP). It's off by default and only an owner or admin can change it. While it's off, the connector reads and nothing more, no matter what scopes a token holds. 3. Confirmation — the tool has to be called with confirm: true. Called without it, it returns a preview of exactly what it would create — the report's widgets, the schedule's cadence and recipients, the prompt text — and changes nothing. Content the connector creates follows your workspace language. If your account language is German, a report drafted through the connector gets German section titles rather than English ones. (That's about the text CrunchJunkie writes; your assistant already replied in whatever language you asked in.) Every action is written to an audit log, stays scoped to your team, and never touches billing or account settings. You can turn actions back off at any time and the read tools keep working. It's the same grounded, catalog-checked logic as "Draft with AI" and "Ask Crunch to build a widget" in the app — so an assistant can only build things CrunchJunkie actually supports, never invent a metric or a data source.