By Ira Bodnar, Ryze AI · Updated · Test record: no calls run
Quick answer
The main way to connect Codex to Webflow is the Ryze AI connector. Generate a Webflow site API token once and paste it into Ryze AI. Then run codex mcp add ryze --url https://connector.get-ryze.ai/mcp and codex mcp login ryze. The Codex CLI, the ChatGPT desktop app and the IDE extension read one MCP configuration, so one setup serves all three. Webflow also runs its own MCP server at https://mcp.webflow.com/mcp, which Webflow's overview page names Codex as a client of.
- In Webflow open Site settings, Apps & Integrations, API access and generate a token with CMS set to Read and write and Sites set to Read-only
- In Ryze AI open Integrations, click Connect on the Webflow card, paste the token and pick the site and CMS collection
- In Codex run codex mcp add ryze --url https://connector.get-ryze.ai/mcp
- Run codex mcp login ryze, sign in on the Ryze AI page and click Allow connection
Codex to Webflow at a glance
| Fact | Detail |
|---|---|
| Main way to connect | The Ryze AI connector, a hosted MCP server that Codex reaches over Streamable HTTP |
| Server address | https://connector.get-ryze.ai/mcp, kept as the [mcp_servers.ryze] table in config.toml |
| Signing Codex in | OAuth in the browser through codex mcp login ryze or Authenticate, or a Ryze AI rk_live_ key kept in an environment variable that bearer_token_env_var names |
| Linking the Webflow site | Once, in Ryze AI, with a Webflow site API token, then the site and CMS collection are chosen |
| Webflow tools | 3 tools: webflow__read, webflow__write and webflow__delete |
| Can Codex change the site | Yes. It can create, update and delete CMS items, and with the optional Pages scope change static page titles, meta descriptions and Open Graph fields |
| Several sites | One Webflow connection per Ryze AI workspace, and a site token sees only its own site. To switch sites, disconnect and connect again with another token |
| Codex plan | Free, Go, Plus, Pro, Business, Edu and Enterprise include Codex. OpenAI marks MCP for Plus and up and for API keys, with no Free or Go column |
| Ryze AI price | SEO Starter, $129 per month after a 3-day free trial. Connecting is free; the Webflow tools need an active plan or trial |
| Webflow's own option for Codex | Webflow's hosted MCP server at https://mcp.webflow.com/mcp with OAuth. Its overview names Codex; it has no Codex install page |
| Last checked | Webflow facts November 15, 2026; Codex facts November 14, 2026. No Webflow call and no step inside Codex was run |
Before you start
- An OpenAI plan that includes Codex. OpenAI lists Codex in ChatGPT Free, Go, Plus, Pro, Business, Edu and Enterprise. On Free and Go its pricing page shows Codex in the desktop app only, subject to rollout, so use the app steps on those plans and skip the CLI and the IDE extension. Plus and higher add both. The MCP row of the feature table covers Plus, Pro, Business, Enterprise / Education and API key sign-in and has no Free or Go column, so OpenAI does not say whether MCP servers work there. Codex also runs on an OpenAI API key in the CLI, SDK or IDE extension, billed at API pricing.
- A Webflow role that can create a site token. Webflow says only site administrators can create a site API token. A token works for the one site it was made on, so you need one token for each site you want Codex to reach.
- A Ryze AI workspace on a plan or free trial. SEO Starter is $129 per month with a 3-day free trial. Connecting the Ryze AI connector is free, but the Webflow tools need any active Ryze AI plan or trial.
How to connect Codex to Webflow with the CLI
The first two steps create the Webflow token and link it in Ryze AI. The next two add the server to Codex and sign in. The last asks a first question. The server URL is the same for every user.
Generate a site API token in Webflow
In Webflow open Site settings, then Apps & Integrations, scroll to API access and click Generate API token. Name it, set CMS to Read and write and Sites to Read-only, and optionally set Pages to Read and write if you want page titles and meta descriptions edited. Generate the token and copy it, because Webflow shows it once.
Connect Webflow in Ryze AI
Create a Ryze AI account or sign in, open Integrations and click Connect on the Webflow card. Paste the site token, then pick the site that hosts your blog and the CMS collection that articles go to.
Add the Ryze AI server to Codex
Run codex mcp add ryze --url https://connector.get-ryze.ai/mcp. In the ChatGPT desktop app or the IDE extension, use the MCP servers settings instead (see the sections below). All three share one MCP configuration.
Sign in and allow the connection
Run codex mcp login ryze, sign in on the Ryze AI page and click Allow connection. On a machine with no local browser, add --no-browser, open the printed URL elsewhere and paste the full redirect URL back into the terminal. Inside a running CLI session, /mcp login ryze starts the same sign-in.
Check the server and ask your first question
Run codex mcp list, or type /mcp inside the Codex TUI, to see the ryze server. Then ask: List the CMS collections on my Webflow site and the fields each one has.
codex mcp add ryze --url https://connector.get-ryze.ai/mcpcodex mcp login ryzeThe CLI is the shortest route. The first command writes the server into ~/.codex/config.toml and the second starts the OAuth sign-in. Run codex mcp get ryze to see the saved entry and codex mcp logout ryze to drop the stored sign-in. OpenAI's command reference says login and logout work only for Streamable HTTP servers that support OAuth, which the Ryze AI connector does.
The Ryze AI help article for Webflow covers the Webflow side of the connection, and the Ryze AI agent API help page covers API keys.
Sources: OpenAI Codex MCP, Codex command reference, Ryze AI Webflow guide. Checked November 14, 2026.
ChatGPT desktop app and IDE extension
The ChatGPT desktop app, the Codex CLI and the IDE extension share one MCP configuration, so a server added in one place shows up in the other two. Add it by hand in the app or the extension with the steps below. OpenAI's documentation used the name Codex app until July 9, 2026, when Codex became part of the ChatGPT desktop app, so older posts may use the old name.
ChatGPT desktop app (Codex)
- Open Settings, then select MCP servers.
- Select Add server, enter the name ryze, choose Streamable HTTP and enter https://connector.get-ryze.ai/mcp.
- Save, then select Restart.
- Select Authenticate next to ryze and finish the Ryze AI sign-in. The server list marks servers that still need OAuth, and /mcp in the composer shows the connected ones.
Codex IDE extension
- Open the gear menu, then select MCP servers.
- Select Add server, enter the name ryze, choose Streamable HTTP and enter https://connector.get-ryze.ai/mcp.
- Save, then select Restart extension.
- Select Authenticate and complete the Ryze AI sign-in.
config.toml and Codex's MCP rules
To keep the server in a file, edit ~/.codex/config.toml, or a project .codex/config.toml, which Codex reads only after you trust the project. OAuth is the default sign-in for a remote server, so one table is enough.
[mcp_servers.ryze]
url = "https://connector.get-ryze.ai/mcp"For a Ryze AI API key instead of OAuth, add bearer_token_env_var = "RYZE_API_KEY" to the same table and set that environment variable to your rk_live_ key. The setting holds the variable name; the key itself stays in the environment. Codex waits 10 seconds for a server to start and 60 seconds for a tool call by default; startup_timeout_sec and tool_timeout_sec raise either one per server.
OpenAI's Codex Cloud page does not mention MCP, and its MCP page warns that local MCP servers and transports may not be available in the cloud, so this page does not say the connector works in Codex cloud tasks. The Ryze AI connector was not tested end to end in Codex, and no Webflow call was run for this guide; the test record further down lists what was checked.
Codex and MCP servers: the rules in one table
OpenAI's Codex pages, read on November 14, 2026, set the rules below for every MCP server Codex loads. The ryze entry for Webflow follows them like any other server.
| Topic | What OpenAI documents |
|---|---|
| Surfaces that take a server | Codex CLI, the ChatGPT desktop app and the Codex IDE extension; a server set up in one is ready in the other two |
| Settings file | ~/.codex/config.toml, one [mcp_servers.<name>] table per server; a project .codex/config.toml loads only in a trusted project |
| Transports | STDIO for a local process and Streamable HTTP for a server at an address; no other transport is listed |
| Remote sign-in | OAuth by default, with Client ID Metadata Documents or dynamic client registration; also bearer tokens, static or environment headers and a header helper |
| Scopes requested | From config or --scopes at login; otherwise from the server's first WWW-Authenticate challenge, then its protected resource metadata |
| Approval rules | Per-server and per-tool modes, a rule that a tool with a destructive annotation needs approval unless it also has a read annotation, and Approve for me, which sends requests to a reviewer agent |
| Tool lists | enabled_tools is an allow list and disabled_tools a deny list; since CLI 0.143.0 MCP tools are found through tool search by default |
| Managing servers | codex mcp list, get, remove, login and logout; /mcp in a session; Settings > MCP servers in the app; the gear menu in the extension |
| Plugins | One directory shared with ChatGPT: the Plugins tab in the app and on the web, /plugins in the CLI, none in the IDE extension |
| Admin controls | An mcp_servers approved list in requirements.toml matches a server by name and URL; an empty list turns every server off on the local client |
| Web and phone | ChatGPT on the web reads no local Codex files and takes a custom server as a plugin at chatgpt.com/plugins; the mobile page describes no way to add one |
Sources: OpenAI Codex MCP, Codex command reference, Codex config reference, Agent approvals and security, Codex plugins, Managed configuration, Codex pricing. Checked November 14, 2026.
Claude, ChatGPT and Cursor
The same URL works in other MCP clients. The site is connected once in Ryze AI, so nothing changes in Webflow.
Claude and ChatGPT
In Claude, add https://connector.get-ryze.ai/mcp as a custom connector under Customize, Connectors. In ChatGPT, OpenAI documents full custom MCP servers on Business and Enterprise/Edu and read and fetch only on Pro. Webflow's own server has a Claude connector and a ChatGPT app of its own, described under the ways to connect.
Cursor
Add the server to .cursor/mcp.json with the same URL.
{ "mcpServers": { "ryze": { "url": "https://connector.get-ryze.ai/mcp" } } }Webflow access: site token and scopes
Webflow never talks to Codex directly. Ryze AI holds the Webflow site token, and Codex signs in to Ryze AI with OAuth. Three things decide what Codex can change.
- The scopes on the site token
- The token you paste into Ryze AI sets the ceiling. With CMS Read and write and Sites Read-only, Codex works on CMS collections and items. Page titles and meta descriptions need the optional Pages scope.
- The one site the token belongs to
- A site token only sees the site it was created on, and Ryze AI keeps one Webflow connection per workspace. Webflow allows up to 5 tokens per site.
- The approval mode in Codex and Ryze AI
- Codex approval settings decide whether it asks before a write or delete. In the Ryze AI app chat the approvals picker starts on Skip all approvals; that setting does not apply to Codex.
Token scopes behind each call
Webflow names each scope as a read and write pair. The table lists the scopes of the recommended token and what Webflow's reference says each one covers. Which Webflow endpoints a Ryze AI tool calls is not documented by Ryze AI, so the last column says what each scope allows in plain terms.
| Scope on the token | What Webflow says it covers | What Codex can do with it |
|---|---|---|
| CMS: Read and write (cms:read, cms:write) | List Collections and List Items need cms:read. Create, Update, Delete and Publish Items, and the live-item calls, need cms:write | List collections and items, create and update items as drafts or live, delete items |
| Sites: Read-only (sites:read) | List Sites needs sites:read | Read the site's details |
| Pages: Read and write (pages:read, pages:write), optional | List Pages and Get Page Metadata need pages:read. Update Page Metadata needs pages:write | List static pages and change a page title, meta description and Open Graph fields, once you set this scope |
Some things stay out of reach on the recommended token. Webflow lists sites:write for its Publish Site endpoint, and the recommended token has Sites set to Read-only. Ryze AI says webflow__write can publish the site, but that was not tested here, so do not count on a full site publish without checking. Publishing CMS items needs only cms:write. The token also has no access to assets, forms, components, ecommerce or comments, and Webflow says site tokens cannot use the custom code endpoints at all.
Sources: Webflow site tokens, Webflow scopes, Webflow Publish Site, Webflow List Pages, Ryze AI Webflow guide. Checked November 15, 2026.
Removing access
To remove access, revoke the token in Webflow under Site settings, Apps & integrations, API access. In Ryze AI, click View on the Webflow card and disconnect it with the trash icon. In Codex, codex mcp logout ryze removes the stored sign-in and codex mcp remove ryze deletes the server entry. Webflow also expires a site token after 365 consecutive days without use.
What Codex can do in Webflow
The Ryze AI connector exposes 3 Webflow tools. Codex calls them by these names through the ryze server. The names come from the Ryze AI app source and were not seen live on a connected account.
| Tool | Type | What it does |
|---|---|---|
| webflow__read | Read | Reads from the connected Webflow site through the Webflow Data API (GET), such as sites, pages, collections and collection items |
| webflow__write | Write | Creates or updates resources on the connected site, such as CMS items (live or draft) and static page SEO and Open Graph fields, and can publish the site |
| webflow__delete | Delete | Deletes a resource on the connected site by path, such as a CMS item |
These tools do not design pages, edit styles or work with the Designer; Webflow's own MCP server covers that. Reading pages and changing page titles or meta descriptions needs the optional Pages scope on the token. Required image, file or multi-reference fields cannot be filled automatically, so make them optional or give them a default. If the collection has other required fields, Ryze AI fills them with a valid value copied from existing items, or tells you at setup which field to make optional.
Approvals in Codex
Codex lets you set approvals per server. In config.toml, default_tools_approval_mode can be auto, prompt, writes or approve; writes prompts for tools that are not marked read-only, and it is the only value OpenAI explains in words. Per-tool overrides use tools.<tool>.approval_mode, and enabled_tools and disabled_tools work as allow and deny lists. Two rules sit on top: a tool that advertises a destructive annotation always needs approval unless it also advertises a read annotation, and Approve for me hands requests to a reviewer agent. Which Ryze AI tools carry those annotations is not documented, so set the mode yourself instead of relying on them. In the Ryze AI app chat, the Tool approvals picker starts on Skip all approvals; switch it to Approve write & delete or Manual approve in the message box. Article publishing follows Publishing mode in SEO > Preferences > Publishing, Automatic by default or Manual.
[mcp_servers.ryze]
url = "https://connector.get-ryze.ai/mcp"
default_tools_approval_mode = "writes"
# Keep delete out of Codex entirely
disabled_tools = ["webflow__delete"]Limits in numbers
Webflow and Codex each set limits on what Codex can ask for. The Webflow figures come from its Data API pages, because the Ryze AI connection uses a site token and the Data API limit for the site's plan applies to it, counted per API key. All figures were read on the dates in the sources line.
| Limit | Number or rule |
|---|---|
| Data API requests per minute | Starter and Basic plans 60; CMS, eCommerce and Business 120; Enterprise custom (Webflow rate limits page) |
| When the limit is hit | HTTP 429 Too Many Requests with a Retry-After header, typically 60 seconds, and the error code too_many_requests (Webflow rate limits page) |
| Site publishes | One successful publish per minute (Webflow rate limits and Publish Site pages) |
| Items per list request | Up to 100 records, paged with offset (Webflow List Items page) |
| Items per bulk write | Up to 100 items per request for create, update, live update and unpublish (Webflow item pages) |
| Fields per collection | Up to 60 fields in a collection schema (Webflow manage collections page) |
| Tokens per site | Up to 5 site tokens, each expiring after 365 consecutive days without use (Webflow site token page) |
| Codex timeouts | 10 seconds to start a server and 60 seconds per tool call by default, both set per server (OpenAI config reference) |
Sources: Webflow rate limits, Webflow Publish Site, Webflow List Items, Webflow Create Items, Webflow manage collections, Webflow site tokens, OpenAI Codex config reference. Checked November 15, 2026.
First 3 prompts and 10 jobs for Codex
Each answer comes from your own site, so this page describes what comes back instead of showing sample output. Codex works with the ryze server once it is signed in, and you can name the tool in the prompt if you want a specific one.
1. Map the CMS
List the CMS collections on my Webflow site and the fields each one has.
Tools used: webflow__read
What comes back: The collection names with their fields, so you can see which collection holds your blog and which fields are required.
2. Find gaps in blog items
List the items in my blog collection with name, slug and publish status, and tell me which ones have an empty summary or no featured image.
Tools used: webflow__read
What comes back: A list of items with their status and the ones missing those fields. The check runs on the field data Codex receives, so a long collection may need to be read in several requests of up to 100 items.
3. Draft a new item
Create a draft item in my blog collection with this title, slug and body, and leave it unpublished.
Tools used: webflow__write
What comes back: A new CMS item in Draft status. Webflow keeps a never-published item as a draft until someone publishes it, so nothing goes live from this prompt.
Page-level edits, such as rewriting a title and meta description, need the Pages Read and write scope on the token. Without it Codex can still change CMS items.
10 jobs to hand to Codex
Ten jobs you can give Codex once the ryze server is signed in, each with the Ryze AI tool behind it. The last column says whether the recommended token (CMS Read and write, Sites Read-only, no Pages scope) covers it.
| Job | What to ask Codex | Tool | On the default connection |
|---|---|---|---|
| Map the collections | List the CMS collections on the site and the fields each one has | webflow__read | Yes |
| Audit the blog list | List the items in the blog collection with name, slug and publish status | webflow__read | Yes |
| Find empty fields | Find blog items where the summary or the featured image is empty | webflow__read | Yes |
| Read site details | Show the site's name, custom domains and locales | webflow__read | Yes |
| Create a draft | Create a draft CMS item from a title, slug and body I give you | webflow__write | Yes |
| Update an item | Update the excerpt or the body of an existing CMS item | webflow__write | Yes |
| Edit live content | Create or update an item directly on the live site | webflow__write | Yes |
| Delete an item | Delete a CMS item I no longer need | webflow__delete | Yes |
| Find weak page metadata | List static pages whose title or meta description is empty | webflow__read | No, needs the Pages scope |
| Rewrite page SEO fields | Rewrite a static page's title, meta description and Open Graph fields | webflow__write | No, needs the Pages scope |
5 ways to connect Codex to Webflow
Five ways can put a Webflow site in reach of Codex. This guide uses the first, the Ryze AI connector, as the main way: one codex mcp add command covers the CLI, the desktop app and the IDE extension, and the Webflow token stays in Ryze AI. The other four were read on their vendors' pages on November 15, 2026. Each row gives the Codex setup as far as those pages and OpenAI's pages describe it; none of the four was tried in Codex.
| Way | Where it runs | Setup in Codex | What it reaches | Price |
|---|---|---|---|---|
| Ryze AI connector (the main way) | Hosted by Ryze AI, one address for every user | codex mcp add ryze --url https://connector.get-ryze.ai/mcp, then codex mcp login ryze, or Add server in the app or the extension. Webflow is linked in Ryze AI with a site token | 3 tools to read, write and delete CMS items and, with the Pages scope, page SEO fields, on one site | SEO Starter, $129 per month with a 3-day free trial; any active Ryze AI plan or trial unlocks the tools |
| Webflow MCP server (remote) | Hosted by Webflow at https://mcp.webflow.com/mcp | Webflow's overview page names Codex, but there is no Codex install page. The getting started page says any agent that supports MCP servers can connect manually with the URL, so codex mcp add webflow --url https://mcp.webflow.com/mcp is the expected form. Webflow documents OAuth sign-in and does not describe Codex's login | Design and build tools for pages, elements, styles and components, plus the CMS, page SEO metadata, assets, forms and more, inside your Webflow roles. Only site owners and admins can authorize it, and each authorization covers one workspace | No price stated for the server; Webflow's pricing page lists it among Starter and Basic site plan features |
| webflow-mcp-server on npm | On your computer, run with npx | A local command with your token in the environment, in the form codex mcp add webflow-local --env WEBFLOW_TOKEN=... -- npx -y webflow-mcp-server@latest. The README shows Cursor and Claude Desktop configs, not Codex | Webflow's open-source server, version 1.0.0 from September 17, 2025. It needs Node.js 22.3.0 or higher, and Designer features need your own registered MCP Bridge App | Free, MIT licence per the GitHub API |
| Zapier MCP | Hosted by Zapier | Create a Zapier MCP server, choose Webflow actions and add the address to Codex. Zapier's quickstart lists Codex among popular clients | Actions such as Create Item, Create Live Item, Update Item, Find Item and API Request (Beta) | Available to all Zapier accounts; one tool call uses 2 tasks |
| Kvalifik mcp-router | A desktop app on your computer, macOS and Windows x64 | Authorize Webflow in the app, enable projects and permissions, then connect an AI app from the Apps screen. Its README names Codex and says it configures a detected local Codex MCP client | Webflow projects across several workspaces through one connection, with per-project access levels | Free, under a custom source-available licence; not affiliated with Webflow per its README |
Options that do not fit Codex
- Webflow's one-click installs. The Webflow connector in Anthropic's directory, the Webflow app in ChatGPT and the plugin in Cursor's marketplace each name only their own assistant. OpenAI says ChatGPT and Codex share one plugin directory, but whether the Webflow app shows up in Codex was not checked, and the ChatGPT listing page could not be read outside a signed-in browser.
- Webflow Beta MCP server. Experimental tools and early features at https://mcp.webflow.com/beta/mcp, added manually. Its page gives no Codex steps, and production work belongs on the main server.
- Composio. Its Webflow toolkit lists Claude, ChatGPT and Cursor, and Webflow connections there need your own OAuth app registered with Webflow.
- kapilduraphe/webflow-mcp-server. A community server with 2 read-only tools, get_sites and get_site, and no CMS access. Its README names Claude Desktop only.
Which one to pick
Ryze AI is the best way to connect Codex to Webflow for creating and updating CMS blog items from a scoped site token, though it cannot design pages or edit styles, which Webflow's own MCP server does. Pick Webflow's server when the work is building pages and components or reading Analyze and AEO data, and you are a site owner or admin who can authorize it. Pick the Ryze AI connector when the work is content in a CMS collection, you want a limited token, or you want the same server address to serve other Ryze AI platforms. Both can sit in the same config.toml under different names.
Sources: Webflow MCP overview, Webflow MCP getting started, Webflow MCP FAQ, Webflow pricing, webflow/mcp-server on GitHub, webflow-mcp-server on npm, Zapier MCP for Webflow, Zapier MCP quickstart, Kvalifik/mcp-router, Webflow Beta MCP server, Composio Webflow toolkit, kapilduraphe/webflow-mcp-server. Checked November 15, 2026.
Codex, Webflow and MCP: dates that matter
| Date | What happened |
|---|---|
| April 8, 2025 | Webflow introduced its official MCP server in its changelog, for tools such as Cursor and Claude Desktop. |
| September 4, 2025 | Webflow's MCP server added Designer API support, with a companion app that installs during authorization and a Node.js 22.3.0 minimum. |
| October 3, 2025 | Codex CLI 0.44.0 added support for Streamable HTTP MCP servers. |
| October 9, 2025 | Codex CLI 0.46.0 let codex mcp add register Streamable HTTP servers with a bearer token or OAuth, then behind an experimental flag. |
| November 24, 2025 | Webflow moved its MCP server from SSE to HTTP, replacing https://mcp.webflow.com/sse with https://mcp.webflow.com/mcp. |
| December 9, 2025 | Webflow launched a Beta MCP server at https://mcp.webflow.com/beta/mcp and cut its data tools from 46 or more to 18. |
| January 17, 2026 | Webflow's changelog marked the /sse endpoint fully deprecated, with MCP v1.0.1. |
| July 9, 2026 | Codex became part of the ChatGPT desktop app, so the surface is now named the ChatGPT desktop app. |
| September 21, 2026 | Webflow released MCP v2.1 with GSAP interactions, Webflow Cloud and Campaigns tools and CMS field groups. A v2.2 is named in a migration guide with no date given. |
| October 7, 2026 | Codex CLI 0.161.0 added /mcp login <name> inside a running session. |
| November 13, 2026 | Codex CLI 0.169.0 was the newest release at the check date. It keeps project configuration and MCP servers off in untrusted directories for codex exec. |
Sources: Webflow changelog, April 8, 2025, Webflow changelog, September 4, 2025, Webflow changelog, November 24, 2025, Webflow changelog, December 9, 2025, Webflow changelog, January 17, 2026, Webflow changelog, September 21, 2026, Codex CLI 0.44.0 release, Codex CLI 0.46.0 release, Codex changelog. Checked November 15, 2026.
How this guide was tested
No call to Webflow was run for this guide. No Webflow account was connected to the Ryze AI connector when the fact packs were built, so the tool list, the scopes and the jobs above rest on Ryze AI's own documentation, its app source and Webflow's developer pages, each read on the dates shown.
| What was run | What came back |
|---|---|
| Webflow's developer pages (MCP overview, getting started, FAQ, site tokens, scopes, rate limits, item and page references) read | Opened on November 15, 2026 and re-read by a second reviewer; the figures and scope names on this page come from them |
| OpenAI's Codex pages (MCP, command reference, config reference, plugins, pricing, changelog) read | Opened on November 14, 2026 and re-read by a second reviewer; the commands, menu names and defaults on this page come from them |
| Ryze AI facts for Webflow and Codex checked | The 3 tool names, the token scopes and the Codex steps match the Ryze AI facts files, the Ryze AI help center and the app source |
Not run: any Webflow call through the connector, codex mcp add, codex mcp login, Add server and Authenticate in the app or the extension, and any of the other four ways to connect. The tool names come from the Ryze AI app source and were not seen on a live account, and the Ryze AI sign-in was not tried in Codex.
Errors and fixes
No error message was collected from a live run, so the rows below come from the vendors' documentation and are worded as documented behavior.
- The ryze server is not listed
- Run codex mcp list or type /mcp in the session. In the app, select Restart after saving the server; in the IDE extension, select Restart extension. OpenAI does not say whether a running CLI session picks up a new server without a restart.
- Codex shows the server but tool calls fail with a sign-in prompt
- Run codex mcp login ryze again, or select Authenticate in the app or the extension. Codex 0.154.0 shows the sign-in prompt when a token refresh fails and does not replay the rejected tool call.
- A project config.toml is ignored
- Codex reads a project .codex/config.toml only after you trust the project. Put the table in ~/.codex/config.toml to use it everywhere.
- The server takes too long to start or a call times out
- The defaults are 10 seconds to start and 60 seconds per tool call. Raise startup_timeout_sec or tool_timeout_sec in the [mcp_servers.ryze] table.
- Codex cannot change a page title or meta description
- The token has no Pages scope. Generate a token with Pages set to Read and write, then reconnect Webflow in Ryze AI.
- Publishing fails or items are not created
- Publishing fails with a token that has no CMS write access. Check that CMS is set to Read and write. If the collection has required image, file or multi-reference fields, make them optional or give them a default.
- Webflow answers 429 Too Many Requests
- Webflow documents HTTP 429 with a Retry-After header, typically 60 seconds, when the site plan's per-minute limit is exceeded. Wait, then retry with smaller batches.
- Codex reads the wrong site
- A site token only sees its own site and Ryze AI keeps one Webflow connection per workspace. Click View on the Webflow card, disconnect with the trash icon and connect with the other site's token.
- Free or Go plan and no CLI
- OpenAI's pricing page shows Codex in the desktop app only on Free and Go, subject to rollout. Use the desktop app steps.
Terms on this page
- Site API token
- A key created in a Webflow site's settings that lets an integration use the Webflow Data API on that one site, with the scopes chosen when it was made. Only site administrators can create one.
- Scope
- A permission on a token that decides which Webflow data it can reach. Scopes come in read and write pairs, such as cms:read and cms:write.
- CMS collection and item
- A collection is a group of CMS items that share a template, such as blog posts. An item is one record in it, such as a single post.
- Draft and changes in draft
- An item created or updated as a draft stays in Draft status. On an already published item, an update sets Changes in draft, and the live item stays as it was until the changes are published.
- MCP (Model Context Protocol)
- The open protocol that lets an AI client such as Codex call tools on a server such as the Ryze AI connector.
- Streamable HTTP
- The MCP transport for a server reached at an address. Codex supports it and STDIO, which is a local process started by a command.
- MCP Bridge App
- The companion app that installs when you authorize Webflow's own MCP server and links a live Designer session to it. Ryze AI does not use it.
Sources: Webflow site tokens, Webflow scopes, Webflow update items, Webflow MCP how it works, Model Context Protocol, OpenAI Codex MCP. Checked November 15, 2026.
Frequently asked questions
How do I connect Codex to Webflow?
Generate a Webflow site API token and connect it in a Ryze AI workspace. Then run codex mcp add ryze --url https://connector.get-ryze.ai/mcp, run codex mcp login ryze, sign in on the Ryze AI page and click Allow connection.
Is there a Webflow connector for Codex?
Yes, two main ones. The Ryze AI connector at https://connector.get-ryze.ai/mcp reaches a Webflow site through a site token. Webflow's own MCP server at https://mcp.webflow.com/mcp names Codex on its overview page, with no Codex install page. Zapier MCP and Kvalifik mcp-router also name Codex.
What is the Codex Webflow MCP setup?
With the Ryze AI connector it is one server named ryze at https://connector.get-ryze.ai/mcp, added with codex mcp add or Settings > MCP servers. With Webflow's server it is a Streamable HTTP server at https://mcp.webflow.com/mcp that signs in with Webflow OAuth.
Which Webflow MCP server should I use with Codex?
Use Webflow's server for designing pages and components, which needs a site owner or admin to authorize it. Use the Ryze AI connector for CMS items and page SEO fields on a token with limited scopes. The two can share a config.toml under different names.
Which Webflow token scopes does the Ryze AI connection need?
CMS set to Read and write and Sites set to Read-only. Pages Read and write is optional and is needed for page titles, meta descriptions and Open Graph edits. Only a site administrator can create the token.
Can Codex publish and delete Webflow content?
Codex can create and update CMS items as drafts or live, and delete items, with the 3 Ryze AI Webflow tools. Publishing a whole site is not guaranteed on the recommended token, because Webflow lists sites:write for it. Set approval modes in Codex to control writes.
Does Codex ask before it changes Webflow?
That depends on your Codex settings. default_tools_approval_mode can be auto, prompt, writes or approve, and disabled_tools can remove a tool such as webflow__delete. In the Ryze AI app chat the approvals picker starts on Skip all approvals.
Which Codex plans can add an MCP server?
OpenAI includes Codex in Free, Go, Plus, Pro, Business, Edu and Enterprise. Its feature table marks MCP for Plus, Pro, Business, Enterprise / Education and API key sign-in, with no Free or Go column. Free and Go show Codex in the desktop app only.
Do I need the CLI, or can I use the desktop app?
The desktop app works. The ChatGPT desktop app, the Codex CLI and the Codex IDE extension share one MCP configuration. In the app choose Settings > MCP servers > Add server, pick Streamable HTTP and enter the connector URL.
How much does it cost?
Connecting the Ryze AI connector is free. The Webflow tools need an active Ryze AI plan or trial: SEO Starter is $129 per month with a 3-day free trial, and annual billing takes 30% off the first year. Codex and Webflow plans are billed separately.
Can Codex work on several Webflow sites?
Not at once through Ryze AI. A site token sees only its own site and a workspace has one Webflow connection. To switch, click View on the Webflow card, disconnect and connect with the other site's token.
Does the Ryze AI connector work in Codex cloud tasks?
This guide does not claim it does. OpenAI's Codex Cloud page does not mention MCP and its MCP page says local servers and transports may not be available in the cloud. The steps here cover the CLI, the desktop app and the IDE extension.
What limits does Webflow set on API calls?
Webflow's Data API allows 60 requests per minute on Starter and Basic site plans and 120 on CMS, eCommerce and Business, counted per API key. Past that it returns HTTP 429 with a Retry-After header, and a site publish is limited to once per minute.
Was this guide tested in Codex?
No. No Webflow call and no step inside Codex was run. The commands and menu names come from OpenAI's pages read on November 14, 2026, and the Webflow facts from Webflow's pages read on November 15, 2026.