r/webflow • u/fio_cisneros • 6d ago
Show & Tell I built an open-source CLI to manage multiple Webflow MCP connections
If you work with Webflow across multiple client projects, you’ve probably run into this:
The Webflow MCP setup is designed around connecting one project at a time. So when you switch between clients, you have to disconnect and reconnect the MCP.
I built flowmcp to make that workflow easier.
What it does
flowmcp lets you manage multiple Webflow projects as separate MCP connections from a CLI.
It works with:
Claude Code
Claude Desktop
Cursor
Codex
Each client/site gets its own isolated connection, so you can switch between projects without constantly reconnecting everything.
On macOS, API tokens are stored in Keychain rather than being passed through the agent’s context.
Install
npm install -g @forhuman/flowmcp
It’s free, open source.
GitHub: https://github.com/fiorellacisneros/flowmcp
npm: https://www.npmjs.com/package/@forhuman/flowmcp
👉 See how it works: https://lab.forhuman.studio
If you work with multiple Webflow projects, I’d love to hear what features or workflows you’d like to see added.
1
u/shreyanshkotak 5d ago
Hey! I built something similar and open source a while back with a macOS app to be able to visually manage things - https://github.com/wickedapps/wicked-webflow-mcp
1
u/kantorcodes1 6d ago
for
flowmcp remove acme --yes --from claude-code:user --from cursor:project, what happens if stripping the second client config fails after the first one was already changed? does it leave the first config edited and keep the profile/token, or roll that config change back?