Skip to main content
Back to the Webflow MCP server

MCP Gateway · Claude Code

Webflow icon

Connect Webflow to Claude Code

A Webflow site often needs code that lives outside the Designer: a tracking script, a webhook into your backend, an answer about how the Webflow API behaves. Claude Code can handle those from the terminal through the Speakeasy MCP Gateway, where each developer signs in with your identity provider and only reaches the Webflow tools their role allows. Agent hooks check every prompt and tool call before it runs.

Category
Developer tools
Tools
22
Authentication
OAuth
Claude Code
CLI

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

Set up

Add Webflow to Claude Code in 4 steps

  1. 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.

  2. 02

    Choose who can use Webflow

    Give teams the mcp:connect scope 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.

  3. 03

    Connect Claude Code

    Add the organization gateway as an HTTP MCP server, then authenticate from /mcp.

    Run the command below with your organization gateway URL.

    Open /mcp in Claude Code and choose Authenticate to sign in.

    claude mcp add --transport http --scope user \
      'speakeasy' \
      'https://<organization host>/mcp/gateway/<organization slug>'
  4. 04

    Sign in and use Webflow from Claude Code

    The first time Claude Code 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 Code, limited to what the person's access allows, and every call lands in the gateway's tool logs.

To roll it out to a whole team, publish the server in a plugin and register the plugin marketplace in Claude Code's managed settings, so every member gets it without running the command. The device agent can also write and reapply these settings on each laptop.

Use cases

What Claude Code users do with Webflow

Wire site events into your backend

Have Claude Code list the webhooks on a site, then create one that points at the endpoint you are building, so the site's events reach your service while you test it.

data_webhook_tooldata_sites_tool

Add an inline script to a site

Claude Code checks which scripts are registered and applied, then adds the inline site script you just wrote, such as an analytics snippet or a small widget loader.

data_scripts_tool

Ask how the Webflow API works

While writing an integration, ask Webflow AI a question about the Webflow API and read the guidelines for its tools before Claude Code makes its first call.

ask_webflow_aiwebflow_guide_tool

Tools

22 tools

Each Webflow tool can be allowed or denied per team and role at the MCP Gateway before Claude Code 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

See all 22 tools

Control

What Speakeasy can see and stop in Claude Code

The gateway covers every client the same way. The rest depends on what Claude Code 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 Code. MCP-scoped policies are enabled per organization.

Prompt and tool-call blocking

Claude Code

Agent hooks send each prompt and tool call to Speakeasy, which allows or denies it before Claude Code runs it.

User attribution

Claude Code

Claude Code's OpenTelemetry exporter ties each session to a named person. Without it, activity can't be attributed.

Budgets

Claude Code

Spend limits can block Claude Code traffic once a budget is reached.

Device agent and MDM

Claude Code

The device agent installs the marketplace, plugin and telemetry settings and reapplies them every minute. It deploys through MDM.

Anthropic inference hooks

Claude Code

On Claude Enterprise, prompts can be checked before inference with nothing installed on the device (beta).

  • Claude Code on the web doesn't use the laptop setup. It needs the device agent in a shared Anthropic-hosted environment.
  • Plugin marketplace URLs for Claude Code carry an access token, so share install snippets only through a private channel.

Questions

Frequently asked questions

Can I stop Claude Code from deleting Webflow site scripts?
Access is set per tool at the MCP Gateway, so a role without data_scripts_tool can't list, add or delete site scripts. Agent hooks also send each tool call to Speakeasy, which allows or denies it before Claude Code runs it.
Does Claude Code store a Webflow token?
No. Sessions authenticate through your identity provider at the gateway, and agents never hold a Webflow credential. Access ends when the employee leaves the directory.
How do Claude Code users get Webflow?
An admin adds Webflow from the Speakeasy MCP Catalog and grants access by team or role. Add the organization gateway as an HTTP MCP server, then authenticate from /mcp. Each person then sees only the Webflow tools their access allows.
Are Webflow calls from Claude Code logged?
Yes. Webflow calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

Webflow in other clients

AI everywhere.

Control here.