Skip to main content

Connect Hunch to Claude

Use this guide when you want Claude to access one website's Hunch capabilities through the Hunch MCP server.

Before you start​

Make sure all of the following are true:

  • your website is already added in Hunch
  • the widget is installed and verified on the live site
  • discovery has run, and you have reviewed the generated tools
  • the website is on a Hunch plan that allows external MCP access
  • your Claude workspace or plan currently supports custom remote MCP connectors

Anthropic can change Claude connector availability or setup screens. If the Claude UI looks different, check Anthropic's current documentation before continuing:

On Claude Team and Enterprise, the organization-level connector has to be added by an owner before individual users can connect it.

Prepare the website in Hunch​

  1. Log in to the Hunch dashboard.
  2. Open Websites.
  3. Select the website you want to expose.
  4. Open the MCP tab.
  5. Review the Capability Policies for that site.

Recommended setup:

  • keep only the capabilities you want exposed enabled
  • allow Public Execute only for public-site actions you want Hunch to run directly
  • grant live scope only when you actually need claimed live browser/session actions

The Hunch MCP page gives you:

  • the endpoint URL
  • the authorization server metadata URL
  • the protected resource metadata URL
  • the scopes supported by the website

Connect from Claude​

  1. In Claude, open the connector or custom integration setup flow.
  2. Add a remote MCP connector.
  3. Paste the Hunch endpoint URL from the website's MCP tab.
  4. Continue through the Hunch sign-in and approval flow when Claude redirects you.
  5. Approve only the scopes you want Claude to use for that website.

For most setups, start with:

  • mcp:read
  • mcp:tools

Grant mcp:live only if:

  • the Hunch plan allows it
  • you need claimed live browser/session actions
  • you are intentionally enabling live-session workflows

What Claude can do after setup​

Claude can then use the same normalized Hunch capabilities that power your widget and channels:

  • grounded answers over website knowledge
  • grounded search
  • normalized site actions such as booking, contact, quote, and lead-capture starters
  • follow-up turns for multi-step actions
  • structured handoff export when a human should take over

If live scope is present and a visitor explicitly claims a live session, Claude can also inspect and use the live-session bridge.

Test the connection​

Start with a few low-risk prompts:

  • "What tools does this Hunch website expose?"
  • "Search this website for return policy information."
  • "Start the contact-sales action."
  • "Continue the action session and confirm it."

Use one end-to-end multi-turn action to verify the installation before wider rollout.

Manage or revoke the connection​

In Hunch:

  1. Return to the website's MCP tab.
  2. Review External Installations.
  3. Revoke any Claude installation you no longer want active.

Capability policy changes take effect for future tool calls even if the installation remains active.

Common issues​

Claude rejects the connection​

Check:

  • the endpoint URL belongs to the intended website
  • the website's plan includes external MCP access
  • the approving Hunch user has permission to manage that website

Claude can read but cannot act​

Check:

  • the installation has mcp:tools
  • the capability is enabled in Capability Policies
  • the relevant site action has been discovered and normalized by Hunch

Claude cannot use live tools​

Check:

  • the plan allows mcp:live
  • the installation was approved with mcp:live
  • a visitor has connected and claimed the live session