Step-by-step setup to connect the Scrunch MCP server to Claude, ChatGPT, Perplexity, Cursor, VS Code, or Microsoft Copilot Studio using OAuth in 5 minutes.
All setup flows connect to the same server and use the same OAuth sign-in — your Scrunch account credentials, no API key required. Pick your AI client below.
MCP server URL:https://app.scrunchai.com/api/mcpAll platforms below use this URL. Authentication happens via Scrunch’s standard OAuth sign-in flow; no API key or shared secret is needed.
Chat assistants
Coding tools
Enterprise platforms
Claude
ChatGPT
Perplexity
Grok
Custom connectors work across Free, Pro, Max, Team, and Enterprise Claude plans. How you add Scrunch depends on whether you’re on a personal plan or part of a Team or Enterprise organization.
Personal (Free, Pro, Max)
Free plans are limited to one active custom connector at a time.
1
Open Customize
In the Claude web app (claude.ai) or Claude desktop app, click Customize in the sidebar navigation.
2
Go to Connectors
In the Settings sidebar, select Connectors. You’ll see built-in connectors (Google Drive, Slack, Notion, etc.) followed by any custom connectors you’ve already added.
3
Add a custom connector
Click the + button and select Add custom connector.
4
Fill in the connector details
In the dialog that opens, enter:
Name:Scrunch AI (or whatever you’d like to call it)
Remote MCP server URL:https://app.scrunchai.com/api/mcp
OAuth Client ID / Client Secret: Leave blank. These are only needed if you’re hosting your own OAuth provider.
5
Click Add, then sign in to Scrunch
Claude redirects you to Scrunch to authenticate. Sign in with your Scrunch account, approve the connection, and Claude returns to the Connectors page with the connector active.
Team & Enterprise — Owners
On Team and Enterprise plans, only owners can add custom connectors. Once added, the connector becomes available for all members in your organization to enable.
1
Open Organization settings
In the Claude web app (claude.ai) or Claude desktop app, go to Organization settings → Connectors, under Libraries & Access. Owners add org-wide connectors here — not from the personal Customize page.
2
Add a custom connector
Click + Add, hover over Custom, then select Web.
3
Fill in the connector details
In the dialog that opens, enter:
Name:Scrunch AI
Remote MCP server URL:https://app.scrunchai.com/api/mcp
OAuth Client ID / Client Secret: Under Advanced settings, leave both blank. Scrunch supports OAuth Dynamic Client Registration, so Claude registers itself.
Connection methods: leave Individual sign-in on. Each member then signs in with their own Scrunch account, so brand access and permissions follow the individual — not you.
4
Click Add, then sign in to Scrunch
Claude redirects you to Scrunch to authenticate. Sign in with your Scrunch account and approve the connection. The Scrunch connector is now available for members in your organization.
Team & Enterprise — Members
Regular members on Team and Enterprise plans cannot add custom connectors — that’s restricted to org owners. Once an owner has added Scrunch, you can enable it for your own account.
1
Ask an owner to add Scrunch
Have an org owner follow the Team & Enterprise — Owners tab to add the Scrunch connector. They only need to do this once for the whole organization.
2
Open Customize → Connectors
Once the connector has been added, go to Customize → Connectors in your Claude account. Scrunch AI will appear in the list.
3
Connect and authenticate
Find Scrunch AI in the list — it carries a Custom label — and click Connect. Claude redirects you to Scrunch to sign in with your own Scrunch account. Your individual brand access and permissions are determined by your Scrunch account — not the owner’s.
Enabling the connector in a chat — When you start a new conversation, click the connector icon in the message composer and toggle Scrunch AI on for that chat. To enable it by default for all new chats, go to Settings → Connectors → Configure on the Scrunch AI connector.
Requires a paid ChatGPT plan (Plus, Pro, Team, Enterprise, or Edu). Plus and Pro accounts get read-only access; Team, Enterprise, and Edu accounts get full read + write access.
Critical: You must remove openid from the OAuth scopes in two separate places during setup (steps 5 and 6 below). If you miss either one, authentication will fail.
1
Open Settings → Apps → Advanced Settings
Click your profile picture in ChatGPT and choose Settings. Open the Apps tab, then click Advanced Settings at the bottom.
2
Enable Developer Mode
In Advanced Settings, toggle Developer Mode on. Workspace owners can also enable this org-wide under Workspace Settings → Permissions & Roles → Connected Data → Developer mode.
3
Go back to Apps and find Create app
Navigate back to the main Apps tab. With Developer Mode enabled, a Create app widget appears.
4
Create a new app
Click Create app and fill in:
Name / icon / description: Anything you like — Scrunch AI works well.
MCP Server URL:https://app.scrunchai.com/api/mcp
Authentication: OAuth
5
Remove openid from Scopes
Inside the Create app form, expand Advanced settings. In the Scopes field, deselect or delete openid. Leave all other default scopes.
6
Remove openid from OIDC scope supported
Still in Advanced settings, scroll to the bottom. Find the OIDC scope supported field and delete openid from that field as well. Both removals are required.
7
Confirm and create
Check the trust acknowledgment and click Create. ChatGPT redirects you to Scrunch to authenticate. Sign in and approve the connection.
8
Use it in a chat
In any new chat, click the apps / + menu in the composer, choose Developer mode, and select Scrunch AI.
Plan limits — Plus and Pro accounts have read-only access. Features like list_brands and get_presence_metrics work on any plan, but operations that modify data — create_brand, archive_prompt, update_tags — require a Team, Business, Enterprise, or Edu workspace.
Custom remote connectors require a Perplexity Pro, Max, or Enterprise plan. On Enterprise, an admin has to enable custom connectors before members can add their own.
1
Open Connectors
For your own account, go to Account settings → Connectors. Enterprise admins adding Scrunch for the whole organization go to Enterprise settings → Permissions → Connectors permissions instead.
2
Add a custom connector
Click + Custom connector in the top-right corner, then select Remote in the dialog.
3
Fill in the connector details
Enter:
Name:Scrunch AI
MCP Server URL:https://app.scrunchai.com/api/mcp
Description:AI brand monitoring and analytics (optional, but it helps Perplexity decide when to reach for Scrunch)
Authentication: OAuth — leave Client ID and Client Secret empty. Scrunch supports Dynamic Client Registration, so Perplexity registers itself.
Transport: Streamable HTTP
4
Acknowledge and add
Check the acknowledgement box confirming you understand the risks of custom connectors, then click Add. Scrunch AI appears in your Connectors list.
5
Authenticate
Click the Scrunch AI connector card to start the sign-in flow. Sign in with your Scrunch account and approve the connection.
Enterprise rollout — adding a connector doesn’t share it. The creator has to share it with the organization from the Permissions screen in Enterprise settings before teammates can see it, and org-wide connectors may take a moment to appear for everyone. An admin can either authenticate once on the organization’s behalf or require each member to sign in individually — require individual sign-in, so each person’s brand access and permissions come from their own Scrunch account.
Grok (grok.com / xAI) supports custom MCP connectors on all paid plans. Free users may have limited or no access to custom connectors.
Click New Connector (or the equivalent + button), then select Custom.
3
Fill in the connector details
Enter:
Name:Scrunch AI (or your preferred name)
MCP Server URL:https://app.scrunchai.com/api/mcp
Leave any OAuth Client ID / Secret fields blank unless instructed otherwise (Scrunch handles authentication via its standard OAuth flow).
4
Save and authenticate
Click Add / Create. Grok will redirect you to Scrunch to sign in with your Scrunch account and approve the connection. Once approved, the connector becomes active.
Enabling in a chat — In a new conversation, look for the connector / tools icon or sidebar. Toggle Scrunch AI on for that chat. You can set it as default for new chats in the connector settings.
MCP server URL:https://app.scrunchai.com/api/mcp
Authentication uses Scrunch’s standard OAuth sign-in. No API key is required.
Claude Code
Cursor
VS Code
Windsurf
Claude Code is the Claude CLI tool. Run the following command in your terminal:
claude mcp add scrunch --transport streamable-http https://app.scrunchai.com/api/mcp
Claude Code will prompt you to authenticate with your Scrunch account the first time you use a Scrunch tool in a session.Verify the connection:
List my Scrunch brands
Your assistant should respond with the brands accessible in your Scrunch org.
Cursor manages MCP servers from the Customize page in the sidebar. Marketplace plugins install with one click; a custom remote server like Scrunch is added by creating an mcp.json file.
1
Create your mcp.json
Add .cursor/mcp.json in your project root for a single project, or ~/.cursor/mcp.json in your home directory to make Scrunch available in every workspace:
The url field is what marks this as a remote server — there’s no transport type to choose. Scrunch serves Streamable HTTP.
2
Authenticate
Save the file. On first use, Cursor prompts you to sign in with your Scrunch account over OAuth. You don’t need a Client ID or Client Secret — Scrunch supports OAuth Dynamic Client Registration, so Cursor registers itself.
3
Check it in Customize
Open Customize in the sidebar and select the MCPs filter. Once Cursor has read the file and you’ve signed in, scrunch appears under Connected with its full tool count — this is also where you toggle it off when you don’t need it.
Still seeing the Connect External Tools with MCP empty state instead? Cursor hasn’t picked up your mcp.json yet — check that the file is saved, then reopen Customize.
Verify the connection:
List my Scrunch brands
Keep the scopes list — don’t drop the auth block. Without it, Cursor discovers scopes automatically and requests openid, which Scrunch’s sign-in flow rejects. Authentication then stalls on Waiting for callback… and your browser shows “Authorization session ended.” Pinning the three scopes above is what makes the flow complete.You still don’t need a CLIENT_ID or CLIENT_SECRET — Scrunch supports Dynamic Client Registration, so Cursor registers itself. scopes is the only auth field required.
Already hit the error? Cursor caches the registration it made the first time, so fixing mcp.json alone isn’t enough. Open the server’s Configure dialog and click Reload to re-register with the corrected scopes.
Looking at Cursor Settings → Tools & MCPs? That page is being retired — a banner at the top of it now points you to Customize. Either surface manages the same servers, but mcp.json is the only place to add a custom remote server like Scrunch; there’s no form for it.
Team and Enterprise customers — a Cursor admin can distribute Scrunch to everyone instead of each person writing their own mcp.json. Add the server under Dashboard → Integrations & MCP, then choose Add to Team Marketplace so teammates can install it from Customize. Each teammate still signs in with their own Scrunch account, so brand access and permissions stay per-user.
Create a .vscode/mcp.json file in your workspace root with the following content:
Save the file. VS Code (with GitHub Copilot) will detect the MCP configuration and prompt you to authenticate with Scrunch on first use.
To share the configuration across your team, commit .vscode/mcp.json to your repository.
1
Open Windsurf Settings
Go to Windsurf Settings → MCP.
2
Add the Scrunch server
Click Add server and enter:
Name:scrunch
Server URL:https://app.scrunchai.com/api/mcp
Transport type: Streamable HTTP
3
Authenticate
Save and restart Windsurf if prompted. On first use, Windsurf will redirect you to authenticate with your Scrunch account.
Verify the connection:
List my Scrunch brands
Copilot Studio
Microsoft Copilot Studio lets you attach the Scrunch MCP to any custom agent. You’ll need an agent already created before connecting Scrunch to it.
Prerequisite: the agent must have generative orchestration turned on. MCP tools are unavailable without it.
1
Open your agent
In Microsoft Copilot Studio, open the agent you want to extend with Scrunch. From the agent’s left navigation, choose Tools.
2
Add a new tool
Click + Add a tool. In the dialog, choose New tool, then select Model Context Protocol. This launches the MCP onboarding wizard.
3
Fill in the wizard
Provide:
Server name:Scrunch AI
Server description:AI brand monitoring and analytics
Server URL:https://app.scrunchai.com/api/mcp
The description matters — the agent’s orchestrator uses it to decide whether to call Scrunch at runtime.
4
Choose OAuth 2.0 → Dynamic discovery
For Authentication, select OAuth 2.0, then set the Type to Dynamic discovery. Scrunch supports Dynamic Client Registration with discovery, so Copilot Studio finds the endpoints and registers itself — you don’t need to enter a Client ID, Client Secret, or any URLs.
5
Authenticate
Click Create, then Next. On the Add tool dialog, choose Create a new connection. Copilot Studio redirects you to Scrunch to authenticate — sign in with your Scrunch account and approve the connection.
6
Add features to your agent
After connecting, you’ll see the full list of Scrunch features. Select which ones the agent should have access to, click Add to agent, then save and publish your agent.
Editing the connector later — If you need to update the connector details (e.g., swap to a different Scrunch account), open Power Apps → Custom connectors, find the Scrunch entry, and update there. The change propagates back into Copilot Studio automatically.
