Skip to main content

Make a Hunch Website Usable From Claude

Use this guide when you want visitors to use a Hunch-enabled website from Claude through the public visitor connector.

Claude can connect via OAuth 2.1 with Dynamic Client Registration (recommended) or with no authentication (simpler fallback). Both use the same public connector URL. The website owner turns on public visitor access in Hunch and reviews the exposed website actions and workflow skills.

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 public workflows have been mapped
  • you reviewed which actions should be available to outside AI visitors
  • your Claude plan or workspace supports custom connectors using remote MCP

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

Enable Public AI Access in Hunch​

  1. Log in to the Hunch dashboard.
  2. Open Websites.
  3. Select the website you want Claude users to reach.
  4. Open Public AI Access.
  5. Set Public Access Mode:
  • Off blocks public AI access.
  • Unlisted allows access only to people with the public connector URL.
  • Listed allows the site to appear in Hunch's public connector directory.
  1. Review Website Action Controls.
  2. Disable any action you do not want public AI visitors to use.
  3. Review Visitor Security. Use signed visitor tokens, challenge mode, referrer rules, blocked visitor hashes, and a max risk score when the connector should not be fully open to anyone with the URL.
  4. Save your settings.
  5. Copy the Public Connector URL.
  6. Optionally use Remote MCP Readiness to:
  • run the connector smoke test
  • copy an install package
  • validate a CIMD document
  • review recent install health

Connect From Claude​

The public connector URL looks like this:

https://api.hunchbank.com/public-mcp/{website_id}

Option A — OAuth (Recommended)​

  1. In Claude, open the connector or custom integration setup flow.
  2. Add a custom remote MCP connector.
  3. Paste the Public Connector URL from Hunch.
  4. Claude discovers OAuth metadata automatically via the server's RFC 8414 well-known endpoint and handles Dynamic Client Registration.
  5. When prompted, you are redirected to a Hunch consent page. The website owner approves the connection.
  6. After approval, Claude receives OAuth tokens with mcp:read and mcp:tools scopes and can make authenticated requests.

Option B — No Authentication (Fallback)​

  1. In Claude, open the connector or custom integration setup flow.
  2. Add a custom remote MCP connector.
  3. Paste the Public Connector URL from Hunch.
  4. Choose No authentication when Claude asks for an authentication mode.
  5. Save the connector and test it.

How Users Discover and Access the Connector​

Custom connectors use remote MCP and connect from Anthropic's cloud, not the user's device — the Hunch server must be publicly reachable. The feature is currently in beta.

Anyone can add the connector directly​

Any Claude user (Free, Pro, Max, Team, or Enterprise) can add the Hunch connector as a custom connector:

  1. Go to Customize > Connectors (or claude.ai/customize/connectors).
  2. Click "+" then "Add custom connector."
  3. Enter a name and the URL (https://api.hunchbank.com/public-mcp/{website_id}).
  4. Claude detects OAuth support and handles the consent flow, or use no-auth for simpler access.
  5. Enable the connector per conversation from the "+" menu.

Free users can add one custom connector.

Submit to the Claude Connectors Directory​

To make the Hunch connector discoverable to all Claude users in the Connectors Directory, submit it to Anthropic for review. Directory connectors appear alongside verified first-party connectors and are browsable by category.

For submission details, contact Anthropic through their official connector submission process.

Team and Enterprise setup​

On Team and Enterprise plans, an Owner or Primary Owner must first add the connector to the organization:

  1. Go to Organization settings > Connectors.
  2. Click "Add", hover over "Custom", select "Web."
  3. Enter the Hunch server URL.
  4. Members then go to Customize > Connectors, find the connector, and click "Connect" to authenticate individually.

Connectors are only available in private projects on Team and Enterprise plans.

Claude plan eligibility​

PlanCan use directory connectorsCan add custom MCPLimit
Free✔✔1 custom connector
Pro✔✔Unlimited
Max✔✔Unlimited
Team✔ (owner enables first)✔ (owner adds first)Unlimited
Enterprise✔ (owner enables first)✔ (owner adds first)Unlimited

What Claude Can Do​

Claude can only use the public-safe subset Hunch exposes for that website:

  • answer grounded website questions
  • search public website knowledge
  • search the exposed tool catalog
  • inspect workflow skills and prompts
  • inspect available public capabilities
  • start approved contact, support, booking, or quote actions
  • continue multi-step action sessions
  • export a structured handoff when a human should take over

Claude cannot use owner-only tools, private dashboard actions, raw DOM tools, or live browser-session bridge tools through the public visitor connector.

Test the Connector​

Start with low-risk prompts:

  • "What can this website help me do?"
  • "Search this website for booking or pricing information."
  • "Search the tools for support or quote workflows."
  • "List the workflow skills available for this website."
  • "Start the quote, support, or contact flow."

Then complete one end-to-end public action before sharing the connector more broadly.

Safety Model​

Public visitor connector access is intentionally narrow:

  • access is off by default
  • owners must choose Unlisted or Listed
  • every request is rate-limited
  • signed visitor tokens can be required before Claude requests are accepted
  • challenge mode can require Cloudflare Turnstile proof before issuing visitor tokens
  • referrer allow/block lists and blocked visitor hashes can deny specific sources or identities
  • max risk score blocks suspicious requests before tool execution
  • only approved public-safe actions and workflow skills are exposed
  • live-session bridge tools are blocked
  • calls are written to the Hunch audit log
  • website embed API keys are never used as connector credentials

Common Issues​

Claude asks for OAuth​

OAuth is now supported. If Claude detects OAuth on the public connector URL, follow Option A above — Claude will handle the consent flow automatically. You can also select no authentication to skip OAuth and use Option B instead.

Claude can read but cannot act​

Check:

  • the action was discovered by Hunch
  • the action is public-safe, such as contact, support, booking, or quote
  • the action is enabled in Website Action Controls
  • public access mode is Unlisted or Listed

The connector URL returns "not enabled"​

The website is still set to Off. Switch it to Unlisted or Listed in Public AI Access and save.