Connect CrunchJunkie to Cursor

Cursor and a CrunchJunkie account on an active paid plan. Cursor's documentation does not tie remote MCP servers to a particular Cursor plan; teams can restrict servers with an allowlist, so an admin may have to approve the URL. The connector URL is https://app.crunchjunkie.io/api/mcp/mcp. It is also shown under Settings → Connect AI assistants (MCP) in CrunchJunkie.

Cursor reads MCP servers from an mcp.json file: ~/.cursor/mcp.json for every project, or .cursor/mcp.json in a project. Add the server with the url key: { "mcpServers": { "crunchjunkie": { "url": "https://app.crunchjunkie.io/api/mcp/mcp" } } } Do not add headers or an auth block. CrunchJunkie supports dynamic client registration, which Cursor uses by default for servers that need OAuth. You can also manage MCP servers from Customize in Cursor's sidebar.

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. Cursor's documentation says Cursor handles authentication for servers that support OAuth, but does not describe the prompt itself. If no sign-in starts, open the server in Cursor's MCP settings and look for a button to connect or sign in.

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. Use the agent chat, not an inline edit.

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.

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). To see connection and sign-in errors, open the Output panel (Cmd+Shift+U on macOS) and select "MCP Logs". Check that the JSON is valid and the file is in the right place. Other assistants are covered in the connector documentation.