Skip to main content
Back to the Webflow MCP server

MCP Gateway · Codex

Webflow icon

Connect Webflow to Codex

Moving content into Webflow usually means mapping a data model onto CMS collections and fields by hand. Codex can do that mapping from the schema or export file in your repository. Behind Speakeasy's gateway, engineers authenticate once with your IdP, each team is limited to the Webflow tools its role needs, and every collection or item Codex creates is logged against a named person.

Category
Developer tools
Tools
22
Authentication
OAuth
Codex
CLI and ChatGPT desktop app

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 Codex 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 Codex

    Add the gateway as an MCP server, then log in.

    Run the first command with your organization gateway URL.

    Run the second command to sign in.

    codex mcp add 'speakeasy' \
      --url 'https://<organization host>/mcp/gateway/<organization slug>'
    codex mcp login 'speakeasy'
  4. 04

    Sign in and use Webflow from Codex

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

To roll it out to a team, a ChatGPT workspace admin imports the plugin marketplace under Admin > Plugins and sets an installation policy per role. Imported plugins reach nobody until a policy is set.

Use cases

What Codex users do with Webflow

Model a CMS collection from code

Give Codex a type definition or JSON schema and it creates a matching Webflow collection with static, option and reference fields, then reads back the collection details to confirm.

data_cms_tool

Import records into collection items

Point Codex at an export file in the repository. It reads the Webflow tool guidelines first, then creates collection items from each record and lists them to check the count.

webflow_guide_tooldata_cms_tool

Register a webhook for content changes

When a build or search index should refresh on CMS changes, Codex creates a site webhook for it and fetches the webhook details to confirm the target.

data_webhook_tool

Tools

22 tools

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

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

Prompt and tool-call blocking

Codex

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

User attribution

Codex

An [otel] block in ~/.codex/config.toml sends telemetry to Speakeasy. Export is off by default.

Budgets

Codex

Spend limits can block Codex traffic once a budget is reached.

Device agent and MDM

Codex

The device agent keeps Codex's configuration in sync on managed laptops.

  • Codex cloud tasks and GitHub code review run off the device. Neither the plugin nor OpenTelemetry covers them; OpenAI's Compliance Logs record them after the fact.
  • The workspace rollout needs a ChatGPT Business, Enterprise or Edu admin.

Questions

Frequently asked questions

Can I keep Codex away from Webflow site publishing?
Yes. Tools are allowed or denied per team at the MCP Gateway, so a role can use data_cms_tool without data_sites_tool, which publishes sites. Agent hooks also send each tool call to Speakeasy, which allows or denies it before Codex runs it.
How is Codex activity attributed to a person?
An [otel] block in ~/.codex/config.toml sends telemetry to Speakeasy. Export is off by default, so add the block to tie sessions to people.
How do Codex users get Webflow?
An admin adds Webflow from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway as an MCP server, then log in. Each person then sees only the Webflow tools their access allows.
Are Webflow calls from Codex 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.