MCP Gateway · Cursor
Connect Webflow to Cursor
Front-end developers often build a section in code first, then need it inside a Webflow page with matching classes and tokens. Cursor can take that markup straight from the editor and place it on the active page through the Speakeasy gateway. Each Webflow call is logged with the developer's email, and Cursor hooks check every prompt and tool call before it runs.
- Category
- Developer tools
- Tools
- 22
- Authentication
- OAuth
- Cursor
- Editor and terminal
Behind the MCP Gateway
Run Webflow MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Webflow call inspected and logged.
Set up
Add Webflow to Cursor in 4 steps
- 01
Add Webflow from the catalog
An admin finds Webflow in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.
Webflow uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.
Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.
- 02
Choose who can use Webflow
Give teams the
mcp:connectscope on the Webflow server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Webflow to their gateway on the next call, and removing it takes it away. - 03
Connect Cursor
Add the gateway to Cursor in one click from the Organization Gateway page.
On the Organization Gateway page in Speakeasy, choose Cursor under Install.
Click Add to Cursor to add the gateway to Cursor's MCP settings, then sign in when Cursor prompts you.
- 04
Sign in and use Webflow from Cursor
The first time Cursor connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
Webflow needs its own OAuth grant, so each person connects it once. Until they do, Webflow calls fail while the rest of the gateway keeps working.
From then on, Webflow's tools appear in Cursor, limited to what the person's access allows, and every call lands in the gateway's tool logs.
For a whole team, a Cursor team admin imports the plugin marketplace under Settings > Plugins > Import and turns on Serve Marketplace From Cursor, so members install without GitHub access.
Use cases
What Cursor users do with Webflow
Turn editor markup into Webflow elements
Select an HTML and CSS snippet in Cursor and have it inserted into a parent element on the current Webflow page, instead of rebuilding it by hand.
Sync design tokens as variables
Cursor reads the color and spacing tokens defined in your codebase, compares them with the site's existing Webflow variables, and creates or updates the ones that differ.
Match classes to your stylesheet
List every style on the site and update the ones that drift from your CSS, so the Webflow build and the coded component render the same way.
Tools
22 tools
Each Webflow tool can be allowed or denied per team and role at the MCP Gateway before Cursor sees it.
ask_webflow_ai
Ask Webflow AI about anything related to Webflow API.
data_cms_tool
Data tool - CMS tool to perform actions like get collection list, get collection details, create collection, create collection fields (static/option/reference), update collection field, list collection items, create collection items, update collection items, publish collection i…
data_components_tool
Data tool - Components tool to perform actions like list components, get component content, update component content, get component properties, and update component properties
data_pages_tool
Data tool - Pages tool to perform actions like list pages, get page metadata, update page settings, get page content, and update static content
data_scripts_tool
Data tool - Scripts tool to perform actions like list registered scripts, list applied scripts, add inline site script, and delete all site scripts
data_sites_tool
Data tool - Sites tool to perform actions like list sites, get site details, and publish sites
Control
What Speakeasy can see and stop in Cursor
The gateway covers every client the same way. The rest depends on what Cursor exposes to Speakeasy.
Tool logs
Gateway
Every Webflow call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Webflow tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Webflow can reject a tool request before it reaches the server, or withhold a result from Cursor. MCP-scoped policies are enabled per organization.
Prompt and tool-call blocking
Cursor
Cursor hooks send each prompt and tool call to Speakeasy, which allows or denies it before Cursor runs it, and fail closed.
User attribution
Cursor
Every Cursor hook event carries the user's email.
Budgets
Cursor
Spend limits can block Cursor traffic once a budget is reached. Connect the Cursor Admin API for dollar spend.
Device agent and MDM
Cursor
The device agent installs the marketplace and plugins and reapplies them every minute.
- Cursor Cloud agents need a checked-in
.cursor/hooks.json. Session and MCP-specific hooks don't run there. - After a plugin update, members run Developer: Reload Window.
Questions
Frequently asked questions
Can I limit Cursor to Designer tools in Webflow?
What do Cursor users do after the Webflow plugin is updated?
How do Cursor users get Webflow?
Are Webflow calls from Cursor logged?
Connect more