MCP Gateway · Claude
Connect Webflow to Claude
Marketing and content teams own most Webflow sites, and much of their work is reading feedback and adjusting page details. In Claude, they can do that by asking. Once an Owner adds the gateway as a custom connector, each person connects with one click and only sees the Webflow tools their role can reach, with every call logged against their name.
- Category
- Developer tools
- Tools
- 22
- Authentication
- OAuth
- Claude
- Web, desktop and mobile
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 Claude 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 Claude
Add the gateway URL as a custom connector, then connect it from Customize > Connectors.
On Team and Enterprise plans, an Owner opens Organization settings > Connectors, chooses Add > Custom > Web and pastes the gateway URL.
Each person opens Customize > Connectors and clicks Connect to sign in.
On Pro and Max plans, each person adds it themselves under Customize > Connectors, with + Add > Add custom connector.
- 04
Sign in and use Webflow from Claude
The first time Claude 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 Claude, limited to what the person's access allows, and every call lands in the gateway's tool logs.
No client ID or secret is needed: the gateway's sign-in handles client registration. Each person only sees the servers their role can reach.
Use cases
What Claude users do with Webflow
Summarize Designer comments on a page
Ask Claude what reviewers said about a landing page. It reads the comment threads with their replies, page location and breakpoint, and lists what is still open.
Rewrite SEO titles and descriptions
Have Claude read the metadata for your site's pages, suggest clearer titles and descriptions, and update the page settings once you approve the wording.
Check images before they go live
Paste image URLs from a campaign brief and Claude previews each one, then lists the assets and folders already on the site so nothing is uploaded twice.
Tools
22 tools
Each Webflow tool can be allowed or denied per team and role at the MCP Gateway before Claude 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 Claude
The gateway covers every client the same way. The rest depends on what Claude 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 Claude. MCP-scoped policies are enabled per organization.
Anthropic inference hooks
Claude
On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.
Conversation import
Claude
Claude conversations can be imported through Anthropic's Compliance API for review after the fact.
- Custom connectors need a Claude plan that supports them.
- Budgets don't cover Claude web and desktop usage.
Questions
Frequently asked questions
Can content editors use Webflow in Claude without changing site code?
Which Claude plans can use the Webflow connector?
How do Claude users get Webflow?
Are Webflow calls from Claude logged?
Connect more