ChatGPT

Add the connector

1. Open Settings → Connectors in ChatGPT
   Then add a custom MCP app. If you do not see the option, your ChatGPT plan does not expose custom connectors.
2. Fill in the form
   The four fields ChatGPT asks for are below. The URL is the same canonical endpoint every other client uses.
3. Sign in to HTFlow when the browser opens
   ChatGPT hands the authorization to HTFlow and comes back connected.

What the sign-in actually does

ChatGPT registers itself with the server, then sends you to mcp.htflow.com. That host has no login of its own, so it bounces the browser to htflow.com to read your existing HTFlow session — signed in, and a short-lived signed proof completes the connection; not signed in, and you log in first and land back in the same place.

ChatGPT's callback is one the server recognises, so no extra approval screen appears.

Check that it worked

A connected client sees 23 tools whose names all contain _flow_. Ask ChatGPT to list your HTFlow sites: that calls list_flow_sites, which proves the connection and the authorization together.

Remember to enable the connector for the conversation you are working in — an app that is installed but not switched on for that chat contributes no tools at all.

Your first build

1. Ask for the rulebook once
   get_flow_webflow_rules hands ChatGPT the constraints its writes will be held to. One call at the start of a session prevents rejected sections later.
2. Describe the page
   The same conversation you would have in the builder panel. ChatGPT creates the site, the page and each section through the tools.
3. Open it in HTFlow and export
   Everything it builds appears in your workspace. From there it is the normal Webflow export.

When it does not connect