How to connect Codex to Framer

Connect your Framer project once in Ryze AI, add one MCP URL to OpenAI Codex, then ask Codex to read, create, update and publish CMS items.

Your MCP URL
https://connector.get-ryze.ai/mcp

Copies the link. In a terminal run codex mcp add ryze --url with it. See the steps

See pricing

By Ira Bodnar, Ryze AI · Updated · Test record: documentation only

Quick answer

The main way to connect Codex to Framer is the Ryze AI connector. Create a Framer API key and link the project to a Ryze AI workspace once, choosing the CMS collection to use. 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 covers all three. Framer also runs its own MCP server for Codex at https://mcp.framer.com/mcp, which this guide compares below.

  1. In Framer open Site Settings, General, API Keys and create a key
  2. In Ryze AI open Integrations, click Connect on Framer, paste the Project URL and the key, then pick a CMS collection
  3. In Codex run codex mcp add ryze --url https://connector.get-ryze.ai/mcp
  4. Run codex mcp login ryze, sign in on the Ryze AI page and click Allow connection

Codex to Framer at a glance

FactDetail
Main way to connectThe Ryze AI connector, a hosted MCP server that Codex reaches over Streamable HTTP
Server addresshttps://connector.get-ryze.ai/mcp, kept as the [mcp_servers.ryze] table in config.toml
Signing Codex inOAuth in the browser through codex mcp login ryze or Authenticate, or a Ryze AI rk_live_ key held in an environment variable that bearer_token_env_var names
Linking the Framer projectOnce, in Ryze AI: the Project URL from the Framer editor plus a Framer API key, then one CMS collection
Framer tools3 tools: framer__read, framer__write and framer__delete. They cover CMS collections and publishing, not pages or custom code
Can Codex change the siteYes, CMS items and a site publish. Codex approval modes decide whether it asks first
Other data in the same chatThe same server URL serves the other platforms connected in your Ryze AI workspace, so no second address is needed
Codex planFree, 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 priceSEO Starter, $129 per month after a 3-day free trial. Connecting is free; the Framer tools need an active plan or trial
Framer's own option for CodexFramer MCP at https://mcp.framer.com/mcp, signed in with OAuth, free during Framer's preview. Framer documents Codex setup for it
Last checkedVendor pages read November 14 and 15, 2026. No Framer or Codex step was run for this guide

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 Free and Go readers should use the desktop app steps. Plus and higher add the CLI and the IDE extension. Codex also runs with an OpenAI API key in the CLI, SDK or IDE extension, billed at API pricing. The MCP row of OpenAI's feature table names Plus, Pro, Business, Enterprise / Education and API key sign-in and has no Free or Go column; the MCP page itself names no extra plan.
  • A Framer project with a CMS collection and access to its Site Settings. The connection needs a Framer API key from Site Settings, General, API Keys, and the project URL from the editor address bar. Publishing needs at least one CMS collection in the project that the key can reach.
  • A Ryze AI workspace on a plan or free trial. SEO Starter is $129 per month with a 3-day free trial. Adding the Ryze AI connector to Codex is free, but the Framer tools need any active Ryze AI plan or trial.

How to connect Codex to Framer with the CLI

Two steps happen in Framer and Ryze AI, three in Codex. The server URL is the same for every user.

  1. Create an API key in Framer

    Open the project in Framer, click the settings icon at the top right to open Site Settings, go to General and scroll to API Keys. Create a key and copy it. Framer says these keys authenticate as the user who created them and are bound to one project.

  2. Connect Framer in Ryze AI

    Sign in to Ryze AI, open Integrations and click Connect on the Framer card. Paste the Project URL from the Framer editor address bar and the API key, then click Continue. The URL must include the 20-character project id; you can paste just the id instead. The address of the published site does not work. In the window that opens, choose a CMS collection under Choose a Collection and click Save.

  3. 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 next section). All three share one MCP configuration.

  4. Sign in and allow the connection

    Run codex mcp login ryze, sign in on the Ryze AI page and click Allow connection. Without a local browser, add --no-browser, open the printed URL and paste the full redirect URL back into the terminal. Inside a running CLI session, /mcp login ryze starts the same sign-in.

  5. 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 every CMS collection in my Framer project and show the fields of each.

codex mcp add ryze --url https://connector.get-ryze.ai/mcpcodex mcp login ryze

The first command registers the server and the second starts the OAuth sign-in. Afterwards codex mcp list shows the server, and /mcp does the same inside the codex TUI. OpenAI's pages do not say whether a CLI session that is already running picks up a newly added server, so start a new session if ryze is missing from the list.

The Ryze AI help article for Framer covers the Framer side of the connection, and the Ryze AI agent API help page covers API keys.

Sources: OpenAI Codex MCP, Codex command reference, Ryze AI Framer guide, Framer Server API quick start. Checked November 14 and 15, 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 shows up in the others. The app and the extension take the same values through a form.

ChatGPT desktop app (Codex)

  1. Open Settings, then select MCP servers.
  2. Select Add server, enter the name ryze, choose Streamable HTTP and enter https://connector.get-ryze.ai/mcp.
  3. Save, then select Restart.
  4. Select Authenticate next to ryze and finish the Ryze AI sign-in. Typing /mcp in the composer lists connected servers.

Codex IDE extension

  1. Open the gear menu, then select MCP servers.
  2. Select Add server, enter the name ryze, choose Streamable HTTP and enter https://connector.get-ryze.ai/mcp.
  3. Save, then select Restart extension.
  4. 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. A project can carry its own .codex/config.toml, which Codex reads only after you trust the project. OAuth is the default for an HTTP server, so run codex mcp login ryze after saving.

[mcp_servers.ryze] url = "https://connector.get-ryze.ai/mcp" # Optional: raise the defaults (10 and 60 seconds) startup_timeout_sec = 20 tool_timeout_sec = 120

To sign in with a Ryze AI API key instead of OAuth, add bearer_token_env_var = "RYZE_API_KEY" to the same table and put your rk_live_ key in that environment variable. Keep the key out of the file. The --bearer-token-env-var option of codex mcp add writes the same line.

OpenAI's Codex Cloud page does not mention MCP, so this guide does not say the connector works in Codex cloud tasks. It covers the CLI, the ChatGPT desktop app and the IDE extension only.

Codex and MCP servers: the rules in one table

OpenAI's Codex pages, read on November 14, 2026, set these rules for every MCP server Codex loads. The ryze server and a second server for Framer follow them alike.

TopicWhat OpenAI documents
Where servers are addedcodex mcp add in the CLI, Settings > MCP servers in the ChatGPT desktop app, the gear menu > MCP servers in the IDE extension, or a [mcp_servers.<name>] table in config.toml
TransportsSTDIO for a local process and Streamable HTTP for a server at an address; the MCP page lists no other
Remote sign-inOAuth by default, with Client ID Metadata Documents or dynamic client registration; bearer tokens, static or environment headers and a header helper are also supported
Approvaldefault_tools_approval_mode takes auto, prompt, writes or approve, with tools.<tool>.approval_mode for one tool. Only writes is explained: it asks before tools not marked read-only
Tool listsenabled_tools is an allow list and disabled_tools a deny list, applied after it
Timeoutsstartup_timeout_sec defaults to 10 seconds and tool_timeout_sec to 60, both set per server
PluginsOne directory shared with ChatGPT: the Plugins tab in the desktop app, /plugins in the CLI, none in the IDE extension
PlanCodex is included in Free, Go, Plus, Pro, Business, Edu and Enterprise; Free and Go get the desktop app only, subject to rollout
Admin controlsAn mcp_servers approved list in requirements.toml runs a server only when its name and URL or command both match

Sources: OpenAI Codex MCP, Codex command reference, Codex config reference, Codex pricing, Codex plugins, Managed configuration. Checked November 14 and 15, 2026.

Claude, ChatGPT and Cursor

The same URL works in other MCP clients. The Framer project is connected once in Ryze AI, so nothing changes on the Framer side.

Claude and ChatGPT

In Claude, add https://connector.get-ryze.ai/mcp as a custom connector under Customize, Connectors. Ryze AI also lists a one-time connection link for Framer in Claude and ChatGPT. In ChatGPT, add the URL as a custom MCP server where your plan allows it. Connect Framer in Ryze AI once and every client sees it.

Cursor

Add the server to .cursor/mcp.json with the same URL.

{ "mcpServers": { "ryze": { "url": "https://connector.get-ryze.ai/mcp" } } }

Framer access: the API key

In this route Framer never talks to Codex. Ryze AI holds the Framer API key, and Codex signs in to Ryze AI. Three things decide what Codex can change in the project.

The Framer API key
Framer says a key authenticates as the user who created it and is bound to one project. Framer describes no scopes, read-only keys or other permission options for a key.
The Ryze AI tools
Three tools exist for Framer: one reads, one writes and one deletes. They reach CMS collections and the site publish step. Pages, layouts, components, custom code and redirects are outside them.
Codex approval settings
Per-server and per-tool approval modes and the allow and deny lists in config.toml decide which calls Codex pauses on. The Approvals section below has an example.

What the key and the tools cover

A Framer Server API key carries no list of scopes. The table pairs the key with the two Framer roles that matter for CMS work. Framer does not state on its Server API pages how a key's reach follows its creator's role, so the last two rows are an inference and are marked as one.

ItemWhat Framer saysWhat it means for Codex
Server API key"These keys authenticate your script as the user who created them, and are bound to a specific project."Codex works on the one project the key belongs to, as the person who created the key
ScopesThe quick start describes no scopes, read-only keys or permission options for a keyA key cannot be limited to reading. Use approval modes and the deny list in Codex to hold back writes
Content permission"Manage CMS content, localization, and other content-related changes."The kind of access CMS item changes need. The link between a key and this role is unverified
Deploy permission"Publish and manage site deployments." With staging off, only members with Deploy permission can publish straight to the live siteA publish may need the key's creator to hold it. Framer does not say what happens for a key made by a member without it

Several things stay out of reach through the Ryze AI Framer tools. They do not edit pages, layouts, components or the canvas, custom code or redirects, and the facts list no localization, branch or project-settings tool even though Framer's own API can reach them. A workspace holds one Framer connection, so a second project needs the connection swapped. Whether framer__write can write to a collection other than the one picked at connection time is not stated.

Sources: Framer Server API quick start, Framer Server API introduction, Framer member roles and permissions, Ryze AI Framer guide. Checked November 14 and 15, 2026.

Removing access

None of the Framer pages read describes deleting or rotating an API key, so how to revoke one in Framer is unverified here. In Ryze AI, click View on the Framer card and disconnect with the trash icon; a new connection can then be made. In Codex, codex mcp logout ryze clears the stored OAuth credentials and codex mcp remove ryze deletes the entry. Setting enabled = false in the [mcp_servers.ryze] table pauses the server and keeps it.

What Codex can do in Framer

The Ryze AI connector exposes three Framer tools, which Codex calls by these names through the ryze server. They come from Ryze AI's integration facts; no Framer account was connected for this guide, so the names were not read from a live connection.

ToolTypeWhat it does
framer__readReadLists the collections of the connected project, a collection's fields, its items, or one item with its field data.
framer__writeWriteCreates or updates CMS items in a collection, matched by slug or id, or publishes the site so changes go live.
framer__deleteDeleteRemoves CMS items from a collection by id. A publish afterwards makes the removal live.

Updates by slug change the existing item in place, and nothing reaches visitors until a publish. Publishing is one mode of framer__write, so an approval prompt on that tool covers both item changes and going live. Pages, custom code and redirects are not in these tools, even though the Framer card in Ryze AI describes them in general terms.

Approvals in Codex

Codex lets you set approvals per server and per tool. default_tools_approval_mode can be auto, prompt, writes or approve, and writes asks before tools that are not marked read-only. A tool that advertises a destructive annotation always needs approval unless it also advertises a read annotation, and with Approve for me chosen, a reviewer agent answers those requests. Which annotations the three Framer tools carry was not checked, so the sure way to keep deletes out is the deny list. The Ryze AI chat inside the app has its own setting and starts on Skip all approvals; pick Approve write & delete or Manual approve in its Tool approvals picker if you use it too.

[mcp_servers.ryze] url = "https://connector.get-ryze.ai/mcp" default_tools_approval_mode = "writes" disabled_tools = ["framer__delete"] # Or ask before every publish and item change [mcp_servers.ryze.tools.framer__write] approval_mode = "prompt"

Limits in numbers

Codex, Framer and Ryze AI each set limits on what a request can do. The figures come from the vendor pages named under the table, each read on the date in its pack.

LimitNumber or rule
Codex MCP startup timeout10 seconds by default (startup_timeout_sec), per server
Codex MCP tool call timeout60 seconds by default (tool_timeout_sec), per server
Framer Server API rate limitNone published. The introduction, quick start, reference and FAQ pages give no request quota
Framer Server API priceFree during open beta; Framer says it will likely charge per use with a monthly free allowance
Framer Server API after a pauseThe first commands after a cold start take a second or two
Framer Server API on failureFramer: "The Server API is not in any way transactional." A run that fails part way can leave some changes made
CMS collections per projectBasic 2; Pro 10, then $40 per 10 up to 40; Free plan projects 10; Enterprise custom
CMS items per projectBasic 1,000; Pro 2,500, then $20 per 10,000 up to 40,000; Enterprise custom
Framer MCP priceFree during preview on Basic, Pro and Enterprise, per Framer's pricing page
Ryze AI Framer connectionsOne per workspace; a connection link is refused while one exists
Ryze AI Content PlanUp to 90 articles per billing cycle and up to 3 a weekday on SEO Starter

Sources: OpenAI Codex MCP, Framer Server API FAQ, Framer pricing, Ryze AI Framer guide. Checked November 14 and 15, 2026.

First 3 prompts and 10 jobs for Codex

Each answer comes from your own project, so this guide describes what comes back and shows no sample output. Collection and field names depend on how your project is built.

1. Map the CMS

List every CMS collection in my Framer project, then show the fields of the collection I publish blog posts into.

Tools used: framer__read

What comes back: Collection names, then the field names and types of the one you named. Later prompts can use those exact field names.

2. Find items with empty SEO fields

Read the items in my blog collection and list the ones with an empty description or SEO title field, with their slugs.

Tools used: framer__read

What comes back: A list of slugs for items whose field is blank. The assistant reads the items and checks the fields, so the field names must match your collection.

3. Rewrite one field and hold the publish

Read the item with the slug <your-slug>, rewrite its description to under 155 characters and update the item. Do not publish yet.

Tools used: framer__read, then framer__write

What comes back: The item's current field data, then an update in place by slug. The change stays in the CMS until you ask for a publish as a separate step.

Ask for publishing in its own message so that you can review the CMS change first. If Codex asks to publish, that request goes through framer__write like any other item change.

10 jobs to hand to Codex

Ten jobs to give Codex once the ryze server is signed in, each with the Ryze AI tool it uses. Default connection means a Framer project connected in Ryze AI with an API key and a chosen CMS collection, on any active plan or trial. None of these jobs was run for this guide.

JobWhat to ask CodexToolOn the default connection
List the CMS collectionsList every CMS collection in the projectframer__readYes
Show a collection's fieldsShow the fields of the blog collection so later prompts use the right namesframer__readYes
List items with slugsList the items in the blog collection with their slugsframer__readYes
Read one itemRead the full field data of the item with this slug before editing itframer__readYes
Find empty fieldsFind items whose description or SEO field is emptyframer__readYes; the assistant reads the items and checks the fields
Create an itemCreate a new blog post item in the blog collection from this draftframer__writeYes; goes live only after a publish
Update an item by slugUpdate the item with this slug in placeframer__write (reads first)Yes
Rewrite one field in bulkRewrite the meta description of these items to under 155 charactersframer__read, framer__writeYes
Publish the sitePublish the site so the CMS changes go liveframer__writeYes; makes changes public, so ask for it as its own step
Remove outdated itemsDelete these items by id, then publishframer__delete (plus read and write)Yes, unless you put framer__delete on the deny list

6 ways to connect Codex to Framer

Six ways can put a Framer project 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, the Framer key stays in Ryze AI, and the same URL serves the other platforms in your workspace. The other five were read on their vendors' pages on November 15, 2026. None of the six was tried in Codex.

WayWhere it runsSetup in CodexWhat it reachesPrice
Ryze AI connector (the main way)Hosted by Ryze AI, one address for every usercodex mcp add ryze --url https://connector.get-ryze.ai/mcp, then codex mcp login ryze, or Add server in the app or the extension. Framer is linked in Ryze AI with a project URL and an API keyCMS collections: list, read, create, update, delete items, and publish the site. Content Plan articles publish into the collection you pickSEO Starter, $129 per month with a 3-day free trial; any active Ryze AI plan or trial runs the tools
Framer MCP, Framer's own serverHosted by Framer; the editor does not need to stay opencodex mcp add framer --url https://mcp.framer.com/mcp, sign in to Framer in the browser and approve, check with codex mcp list, then restart Codex and start a new chat. Framer also lists a Plugins directory install for Codex. Streamable HTTP with OAuthPer Framer: canvas, components, supported project settings and the CMS in projects your account can open, with publishing only when you ask. No localization at launch. Framer lists no tool names or countFree during preview on Basic, Pro and Enterprise; Codex usage follows your OpenAI plan
Framer External Agents (@framer/agent)On your computer, a local bridgeRun npx @framer/agent setup in the Codex terminal, then run the /framer skill and grant access to the project in the browser. Framer names Codex for itCanvas, components and the CMS, including creating, updating and deleting items; changes land on a branch. Supports localization, which Framer MCP does notNo price on Framer's page; @framer/agent 0.0.48 was published November 4, 2026
Tommy's MCP (Unframer plugin)A Framer plugin that must stay open in the editor, bridged through mcp.unframer.coOpen the plugin in the project, copy its MCP URL and add it to Codex. The docs give an installer command and manual steps for Codex Desktop and Codex CLI22 tools in the docs sidebar, among them CMS collection and item tools, page creation and color and text styles. Only the project that is openNo separate price on the Marketplace page; unframer.co lists React Export plans from $450 per year
Composio Framer toolkitHosted by ComposioAdd the Composio MCP address https://connect.composio.dev/mcp as a Streamable HTTP server and authenticate, using your own Framer API key. Composio's Framer page shows ChatGPT setup and does not name Codex156 tools listed for Framer: CMS collections and items, pages, components, code files, branches, redirects, locales and publishFree plan: 10,000 tool calls per month; Standard $18 per seat per month
framer-mcp-server by ericpjtsai (open source)A local Node process using the Server APIThe README shows .mcp.json for Claude Code and Cursor settings, with FRAMER_PROJECT_URL and FRAMER_API_KEY. For Codex, OpenAI's STDIO syntax would be codex mcp add framer-local --env FRAMER_PROJECT_URL=... --env FRAMER_API_KEY=... -- npx -y framer-mcp-server. This line was built from the two pages and not tried14 tools in the README: CMS items, page context, canvas changes, code files, local preview and publishFree, MIT license. 0 GitHub stars and last push April 4, 2026 on November 15

Options that do not fit this job

  • The Framer Server API on its own. It is a Node package that connects over a persistent WebSocket and suits scripts and servers. No assistant is named for it, and Framer says an HTTP layer must be built on top for HTTP use.
  • Zapier MCP. Zapier has no Framer app page, which returned a 404 on November 15, 2026, so Zapier MCP has no direct Framer actions. A third-party Framer plugin that posts webhook records into the CMS is the nearest indirect path.
  • Sheshiyer/framer-plugin-mcp. The most-starred Framer MCP repository found, with 37 stars, but it creates and builds Framer plugin projects. It does not read or edit a Framer site or its CMS.

Which one to pick

Ryze AI is the best way to connect Codex to Framer for reading, editing and publishing CMS items, with a caveat: its three tools stop at the CMS and the publish step, it needs an active Ryze AI plan or trial, and a workspace holds one Framer connection. Choose Framer MCP when Codex should work on pages, layouts or components, since it is hosted by Framer, uses OAuth, is free during preview and has no tool list to learn. Choose External Agents for localization. The two hosted servers can sit side by side in config.toml as ryze and framer. The Framer MCP server page has the full Ryze AI tool reference.

Sources: Framer: getting started with Framer MCP, Framer: what you can do with Framer MCP, Framer MCP, Framer External Agents, Framer Server API FAQ, Framer pricing, Tommy's MCP on the Framer Marketplace, Unframer pricing, Composio Framer toolkit, Composio pricing, ericpjtsai/framer-mcp-server, Sheshiyer/framer-plugin-mcp, Zapier MCP, OpenAI Codex MCP, Ryze AI Framer guide. Checked November 14 and 15, 2026.

Codex, Framer and MCP: dates that matter

DateWhat happened
October 3, 2025Codex CLI 0.44.0 added support for Streamable HTTP MCP servers.
February 12, 2026Framer introduced the Server API, free during open beta.
June 9, 2026The first version of @framer/agent, the External Agents CLI, was published to npm.
July 9, 2026Codex became part of the ChatGPT desktop app with release 26.707, hence the app's name in OpenAI's steps.
August 4, 2026Framer Plugin API 4.1.0 added publishing and branching APIs.
October 7, 2026Codex CLI 0.161.0 added /mcp login <name> for signing in from a running session.
October 22, 2026Framer MCP appeared on Framer's updates page.
October 30, 2026Framer last updated its getting started and what you can do help articles for Framer MCP.
November 2, 2026Framer's updates page says Harness 2 for the Framer Agent brings the same capabilities to external agents through MCP.
November 4, 2026@framer/agent 0.0.48 was published, the newest version on November 15.
November 10, 2026Framer published a blog post with MCP setup for eight tools. Codex appears in it only in passing.
November 13, 2026Codex CLI 0.169.0, the newest release on the check date, keeps project configuration and MCP servers off for codex exec in untrusted folders.

Sources: Codex changelog, Codex CLI 0.44.0 release, Framer updates, Framer MCP update, Framer Server API update, Framer developer changelog, @framer/agent on npm, Framer blog on connecting AI tools. Checked November 14 and 15, 2026.

How this guide was tested

No call to Framer or to the Ryze AI connector was run for this guide, because no Framer project was connected to a Ryze AI workspace. The build read vendor pages and checked them against Ryze AI's integration facts. The table lists what was read.

What was runWhat came back
Framer help article on Framer MCP, read November 15 and again November 17Codex setup by Plugins directory or codex mcp add framer --url, server https://mcp.framer.com/mcp, article updated October 30, 2026
Framer Server API quick start, read November 15 and again November 17Keys are created under Site Settings, General; they authenticate as their creator and are bound to one project. No scopes and no revocation steps
Framer pricing, developer pages and npm registry, November 15Framer MCP free during preview; Server API free during open beta; no published Server API rate limit; @framer/agent 0.0.48
OpenAI Codex MCP, command reference, pricing and changelog pages, November 14The CLI, desktop app and IDE steps for a Streamable HTTP server with OAuth, the approval and tool list settings, and the plan wording
Ryze AI integration facts for FramerThree tools, API key sign-in, the connection steps and the one-connection-per-workspace rule

No step of this guide was run inside Codex. codex mcp add, codex mcp login, Add server and Authenticate in the app and the extension, a hand-written config.toml table, the bearer_token_env_var route and the approval settings were not tried; they follow OpenAI's pages as read on November 14, 2026 and the Ryze AI facts. No request went to mcp.framer.com or the Framer Server API, and no Ryze AI Framer tool was called, so tool names were not seen on a live connection and no Framer error message was captured. The other five ways were not tried either.

Errors and fixes

No call was run for this guide, so there are no copied error messages. The fixes below come from Framer's troubleshooting list for Framer MCP, from the Ryze AI facts and from OpenAI's Codex pages.

The Framer card rejects the project URL
The link must include the 20-character project id, or you can paste just the id. The address of the published site does not work. Copy the URL from the Framer editor address bar.
Publishing does nothing or fails
Publishing needs at least one CMS collection in the project that the API key can reach. Create a collection in Framer, then connect again and choose it under Choose a Collection.
A connection link is refused
A workspace holds one Framer connection, and a connection link is refused while one exists. Click View on the Framer card, disconnect with the trash icon and connect again.
The Framer tools do not run
The Ryze AI connector is free to add, but the Framer tools need any active Ryze AI plan or trial. Check the workspace plan.
ryze is missing from codex mcp list
Run codex mcp add ryze --url https://connector.get-ryze.ai/mcp again, or look in the other surfaces, which share one configuration. In the app and the extension, select Restart or Restart extension after saving.
The sign-in window never opens
Run codex mcp login ryze --no-browser, open the printed URL in any browser and paste the full redirect URL back into the terminal.
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 or trust the project.
A tool call times out
Codex waits 10 seconds for a server to start and 60 seconds for a tool call by default. Raise startup_timeout_sec or tool_timeout_sec in the [mcp_servers.ryze] table.
Framer MCP will not connect (Framer's own server)
Framer lists these checks: enter https://mcp.framer.com/mcp exactly, confirm the client supports remote Streamable HTTP servers and OAuth, ask a workspace administrator whether plugins or MCP connections need approval, retry the sign-in if you closed the window, and give the agent the full project link if it picks the wrong project.

Terms on this page

MCP
Model Context Protocol, an open standard for how applications pass context to language models. Codex calls the tools an MCP server exposes.
Streamable HTTP
The Codex transport for a server that lives at an address, such as the Ryze AI connector and Framer MCP. The other transport, STDIO, starts a local process.
config.toml
The Codex settings file at ~/.codex/config.toml. Each MCP server gets an [mcp_servers.<name>] table there, read by the CLI, the desktop app and the IDE extension.
API key (Framer Server API)
A key created in a project's Site Settings, General section. It authenticates as the user who created it and works for that one project.
CMS collection
A set of structured content items in a Framer project, such as blog posts. Each plan caps how many collections and items a project can have.
Slug
The text identifier of a CMS item. Every item has an id, a slug and its field data, and the Ryze AI write tool matches items by slug or id.
Publish and deploy
Publishing makes a new version of the site. In the Server API, publish() creates a preview link and deploy() promotes it to production.
Framer MCP
Framer's own remote MCP server at https://mcp.framer.com/mcp, signed in with OAuth, that works on pages, layouts and the CMS with the signed-in account's permissions.

Sources: Model Context Protocol, OpenAI Codex MCP, Framer Server API quick start, Framer Server API reference, Framer CMS developer docs, Framer help article on Framer MCP. Checked November 14 and 15, 2026.

Frequently asked questions

How do I connect Codex to Framer?

Create an API key in Framer under Site Settings, General, API Keys, then connect the project in Ryze AI with its Project URL and the key and choose a CMS collection. 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 Framer connector for Codex?

Yes, two hosted ones. The Ryze AI connector at https://connector.get-ryze.ai/mcp has three Framer tools for the CMS and publishing. Framer runs its own MCP server at https://mcp.framer.com/mcp and documents Codex setup for it, with a Plugins directory install or codex mcp add framer --url.

What is the Framer MCP server for Codex?

It is Framer's own remote MCP server, introduced on Framer's updates page on October 22, 2026. It uses Streamable HTTP and OAuth with your Framer account, and Framer says it works with pages, layouts, components, supported project settings and the CMS. Framer lists no tool names or count.

Should I use the Ryze AI connector or Framer's own MCP server?

Use the Ryze AI connector for CMS items and publishing, and Framer MCP when Codex should edit pages, layouts or components. Both are hosted and speak Streamable HTTP. They can sit in config.toml together as ryze and framer, and Framer MCP is free during Framer's preview.

Which Codex plan do I need for Framer?

OpenAI marks MCP for Plus and higher: its feature table shows MCP for Plus, Pro, Business, Enterprise / Education and API key sign-in and has no Free or Go column. Codex itself is included in Free, Go, Plus, Pro, Business, Edu and Enterprise, but Free and Go get the desktop app only, subject to rollout.

Can Codex edit or delete Framer CMS content?

Yes. Through Ryze AI, Codex can create items, update them in place by slug, and delete them by id, and a publish makes the changes live. Set default_tools_approval_mode to writes so Codex prompts first, or put framer__delete in disabled_tools to leave deletes out.

Can Codex edit Framer pages, layouts or custom code through Ryze AI?

No. The three Ryze AI Framer tools cover CMS collections and the site publish step only. For pages, layouts and components, Framer's own MCP server is the documented route.

Where do I find the Framer API key?

In the Framer project, open Site Settings with the settings icon at the top right, go to General and scroll to API Keys. Framer says a key authenticates as the user who created it and is bound to one project.

Does Codex publish my Framer site on its own?

Only when you ask. Publishing is a mode of framer__write, and nothing reaches visitors until a publish runs. Ask for it as its own step, and set the approval mode for framer__write to prompt if you want to confirm each one.

Does Framer need to stay open while Codex works?

Framer says its hosted MCP server does not need the editor open, and that its Server API runs without opening Framer. The Ryze AI connection uses a Server API key. The Tommy's MCP plugin is the exception, since it must stay open in the editor.

Can I connect more than one Framer project?

A Ryze AI workspace holds one Framer connection. To switch projects, click View on the Framer card, disconnect with the trash icon and connect the other project.

Does the connection work in Codex cloud tasks?

OpenAI's Codex Cloud page does not mention MCP, so this guide does not say it does. The steps cover the Codex CLI, the ChatGPT desktop app and the Codex IDE extension.

How much does connecting Codex to Framer cost?

Adding the Ryze AI connector is free, and the Framer 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. Framer MCP is free during preview and the Server API is free during open beta, and Codex usage follows your OpenAI plan.

Can I use the same Ryze AI connector in Claude or ChatGPT?

Yes. The URL https://connector.get-ryze.ai/mcp works in Claude as a custom connector and in ChatGPT as a custom MCP server where the plan allows it. Framer is connected once in Ryze AI and every client sees it.

Connect Framer to Codex

Adding the connector is free; the Framer tools need an active plan or trial. SEO Starter is $129 per month with a 3-day free trial; annual billing takes 30% off the first year.

Framer MCP server

Need help? Read the Ryze AI Framer guide or email Ryze AI support.