Back to the MCP Gateway catalog

MCP Gateway · Catalog

Webflow icon

Webflow MCP server

Official

Webflow MCP is the official Model Context Protocol server for Webflow, with OAuth and tools that let agents work with CMS content, pages, components, elements, and styles, and ask Webflow AI for help. Connect it through the Speakeasy MCP Gateway and agents such as Claude, Cursor, and ChatGPT get one governed URL for it, with SSO, RBAC, and a full audit trail.

Developer tools22 toolsAuth: oauth

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.

Deploy on MCP Gateway

Tools · 22

Each tool below can be allowed or denied per team and role at the MCP Gateway, and every call is inspected and logged.

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 items, and delete collection items

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

data_comments_tool

Data tool - A comment in Webflow is user feedback attached to a specific element or page inside the Designer, stored as a top-level thread with optional replies. Each comment includes author info, timestamps, content, resolved state, and design-context metadata like page location and breakpoint. Use this tool to inspect feedback discussions across the site and understand where and why they were left.

data_enterprise_tool

Data tool - Enterprise tool to perform actions like manage 301 redirects, manage robots.txt and more. This tool only works if User's workspace plan is Enterprise or higher, else tool will return an error.

data_webhook_tool

Data tool - Webhook tool to perform actions like list webhooks, create webhooks, get webhook details, and delete webhooks for a Webflow site.

asset_tool

Designer Tool - Asset tool to perform actions like create folder, get all assets and folders, update assets and folders

get_image_preview

Designer Tool - Get image preview from url. this is helpful to get image preview from url. Only supports JPG, PNG, GIF, WEBP, WEBP and AVIF formats.

de_component_tool

Designer tool - Component tool to perform actions like create component instances, get all components and more.

component_builder

Designer Tool - Component builder to insert component instances on the current active page. Supports inserting into an element (as a child) or into a component instance's slot. Use insert_in_element to add a component inside a container/div/section. Use insert_in_slot to add a component inside a specific slot of an existing component instance.

element_tool

Designer Tool - Element tool to perform actions like get all elements, get selected element, select element on current active page. and more

element_builder

Designer Tool - Element builder to create element on current active page.

whtml_builder

Designer Tool - WHTML builder to insert elements from HTML and CSS strings on the current active page. Accepts HTML markup and optional CSS rules, constructs WHTML, and inserts into a parent element.

element_snapshot_tool

Designer Tool - Element snapshot tool to perform actions like get element snapshot. helpful to get element snapshot for debugging and more and visual feedback.

de_page_tool

Designer Tool - Page tool to perform actions like create page, create page folder, get current page, switch page

style_tool

Designer Tool - Style tool to perform actions like create style, get all styles, update styles, remove styles

variable_tool

Designer Tool - Variable tool to perform actions like create variable, get all variables, update variable

webflow_guide_tool

Provides essential guidelines and best practices for effectively using the Webflow tools. Call this tool to understand recommended workflows and important considerations before performing actions. ALWAYS CALL THIS TOOL FIRST BEFORE CALLING ANY OTHER TOOLS. ALWAYS CALL THIS TOOL FIRST BEFORE CALLING ANY OTHER TOOLS.

get_more_tools

Check for additional tools whenever your task might benefit from specialized capabilities - even if existing tools could work as a fallback.

Questions

What is a Webflow MCP server?
A Webflow MCP server exposes Webflow to AI agents as Model Context Protocol tools. Instead of a custom integration per agent, any MCP client can connect to the server and call tools such as ask_webflow_ai or data_cms_tool to work with Webflow. The server in this catalog is the official Webflow MCP server, which authenticates with OAuth.
What can you do with Webflow MCP?
Agents can work with CMS content, pages, components, elements, and styles, and ask Webflow AI for help. The catalog lists 22 tools for this server, including ask_webflow_ai, data_cms_tool, and data_components_tool. The full list with descriptions is on this page.
Why put Webflow MCP behind an MCP gateway?
Connecting the Webflow MCP server directly to each client means a separate credential per developer, no inventory of who can reach Webflow through an agent, and no record of what agents did with it. An MCP gateway sits between every agent and the Webflow server, so sign-in runs through your identity provider, role-based access decides which teams can call which Webflow tools, and every call is inspected and logged in one place. The Speakeasy MCP Gateway applies those controls to Webflow and to every other server in your catalog.
How do you connect Webflow MCP through a gateway?
Add the Webflow server from the Speakeasy MCP catalog and every agent reaches it through one gateway URL, next to the rest of your approved servers. Authentication uses OAuth 2.1 with PKCE and dynamic client registration, sign-in runs through your identity provider, and role-based access controls decide which teams can use which Webflow tools. Every prompt, response, and tool call is inspected and logged at the gateway.
How is this different from an unofficial Webflow MCP?
Community-built Webflow MCP servers wrap the same Webflow surface but are not vendor-maintained, and most authenticate with a static credential that gives an agent everything the credential owner can touch. This catalog lists the official Webflow MCP server, which uses OAuth. Running it behind the Speakeasy MCP Gateway adds SSO, role-based access, and an audit trail of every call.

AI everywhere.

Control here.