Docs

Connect CrunchJunkie to ChatGPT

Add the CrunchJunkie MCP connector to ChatGPT as a custom MCP server, sign in with your CrunchJunkie account, and ask ChatGPT about your clients and AI visibility.

What you need

A ChatGPT account that can add a custom MCP server, and a CrunchJunkie account on an active paid plan. OpenAI's developer documentation does not list which ChatGPT plans can add one; it says only that account and workspace policies apply. If the option is missing, ask your ChatGPT workspace admin. The connector URL is https://app.crunchjunkie.io/api/mcp/mcp. It is also shown under Settings → Connect AI assistants (MCP) in CrunchJunkie. OpenAI has renamed this area of ChatGPT more than once (connectors, apps, developer mode, and now plugins). These steps follow OpenAI's current developer documentation; if a label on your screen differs, look for the same step.

Add the connector

1. Go to ChatGPT Plugins (chatgpt.com/plugins). 2. Select the plus button, then "Add custom MCP server". 3. Enter a name and a description. 4. Under "Connection", enter the connector URL (it ends in /mcp, as OpenAI requires for a public endpoint). 5. Choose the OAuth option for authentication; do not choose "No authentication". 6. Review the risk warning and select "I understand and want to continue". 7. Select "Create as a plugin" and review the tools ChatGPT found on the server. OpenAI's quickstart installs a plugin like this: open it on the Plugins page and select the plus button, then on the ChatGPT homepage switch the tab at the top from Chat to Work, start a new chat, type @ in the prompt box and select the plugin. We have not tested that path ourselves.

Sign in

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. OpenAI's documentation says ChatGPT supports Client ID Metadata Documents and dynamic client registration for custom servers, which are the two methods CrunchJunkie accepts.

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.

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. ChatGPT decides which of the connector's tools it shows, and OpenAI's documentation doesn't say which plans can use write tools. Account and workspace policies apply to adding and using custom MCP servers. If ChatGPT lists only read tools, ask your ChatGPT workspace admin; the connector offers the same tools to every assistant.

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 ChatGPT cannot connect, check that the URL is exactly the one above, including /api/mcp/mcp. After CrunchJunkie adds tools, select "Refresh" on the connection on the Plugins page and start a new conversation. Business and Enterprise workspaces can restrict custom MCP servers; if adding one is blocked, the workspace admin has to allow it. Other assistants are covered in the connector documentation.