The Webflow MCP in Claude Code holds one project at a time, so every client switch means disconnect, restart, reconnect. AgencyFlow keeps every client's connection live at once, each verified to a single site, then keeps going: open the site in Webflow, copy the exact prompt for a chat, and schedule a full-site publish that fires from the cloud with your Mac closed.
One project at a time. Every switch is a cold start.
Every project connected and organized. Start 50 chats on 50 projects, if you want.
Name it after the client. AgencyFlow registers it with Claude Code as its own Webflow MCP server, so it never competes with another client for a slot.
Webflow's own login opens in your browser. Tick the single site, never the workspace, and AgencyFlow then asks the live connection what it can actually reach. One site means correctly scoped. More, and you know before work starts.
Authorizations lapse. When one does, the tag turns orange and a tap runs the same browser step again. Connect All MCPs, in the ⋯ menu, does it for every card that needs it.
Click MCP Live and the exact instruction is on your clipboard. Paste it into any Claude Code chat and the work goes to that one client, never a neighbor.
The Webflow mark on the card opens that site's Designer in your browser. The link comes from the verified site, not the name you typed, so it cannot open the wrong client.
Pick the site, the moment, and the domains in the Scheduled Publishing tab, and the publish fires from our servers with your Mac open or closed. Paranoid Mode skips it if the site changed after you scheduled, so nothing unreviewed goes live.
Permissions are granted per connection, at the moment you authorize it: a single-site grant physically cannot reach another site, because Webflow itself refuses the call, and AgencyFlow rechecks the scope after every connect. Every card also shows its status, a tap on a flag runs the fix, and the panel answers ⌘N to add, ⌘F to search, ⌘1 and ⌘2 to switch tabs, and ⌘R to refresh.
I run a Webflow studio for B2B tech. I built AgencyFlow because the restart loop was costing my own team way too much time, and every Webflow team we showed it to wanted a copy.
Three projects free, forever. Unlimited on any paid plan.
Switch between monthly and annual any time. Paid plans and founding members include scheduled publishing on our servers when your Mac is closed.
Yes. Webflow ships an official MCP server that connects Claude Code to your Webflow projects. AgencyFlow does not replace it. AgencyFlow manages those connections so more than one stays live at a time.
Not with the stock setup. The Webflow MCP authorizes one project per connection, and switching sites means disconnect, restart, reconnect. AgencyFlow creates a separately named, separately scoped MCP server for each site, so all of them stay connected at the same time.
Yes. Webflow maintains a first-party MCP server, currently on version 2.0. AgencyFlow sits on top of it and handles the connection management that the official server does not.
Yes. Connect publishing for a site, then choose the date, time, and domains. AgencyFlow publishes from our servers at that moment, whether your Mac is open, asleep, or off. You can reschedule, cancel, or publish immediately from the menubar, and every launch is recorded with its outcome.
A per-launch option that skips the publish if the site is edited after you scheduled it. At fire time AgencyFlow compares the site's current state with the state it captured when you scheduled. If anything changed, or the state cannot be read, nothing publishes and you get a notification instead.
Not for MCP connections. Claude Code holds those tokens and AgencyFlow only manages the registrations. Scheduled publishing needs a token that works while your Mac is off, so for that you grant AgencyFlow a separate authorization scoped to one site. It is stored encrypted on our servers and can be revoked from the project card at any time.
Each project gets its own named MCP server, authorized to a single Webflow site, and AgencyFlow checks that scope after every connection. A call aimed at the wrong client is refused by Webflow itself, so work on one site cannot land on another.
No. AgencyFlow is built for Claude Code only, and it requires macOS 26 or later on Apple Silicon. Support for other clients is not currently on the roadmap.
Three projects are free forever. Unlimited projects are $39 per month or $249 per year. Scheduled publishing is included with paid plans and for founding members.
Three projects free, no sign-in needed. First 25 sign-ups: free forever.