Using Webflow’s MCP with Multiple Clients & Workspaces

Do you need to use Webflow's MCP server with multiple client sites- without continually disconnecting and reconnecting?

Here's the approach I use, which-

• Allows me to separate client MCP connections cleanly
• Authenticate ONCE for each
• Easily pick up where I left off
• Support advanced MCP configs, e.g. for site migrations or complex data loads

Create your MCP config with the Claude CLI-

claude mcp add --transport http webflow-project1 https://mcp.webflow.com/mcp -s project

Tips;

• Run this in the directory you will be opening in VS Code, which represents your specific client or project
• Remember to give your project a custom name, like webflow-project1
• Note the scoping with -s project , very important

Primary Use Cases

• Easily switching between Claude MCP configurations, per client
• Ability to work simultaneously on multiple client projects without conflict, while still keeping their MCP access distinct

Advanced Use Cases

Site migrations

• Multiple MCP connections, possibly across workspaces
• Ability to protect a source prod site by restricting tools to read-only tools

More Research

MCP Gateways

Challenges

Claude code has a bug regarding token persistence, which requires some further research to minimize re-auth.