Skip to main content

Connect Hunch to ChatGPT

Use this guide when you want ChatGPT 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
  • you have a ChatGPT workspace or plan that currently supports custom remote MCP connectors

OpenAI can change ChatGPT connector availability or UI labels. If something in ChatGPT looks different, check OpenAI's current documentation before continuing:

What to prepare 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 table.

Recommended setup before you connect:

  • disable any site-derived capability you do not want exposed externally
  • allow Public Execute only for public-site actions you are comfortable letting Hunch run directly
  • use standard MCP access first and add live scope only if you actually need claimed browser-session actions

The MCP page gives you:

  • the endpoint URL
  • the authorization server metadata URL
  • the protected resource metadata URL
  • the scopes currently supported for that website

Connect from ChatGPT​

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

If you want the full Hunch tool surface rather than a narrow connector-style subset, make sure you are using the current OpenAI flow that supports full MCP tools.

In most cases, start with:

  • mcp:read
  • mcp:tools

Only grant mcp:live if:

  • your Hunch plan allows live scope
  • you need claimed live browser/session actions
  • you understand that live actions require an explicit visitor claim flow

What ChatGPT can do after setup​

Once connected, ChatGPT can use the same Hunch capability layer that powers the widget, subject to your policies and plan:

  • grounded site questions with site.ask
  • grounded retrieval with site.search
  • normalized site actions through site.action.*
  • multi-turn action completion through action.reply, action.confirm, and action.cancel
  • handoff exports when a human should take over

If live scope is granted and a visitor explicitly connects their current widget session, ChatGPT can also access the claimed live-session bridge.

Test the connection​

Start with safe prompts:

  • "What can this website's Hunch server do?"
  • "Search this site for pricing information."
  • "List the actions available for this website."
  • "Start the demo booking flow."

Then test one multi-turn action from start to finish.

Manage or revoke the connection​

Back in Hunch:

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

You can also change capability policies after a connector is installed. Future tool calls will follow the latest policy state.

Common issues​

ChatGPT cannot finish the install​

Check:

  • the website is on a Hunch plan with external MCP access enabled
  • the endpoint URL came from the correct website's MCP tab
  • the Hunch user approving the install has access to that website

Tools appear missing​

Check:

  • the capability is still enabled in Capability Policies
  • discovery has already produced the relevant site action
  • the requested scope includes mcp:tools

Live actions are unavailable​

Check:

  • the website is on a plan that allows mcp:live
  • the connector was granted mcp:live
  • a real visitor has explicitly claimed the live browser session