Claude

Add the connector

1. Open Settings → Connectors in Claude
   Then Add custom connector. If your Claude plan does not offer custom connectors, the section will not be there.
2. Paste the HTFlow endpoint

   https://mcp.htflow.com/mcp

3. Leave the OAuth fields empty
   Client ID and Client Secret stay blank. The server registers Claude itself, so there is nothing to fill in.
4. Sign in to HTFlow when the browser opens
   That is the whole authorization. Claude comes back connected.

What the sign-in actually does

The connector sends you to mcp.htflow.com, which has no login of its own — it bounces the browser to htflow.com to read your existing HTFlow session. If you are signed in, a short-lived signed proof goes back to the connector and the connection is made. If you are not, you log in first and land back in the same place.

Claude's callback is one the server recognises, so there is no extra approval screen — the connection completes as soon as HTFlow knows who you are.

Check that it worked

A connected client sees 23 tools whose names all contain _flow_. The quickest proof is to ask Claude to list your sites — that calls list_flow_sites, which exercises both the connection and the authorization in one round trip.

Tools listed but every call failing means the opposite: Claude reached the server, but the session did not authenticate. Remove the connector and add it again.

If your setup uses a configuration file

Desktop installs that are configured by file rather than by connector take the endpoint and a bearer token instead. Create the token under Settings → API Tokens first.

{
  "mcpServers": {
    "htflow": {
      "url": "https://mcp.htflow.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN"
      }
    }
  }
}

On macOS that file lives at ~/Library/Application Support/Claude/claude_desktop_config.json. Restart the app after saving it.

Your first build

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

When it does not connect