The standard Webflow MCP setup in Claude Code holds one project at a time, so every client switch means disconnecting, restarting, and reauthorizing.
AgencyFlow, built by Absurdity Studio, registers each client project as its own named Webflow MCP server, so every connection stays live and you can run separate Claude Code chats on separate client sites at the same time.
Adding a site runs through the same Webflow OAuth screen as the official connector, and each token is scoped to a single site, with the app showing exactly which site each connection can reach before you start work. In the team's demo, three chats fixed three different sites in parallel (a typo in an H1, a link labeled Facebook that pointed to Google, and a duplicate H1) with no reconnecting in between.
The team's own advice holds: review what the AI changed before you publish. AgencyFlow also handles launch day: schedule a full-site publish and it fires from the cloud at the time you set, with your Mac closed.
Built for agencies and freelancers managing multiple Webflow clients with Claude Code. macOS only, 3 projects free forever.
New to the Webflow MCP? Start with the seven tasks it saves the most time on.
Screenshots
AgencyFlow MCP pros and cons
Pros
- Run separate Claude Code chats on separate client sites at once
- Same Webflow OAuth flow as the official connector
- Per-site token scoping with verification
- Scheduled publishes fire from the cloud, Mac off
- 3 projects free forever
Cons
- macOS only
- Works only with Claude Code
