← Resource library

How to Connect Multiple Webflow Sites With MCP (3 Methods)

Watch on YouTube

About this video

Managing multiple Webflow sites with AI can get frustrating, especially when you're constantly switching accounts, reconnecting tools, or logging back in.

In this video, I'm sharing 3 ways to connect multiple Webflow sites and workspaces using the Webflow MCP, so you can manage different projects without constantly reauthenticating.

Whether you're a freelancer managing multiple clients, an agency working across different Webflow workspaces, or a business managing several websites, there's a solution depending on which AI tools you're using.

Here are the 3 methods we'll cover:

1. Folder-Scoped MCP Connections
My preferred method for working across multiple Webflow projects. By creating separate project folders with their own MCP configuration files, you can keep each client connection organized and switch between projects using tools like Cursor, Claude Code, or Zed.

2. Multiple Accounts in One App
Some AI applications, including Grok Bot and Codex, allow you to connect multiple Webflow accounts directly within the same app. This makes switching between different clients and workspaces much easier without needing a custom setup.

3. Custom Local MCP Proxy Servers
If you're using Claude Desktop, this is the workaround for managing multiple Webflow connections. A lightweight local proxy allows you to create separate MCP connections for each client without running into authentication conflicts.

In this video, you'll learn:

  • How to connect multiple Webflow workspaces with MCP
  • Which connection method works best for different AI tools
  • How folder-scoped MCP configurations work
  • How to manage multiple Webflow accounts in Grokbot and Codex
  • Why Claude Desktop requires a different approach
  • How local MCP proxy servers solve connection conflicts
  • Where to find my tested setup instructions and configurations

Resources

Chapters

  • 00:00 Introduction
  • 01:00 Method #1: Folder-Scoped MCP Connections
  • 02:10 Method #2: Multiple Accounts in One App
  • 02:55 Method #3: Custom Local MCP Proxy Servers
  • 03:54 Final Thoughts

Full transcript

1,070 words

Copy transcript

Today we're talking about how to use the Webflow MCP on multiple sites at once. So here's the problem. Many people need to work on more than one Webflow site at a time. Agencies and freelancers like myself or even business owners or businesses with multiple units that have to switch across workspaces for whatever access or team reasons. I don't know about you, but I hate having to log back into things all the time. So I found a couple of different solutions depending on which tool you're using and I'm going to share them here.

Over the last couple of weeks, I've had multiple people message me directly, so I figured I'd make a video. Today we're going to talk about three ways that you can connect to multiple Webflow workspaces with the MCP. I'm presenting multiple reasons because it really depends on which app you use, which tools you're using. There's different solutions for different people. I'm not going to go through video tutorials because the interface has changed so quickly.

It's possible that this video may go out of date, but I have found that these types of connections are common and they work across multiple apps. So I'm going to keep the repo up to date with the correct instructions. The interfaces themselves may change even from week to week. The first type of connection is a folder scoped MCP. Now this for me has been really the easiest by far and this is one of the first ways that I figured out how to do it.

The way that this is done is by having different folders for every workspace or every client that you're working on and then you have a custom configuration file in that workspace, maybe an mcp.json or something like that. You're going to have the name of that particular Webflow file, something custom like Webflow-client name. You have to restart and do a new session with your AI and then you'll pick it up just for that particular folder and it'll be ready to authenticate in Webflow.

I love this option because since it's in a particular folder, Cloud Code or Cursor, just use it when you're in that particular folder. You don't have to worry about trying to pick up the wrong site if you're working on just a global desktop app. It's also extremely easy to switch between different projects and what I do is I just have different IDEs open for each different project. I'm using Z and I just open up the Z window for client number one, client number two.

I can switch instantly just by using that other window and it's already connected. It's always live. The only conflict is if you are trying have multiple agents use that connection at the same time. If you're some sort of AI orchestration wizard and you open up a bunch of different terminals and you have them all trying to use that MCP, you're probably going to run into some traffic jams. The next option is to add multiple accounts to the same app.

There are only a few apps out there that support having multiple connections of the same type, but when they do, it's super easy and it's really a nice way to work. Grok Bot was actually the first that I found that did this. That was one of the things that hooked me right away because it's just so easy to connect multiple Webflow accounts. Codex has also recently added this to their desktop apps. It's really easy. All you have to do is go to your plugin settings, find your connection, and then go to add another connection of that same type.

Not everything supports this, like I said. When they do, it's really easy. You just re-authenticate that new account and then you can rename it or call it whatever you want. Cloud desktop cannot do this. It's one of the biggest hurdles I found to working with multiple accounts because it doesn't make it super user-friendly and super easy. We're going to go to option number three and this is the one that works with Cloud desktop.

The last option is a custom local MCP proxy server. Now, it's a lot of words. It sounds complicated. I'm going to walk you through it. It's going to be pretty easy. This is the trick for Cloud desktop to be able to handle multiple connections. If you try to do it without a proxy server, you're either going to have to re-log in all the time or it's going to give you a bunch of error messages when you try to add multiple connections.

What we have to do here is similar to how the folder scopes connections work. You can think of it in the same way where you have a different specifically named MCP for each specific client. Now, the only difference here is that the desktop app can see everything at once and it doesn't just limit itself to a folder. If you try to add another connection without using a proxy, it's going to say, oh, sorry, your computer's already using the Webflow connection for site number one.

But what you can do is you can use those proxy servers and you add as many as you want and then the proxy is what connects directly to Webflow. Cloud's going to the proxy servers and the proxy is going to Webflow. It'll show up on your side as a local MCP and it stays around even if you have multiple connections attached. I know that sounds complicated, but the agent can do it pretty well with the right instructions. I'm going to give you the right instructions.

They're going to be right here in this GitHub repo. I've compiled these and tested these over a couple of different iterations and I use all the different models and the different apps all the time. I'm always trying to find what works best for certain tasks. Every time I run into a bug or an issue, I'll update my skills and try to make sure that they're as current as possible. But if you do run into any issues, just let me know and I'm always happy to help troubleshoot or to keep things up to date.

Thanks for watching and good luck connecting to multiple Webflow sites.