Skip to main content
Back to the Webflow MCP server

MCP Gateway · OpenCode

Webflow icon

Connect Webflow to OpenCode

Release work on a Webflow site, like publishing, redirects after a URL change or a robots.txt edit, fits in a terminal checklist. OpenCode can run those steps as a remote server in its mcp config, with the Speakeasy gateway deciding which Webflow tools each role can reach. The OpenCode plugin sends every prompt and tool call to Speakeasy to be allowed or denied first.

Category
Developer tools
Tools
22
Authentication
OAuth
OpenCode
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.

Deploy on MCP Gateway

Set up

Add Webflow to OpenCode 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. OpenCode connects to the Webflow server's own URL, and the server's authorization decides who can connect and which tools they can call.

  3. 03

    Connect OpenCode

    Add the server to OpenCode's own mcp config block as a remote server.

    Copy the server's URL from its hosted install page in Speakeasy.

    Add it to the mcp block of your OpenCode config with type set to remote.

    Restart OpenCode and sign in when prompted.

    {
      "mcp": {
        "<server slug>": {
          "type": "remote",
          "url": "<URL from the hosted install page>"
        }
      }
    }
  4. 04

    Sign in and use Webflow from OpenCode

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

OpenCode doesn't receive MCP servers from plugins. The observability package is installed separately, from a ZIP or with speakeasy-hooks install --provider=opencode, and the device agent can maintain it.

Use cases

What OpenCode users do with Webflow

Add redirects after a URL change

When pages move, OpenCode reads the old and new paths from your change list and creates the matching 301 redirects, then updates robots.txt if a section should stay hidden.

data_enterprise_tool

Audit page settings before release

OpenCode lists every page on the site and reads its metadata, flagging pages with missing titles or descriptions so you can fix them before publishing.

data_pages_tool

Publish a site from the terminal

Once checks pass, OpenCode looks up the site details and publishes it, so the release step happens in the same session as the review.

data_sites_tool

Tools

22 tools

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

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

Prompt and tool-call blocking

OpenCode

The OpenCode plugin sends each prompt and tool call to Speakeasy, which allows or denies it before it runs.

Usage telemetry

OpenCode

Token and cost totals flow through the plugin, reported per turn.

Device agent

OpenCode

The device agent installs and maintains the observability package.

  • OpenCode has no OpenTelemetry exporter, so session data comes through the plugin.
  • Tool output is blocked at the gateway rather than in OpenCode's hooks.

Questions

Frequently asked questions

Does the Webflow redirects tool work on every plan?
No. data_enterprise_tool, which manages 301 redirects and robots.txt, only works on an Enterprise workspace plan or higher. On other plans the tool returns an error.
How is OpenCode's observability package installed?
It is installed separately, from a ZIP or with speakeasy-hooks install --provider=opencode, and the device agent can maintain it. OpenCode doesn't receive MCP servers from plugins.
How do OpenCode users get Webflow?
An admin adds Webflow from the Speakeasy MCP Catalog and grants access by team or role. Add the server to OpenCode's own mcp config block as a remote server. Each person then sees only the Webflow tools their access allows.
Are Webflow calls from OpenCode 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.