Docs
Connect CrunchJunkie to Claude Code
Add the CrunchJunkie MCP connector to Claude Code with one command, sign in with your CrunchJunkie account, and query your clients and AI visibility from the terminal.
What you need
Claude Code installed and signed in, and a CrunchJunkie account on an active paid plan. The connector URL is https://app.crunchjunkie.io/api/mcp/mcp. It is also shown under Settings → Connect AI assistants (MCP) in CrunchJunkie.
Add the connector
Run this in your terminal:
claude mcp add --transport http crunchjunkie https://app.crunchjunkie.io/api/mcp/mcp
The name (crunchjunkie) is yours to choose. By default the server is stored for you and the current project only. Add --scope user to make it available in all your projects, or --scope project to write it to the project's .mcp.json so your team shares it (Claude Code asks each person to approve a project server before using it).
Sign in
Inside Claude Code, run /mcp and follow the steps in your browser. From a shell you can run claude mcp login crunchjunkie instead. Over SSH, where no local browser is available (connect with ssh -t so the paste step works), the command prints the authorization URL: open it on your own machine, then paste the full redirect URL from the browser's address bar back at the prompt. Add --no-browser to force that mode.
When the assistant first uses the connector, it sends you to a CrunchJunkie sign-in page. You sign in with your CrunchJunkie account, the same way you sign in to the app (email and password, Google, or your company's SSO), and approve the access. There is no API key to copy or store. The sign-in is OAuth 2.1 through WorkOS AuthKit, and the assistant registers itself with dynamic client registration or a Client ID Metadata Document, so you enter no client ID or secret.
The connection acts as you and sees only what your account can see, in one workspace at a time. Until you choose, that is the workspace you joined first. To change it, open Settings → Connect AI assistants (MCP), or ask the assistant to list your workspaces and switch. If your company requires SSO, connect after signing in with SSO.
Claude Code stores the tokens and refreshes them automatically. To sign out, use "Clear authentication" in the /mcp menu or run claude mcp logout crunchjunkie.
Check that it works
Start a new chat with the connector switched on and ask:
"List my clients."
You should get your CrunchJunkie clients back. Then try a real question:
"How visible was <brand> in AI answers over the last 30 days, with sample sizes?"
Replace <brand> with one of your clients. The answer comes from your live data and quotes how many AI answers each percentage is based on. If the assistant answers from general knowledge instead of calling a CrunchJunkie tool, tell it to use the CrunchJunkie connector.
Run /mcp to see whether the server shows as connected.
Write actions
Reading never changes anything. Write actions (creating a report, adding a widget, tracking a prompt and the like) are off until a workspace owner or admin switches on "Allow write actions" under Settings → Connect AI assistants (MCP). Even then, every write tool first returns a preview and changes nothing until you confirm it, and a member with the Read only role cannot make changes at all. The full rules are in the connector documentation.
If it doesn't work
The CrunchJunkie sign-in page never opens, or the assistant says it is not signed in: remove the connector and add it again, and check that the URL is exactly https://app.crunchjunkie.io/api/mcp/mcp.
A tool answers "missing scope" or "forbidden": the account you signed in with is not on an active paid plan, or is not a member of the workspace that owns the data. Sign in with an account that has access. If your account belongs to several workspaces, the assistant may be working in another one; ask it to list your workspaces.
Write tools are refused: write actions are off by default. A workspace owner or admin switches them on under Settings → Connect AI assistants (MCP).
If the browser does not open, copy the URL from the terminal and open it yourself. If the redirect fails with a connection error after you sign in, paste the full callback URL from the address bar into the prompt in Claude Code. Runs in non-interactive mode (claude -p) and Agent SDK runs cannot complete the sign-in, so sign in first from an interactive session. To start over, run claude mcp remove crunchjunkie, which also deletes the stored tokens and client registration, and add the server again. Other assistants are covered in the connector documentation.
Getting started Reporting Report templates Filtering, dimensions & comparisons Sharing & delivering reports White-label & branding Metrics glossary AI visibility Your own AI API keys Perception AI Shopping Visibility GEO Audit AI crawlers & crawlability Rank Tracker AI traffic from GA4 Monitoring Signals & Automations Integrations Looker Studio Connect to Claude & ChatGPT (MCP) Connect Claude Connect ChatGPT Connect Cursor Connect VS Code REST API Webhooks Single sign-on (SSO) Account & billing Data, privacy & security The Crunch assistant Refer a friend FAQ