MCP server
Overview
HTFlow speaks MCP, so the assistant you already pay for can build and edit Flow sites. The export into Webflow is identical either way.
The endpoint
https://mcp.htflow.com/mcpThat one endpoint serves the Flow tools: raw Webflow-compatible HTML, CSS and vanilla JavaScript. It never reads or writes anything else.
Why drive it from your own client
The built-in agent panel runs on an OpenRouter key you supply. If you already pay for ChatGPT or Claude, MCP lets that subscription do the work instead — no second AI bill and no key to manage.
For developers there is a third reason: your editor already has the project context. Building a marketing page from the same window as the codebase it belongs to is simply less switching.
What a connected client can do
- List, create, read and delete Flow sites.
- Create, rename, reorder and delete pages and sections.
- Edit individual elements inside a section.
- Read and merge design tokens.
- Fetch the enforced Webflow rulebook with
get_flow_webflow_rules. - Audit a whole site against those rules with
audit_flow_site.
Getting set up
Claude Add HTFlow as a custom connector and sign in once.ChatGPT Add HTFlow as a custom MCP app over OAuth.Other clients Cursor, VS Code and anything else that speaks MCP.Agent workflow The read-then-write order the server expects.Tool reference All 23 tools, what they take and what they return.API tokens Authenticating a client against your workspace.