Connect Cursor to Multiple Webflow Workspaces

MCP, Model Context Protocol, is what lets an AI tool like Cursor talk directly to your Webflow sites. Read your CMS, check your pages, make changes, and a lot of other things, all through natural language instead of clicking through the Designer. That's lovely.

But most people set this up once, for one Webflow workspace, and stop there. But if you are not like most people and you work across a personal workspace, an agency workspace, and a handful of client sites, one connection might not be enough. So. You’ll need something like Cursor to know which Webflow workspace it's talking to, every time, all at once.

So. In this video, we’ll go over what you need to set up to make this happen. We'll connect the 1st workspace, then we’ll connect 2 more, we’ll go over some best practices, and finally, we’ll test it to make sure everything is up and running.

By the end, you'll have a Cursor setup that allows you to work on multiple sites in multiple workspaces, in multiple different dimensions. All at the same time.

So. What you'll need is Cursor, the desktop app. You'll need access to two or more Webflow workspaces. And you'll need MCP access configured for each workspace, with any role except Reviewer, since the MCP server respects your existing Webflow permissions.

To run multiple workspaces side by side, we're going to add the MCP server manually and give each one its own name.

Okay. Let’s add the first workspace. We’ll go up to customize, find our MCPs, and here we're going to add a new custom MCP server. We’ll choose this one here. If you don’t have one, you’ll have to create one first. I’m just pasting the code snippet here. We'll name this first entry something specific rather than generic, since that name is what Cursor will show us going forward.

Once we save the file, we’ll go in and enable it, and then we’ll go and authenticate, and Cursor opens an OAuth login page in the browser. We’ll toggle and continue. If you’re logged into Webflow, we’re right there, and we can choose exactly which site, or sites, and workspace we want this connection to access. Back in Cursor, the connection should show a green status once it's live. We can confirm it's actually working with a simple prompt, just asking Cursor to list the site, or sites, this connection can access. And we see that the response matches what we just authorized.

Okay. Let’s move on. Let's add a couple more.

Back in that same configuration file, let’s add another entry, pointing at the same MCP address but under a different name. So we have our site 2, in our Agency workspace. Let’s paste that in here, and we have the 3rd site, a client site, and it’s in the 3rd workspace.

Cursor treats each entry as its own independent connection, so when we authorize the second one, we're logging into that workspace specifically and choosing its own sites and Workspaces, separate from what the first connection can see. Same with the 3rd one. Each named entry has its own authorization, its own set of permitted sites, and its own session. Disconnecting or reauthorizing one has no effect on the others.

That’s connecting two more sites, from two different workspaces. Let’s look into some best practices.

Each named entry is really just a slot for one OAuth connection.

Naming each one for what it actually is, the client, the brand, or the Workspace it points to, is what keeps this manageable.

One thing to flag on Workspaces and sites: a single Webflow login can have access to multiple Workspaces, and a Workspace can hold multiple sites. When we authorize a connection, we're not just picking a workspace, we're picking which Workspaces and which sites within them Cursor can see. If you manage several client sites under one Workspace, you can scope a single connection down to just the site you're working in, rather than exposing the whole Workspace.

With multiple connections live, the real trick is telling Cursor which one to use for a given task. The most reliable way to do that is naming the connection directly in the prompt, for example, asking Cursor to use a specific connection to list the collections in a site and show their field structures. Don't assume Cursor will infer the right workspace from context alone, especially once more than two connections are configured.

Okay, that's some good practice. Let's wrap it up with some testing, some real tasks.

Let’s ask Cursor to audit Multiple Webflow Workspaces, all three, that we have connected through MCP at the same time.

In Cursor, we have each one named clearly enough that we always know which site we're about to work on. We have Site 1, Site 2, and site 3.

We’re asking for the same information from all these different sites. Let’s send it. And here’s the response. What’s the win here? By doing this, it makes it convenient to get all that info without logging in and out to access different sites in different workspaces.

Let’s do another one. We’ll ask for three completely different things.

Let’s update the copy on site 1. We'll ask for a design change on site 2, and lastly, we’ll pull analytics data from the 3rd site. Let’s send it. And there we go, all the things working simultaneously. And, all three tasks have been completed.

So connecting MCP with Cursor gives us direct access to multiple Webflow sites in multiple different Workspaces. It allows you to be connected to more than one site or workspace at a time, so you can multitask as much as you can handle.

That’s connecting MCP to multiple workspaces using Cursor.

‍