MCP Gateway · Claude Cowork
Connect Webflow to Claude Cowork
Site refreshes are long jobs: dozens of CMS entries to rewrite, static copy to change across pages, and a publish at the end. Cowork can carry that whole sequence for a content team. The Webflow server arrives through the organization's synced plugin, Cowork's OTLP export ties each session to a person, and Speakeasy's agent hooks allow or deny each prompt before the step runs.
- Category
- Developer tools
- Tools
- 22
- Authentication
- OAuth
- Claude Cowork
- Cowork tab in Claude Desktop
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 Cowork 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. Claude Cowork connects to the Webflow server's own URL, and the server's authorization decides who can connect and which tools they can call. - 03
Connect Claude Cowork
Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.
New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.
Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.
In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.
Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.
In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.
- 04
Sign in and use Webflow from Claude Cowork
The first time Claude Cowork 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 Cowork, limited to what the person's access allows, and every call lands in the gateway's tool logs.
Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.
Use cases
What Claude Cowork users do with Webflow
Refresh every item in a collection
Cowork lists the items in a collection, such as case studies or team bios, rewrites each against a new style guide, updates them, and publishes the changed items.
Replace copy across many pages
Give Cowork a messaging change, like a new product name. It reads the static content on each page, updates every mention, and reports which pages changed.
Close out feedback, then publish
Cowork reviews the open Designer comments, checks each against the current page content, and publishes the site once the outstanding items are addressed.
Tools
22 tools
Each Webflow tool can be allowed or denied per team and role at the MCP Gateway before Claude Cowork 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 Cowork
The gateway covers every client the same way. The rest depends on what Claude Cowork 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 Cowork. MCP-scoped policies are enabled per organization.
Prompt blocking
Claude Cowork
Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.
Session telemetry
Claude Cowork
Cowork's OTLP export ties sessions to people and feeds observability.
Anthropic inference hooks
Claude Cowork
On Claude Enterprise, prompts can be checked before inference (beta).
- Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
- Personal Claude accounts can't be governed in Cowork.
Questions
Frequently asked questions
How does a new Webflow plugin version reach Cowork?
Can the device agent manage Webflow access in Cowork?
How do Claude Cowork users get Webflow?
Are Webflow calls from Claude Cowork logged?
Connect more