By Ira Bodnar, Ryze AI · Updated · Connector tested November 13, 2026
Quick answer
The main way to connect Codex to WordPress is the Ryze AI connector. Link the site to a Ryze AI workspace once, with an application password for a self-hosted site or a WordPress.com sign-in for WordPress.com and Jetpack sites. 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 a single setup serves all three.
- In WordPress admin create an application password under Users, Profile
- In Ryze AI open Integrations, click Connect on WordPress and enter the site URL, username and password
- 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 WordPress 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 WordPress site | Once, in Ryze AI: an application password (self-hosted) or a WordPress.com sign-in (WordPress.com and Jetpack) |
| WordPress tools | 9 tools: 2 read, 6 write and 1 delete. Four of the write tools need a self-hosted site and an administrator |
| Can Codex change the site | Yes, posts, pages, media, categories, tags and custom post types. Your approval and permission modes decide whether it asks first |
| Several sites | Add more sites in Ryze AI with Add one more account. Codex works on the primary site unless you name another, and every WordPress tool takes an optional connection_id |
| 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 WordPress tools need an active plan or trial |
| WordPress's own options for Codex | The WordPress.com MCP server, documented for Codex as codex mcp add wpcom-mcp. The MCP Adapter plugin page names no assistant and accepts any MCP-compatible client |
| Last tested | Connector probed November 13, 2026; nine WordPress reads from Claude Code on November 14, 2026. 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. The MCP row of the same page's 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 on those two plans. 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. OpenAI's MCP page names no extra plan for MCP servers.
- A WordPress login. On a self-hosted site, a WordPress user who can generate an application password; the site must be served over HTTPS, because WordPress turns application passwords off on plain HTTP by default. On WordPress.com or Jetpack, a WordPress.com account that can reach the site. Plugin installs, the Yoast and Rank Math bridges and head code need an administrator user.
- 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 WordPress tools need any active Ryze AI plan or trial.
How to connect Codex to WordPress with the CLI
Two steps happen in WordPress and Ryze AI, three in Codex. The server URL is the same for every user.
Create an application password in WordPress
Self-hosted sites: in WordPress admin open Users, Profile, scroll to Application Passwords, type a name such as Ryze AI and click Add New Application Password. Copy the password at once, because it is shown only once. Skip this step on a WordPress.com or Jetpack site.
Connect WordPress in Ryze AI
Create a Ryze AI account or sign in, open Integrations and click Connect on the WordPress card. On the Self-hosted site tab, enter the Site URL (https://), the username you use to sign in to wp-admin and the application password, then click Continue. On the WordPress.com / Jetpack tab, sign in on WordPress.com, approve access and choose the site. For Jetpack sites the Jetpack JSON API module must be enabled. Optionally click View on the card to choose the Author and Category new posts use.
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. Without a local browser, add --no-browser, open the printed URL and paste the full redirect URL back into the terminal. From 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 my 10 most recent WordPress posts with title, status and publish date.
codex mcp add ryze --url https://connector.get-ryze.ai/mcpcodex mcp login ryzeThe CLI is the shortest route. The first command registers the server and the second starts the OAuth sign-in. Run codex mcp list afterwards, or /mcp inside the codex TUI, to confirm the server is registered.
The Ryze AI help article for WordPress covers the WordPress side of the connection, and the Ryze AI agent API help page covers API keys.
Sources: OpenAI Codex MCP, Codex command reference, Ryze AI WordPress 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 others. The app and the extension use a form instead of commands.
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.
- In the server list, which flags the servers that still need OAuth, choose Authenticate for ryze and finish the Ryze AI sign-in. Typing /mcp in the composer lists the connected servers.
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 in a trusted project. OAuth is the default for an HTTP server; run codex mcp login ryze to sign in.
[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 = 120For 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. Do not paste the key into the file. When you register the server from the shell, the --bearer-token-env-var option of codex mcp add writes the same setting.
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 either; the test record further down lists what was run.
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 WordPress 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, Streamable HTTP for a server at an address. The MCP page lists no other |
| Remote sign-in | OAuth by default, with Client ID Metadata Documents or dynamic client registration; also bearer tokens, static or environment headers, a header helper and ChatGPT session sign-in for trusted first-party servers |
| Scopes requested | From config or --scopes; otherwise from the server's first WWW-Authenticate challenge, then its protected resource metadata |
| Approval rules | Per-server and per-tool approval modes, plus two rules: a tool with a destructive annotation needs approval unless it also has a read annotation, and Approve for me hands requests to a reviewer agent. Details under Approvals in Codex below |
| 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, written under Admin Console > Agent Security, runs a server only when name and URL or command match. An empty list turns all servers off |
| 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, Permission modes, Codex plugins, Managed configuration, Codex on mobile, Codex Cloud. 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 WordPress.
Claude and ChatGPT
In Claude, add https://connector.get-ryze.ai/mcp as a custom connector under Customize, Connectors. In ChatGPT, add it as a custom MCP server where your plan allows it. If the connector was added before WordPress was connected, remove and re-add it so the tool list refreshes.
Cursor
Add the server to .cursor/mcp.json with the same URL.
{ "mcpServers": { "ryze": { "url": "https://connector.get-ryze.ai/mcp" } } }WordPress permissions: credentials and roles
WordPress never talks to Codex directly. Ryze AI holds the WordPress credential, and Codex signs in to Ryze AI with OAuth; the connector's discovery files list two scopes for that sign-in, mcp:read and mcp:write. Three things decide what Codex can change.
- The WordPress user behind the credential
- Posts and pages follow the capabilities of the WordPress user whose application password you entered. A user who cannot delete posts in wp-admin cannot delete them through the connector either. Plugin installs, the SEO bridges and head code need an administrator.
- Application passwords
- WordPress introduced application passwords in version 5.6. They are available by default on sites served over HTTPS, and WordPress filters can switch them off for the whole site or restrict them to some users. A password can be revoked at any time on the user's profile screen.
- Self-hosted or WordPress.com
- Self-hosted connections also reach plugin routes such as /yoast/v1. WordPress.com connections reach only the core /wp/v2 routes, and plugin installs, the Yoast and Rank Math bridges and head code do not work there.
Credentials and roles behind each call
An application password carries no app scopes. It acts as the WordPress user it belongs to, so on a self-hosted connection that user's role is the ceiling for every call Codex makes. A WordPress.com or Jetpack connection signs in on WordPress.com instead. WordPress.com's OAuth2 sign-in does use scopes, single-blog access by default, and this guide does not name the one the Ryze AI sign-in requests. Below are the two credentials and the five standard roles as WordPress describes them.
| Credential or role | What WordPress says | What Codex can do with it |
|---|---|---|
| Application password (self-hosted) | Part of WordPress since 5.6. Made and revoked on the user's profile screen, 24 letters and digits, sent with the username over Basic Auth on HTTPS requests. It cannot log in at wp-login.php, and narrower passwords are listed only as future work | Whatever the user behind it may do, plugin routes such as /yoast/v1 included |
| WordPress.com sign-in (WordPress.com and Jetpack) | WordPress.com's OAuth2 endpoints serve its own sites and Jetpack-connected sites alike. Its /wp/v2 namespace mirrors the core REST API, and the Jetpack JSON API forwards signed-in requests to the live site | Core /wp/v2 routes only. Plugin installs, the two bridges and head code are off |
| Administrator | Every administration feature of a single site, activate_plugins included. On a single-site install also install_plugins, update_plugins, delete_plugins, edit_users and unfiltered_html; on Multisite only the Super Admin holds those | All nine tools on a self-hosted site. Plugin installs, the bridges and head code need this role |
| Editor | Publishes and manages posts, other users' posts included | Content tools across every author's posts. No plugin, bridge or head-code tools |
| Author | Publishes and manages their own posts | Content tools on the user's own posts |
| Contributor | Writes and manages their own posts but cannot publish them | Own posts, left unpublished; publishing needs a higher role |
| Subscriber | Manages only their own profile and holds just the read capability | No content changes |
Some things stay out of reach whatever the role. Codex cannot install a plugin from an uploaded zip file or a URL, because the install tool takes wordpress.org directory plugins only. It cannot change robots.txt. It reaches Elementor text only where the post type exposes meta._elementor_data. Yoast and Rank Math fields sent without the one-time bridge are dropped by WordPress without an error. A WordPress.com connection adds four more gaps: plugin routes such as /yoast/v1, plugin installs, both SEO bridges and head code.
Sources: WordPress roles and capabilities, REST API authentication, Application passwords guide, WordPress.com OAuth2, WordPress.com API namespaces, Jetpack JSON API, Ryze AI WordPress guide. Checked November 14, 2026.
Removing access
To remove access, revoke the application password in WordPress under Users, Profile, Application Passwords. In Ryze AI, click View on the WordPress card to manage or remove the connected site. In Codex, codex mcp logout ryze clears the stored OAuth credentials and codex mcp remove ryze deletes the entry; to pause the server and keep it, set enabled = false in its [mcp_servers.ryze] table.
What Codex can do in WordPress
The Ryze AI connector exposes nine WordPress tools. Codex calls them by these names through the ryze server. The plugin install, bridge and head-code tools need an administrator user on a self-hosted site.
| Tool | Type | What it does |
|---|---|---|
| wordpress__read | Read | Runs a read-only (GET) REST API request on the connected site, covering posts, pages, media, categories, tags, users, plugins and custom post types. |
| wordpress__search_content | Read | Searches a text field such as a post's raw content and returns the matching lines with line numbers and context. |
| wordpress__write | Write | Runs a REST API request that creates or updates resources (POST, PUT or PATCH), such as creating a post or updating a page. |
| wordpress__edit_content | Write | Makes find-and-replace edits to a text field such as post or page content, an excerpt or a title, without resending the whole content. |
| wordpress__delete | Delete | Runs a DELETE REST API request, for example to delete a post. |
| wordpress__installPlugin | Write | Installs and activates a plugin from the wordpress.org directory on a connected self-hosted site. |
| wordpress__enableYoastRestBridge | Write | One-time setup on a self-hosted Yoast SEO site that makes the Yoast title, meta description, focus keyword, canonical and noindex fields writable through the REST API. |
| wordpress__enableRankMathRestBridge | Write | One-time setup on a self-hosted Rank Math site that makes the Rank Math title, description, canonical URL and focus keyword fields writable through the REST API. |
| wordpress__addHeadCode | Write | Adds a block of HTML inside the head of every page on a self-hosted site, such as tracking snippets, pixels and verification tags. |
Only wordpress.org directory plugins can be installed, not uploaded zip files or URLs, and plugin installs can crash a site. Yoast and Rank Math fields written through the plain REST API without the bridge are silently dropped by WordPress. The agent cannot change robots.txt, and Elementor text is reachable only where the post type exposes meta._elementor_data.
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 with Approve for me as the permission mode, a reviewer agent answers those requests instead of you. Which annotations the nine WordPress tools carry was not checked, so the deny list is the sure way to keep a tool out. For WordPress, a deny list on wordpress__delete and the plugin, bridge and head-code tools keeps Codex to reading and editing content. The Yoast bridge, Rank Math bridge and head-code tools default to not installing the Code Snippets plugin, and their descriptions require your explicit yes in chat first. The Ryze AI chat itself 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 = [
"wordpress__delete",
"wordpress__installPlugin",
"wordpress__enableYoastRestBridge",
"wordpress__enableRankMathRestBridge",
"wordpress__addHeadCode",
]Limits in numbers
WordPress, WordPress.com, Yoast and Codex each set limits on what Codex can ask for. The figures come from their pages as read on November 14, 2026, and one row from the test of that day.
| Limit | Number or rule |
|---|---|
| Items per REST request | 1 to 100 through per_page; the posts route returns 10 by default. 101 was refused in the test |
| Record and page counts | Paged answers carry X-WP-Total and X-WP-TotalPages headers |
| Trimming an answer | _fields keeps only the fields you name, nested ones from WordPress 5.3 |
| Application password format | 24 characters, letters and digits only; Last Used is accurate to within 24 hours |
| Trash | 30 days by default (EMPTY_TRASH_DAYS). On WordPress.com, posts and pages stay recoverable 30 days; deleted media, categories and tags do not |
| Yoast's own REST API | Read-only, with no POST or PUT calls; it adds yoast_head and yoast_head_json to core answers |
| Free WordPress.com MCP access | Through November 30, 2026 for free sites and for Jetpack sites without Jetpack AI or Complete |
| Request quota seen in the test | No answer in the November 14, 2026 test carried a rate limit or quota figure, so this page gives no number |
| Codex waiting times | Server start 10 seconds and each tool call 60 seconds by default; startup_timeout_sec and tool_timeout_sec raise them |
| Codex output budget | tools.<tool>.output_token_limit, counted before a 20% serialization allowance |
Sources: REST API pagination, Posts endpoint reference, Global parameters, Application passwords guide, wp-config.php settings, WordPress.com MCP help, WordPress.com MCP for developers, Yoast REST API, OpenAI Codex MCP. Checked November 14, 2026.
What the connector answered, tested
Codex did not send these calls. On November 14, 2026 Claude Code ran wordpress__read nine times through the Ryze AI connector, for a site linked with a WordPress.com sign-in, so the requests went out through WordPress.com's public API. Codex points at the same address and tool. The page size and sort checks were narrowed to a missing ID and the id field, so no answer held a post. The exact messages are in the errors table below.
| Request | Answer | What it means when you ask Codex |
|---|---|---|
| /wp/v2/types | 18 post types, post, page, attachment and wp_block among them | Ask for this list first when you work with custom content |
| /wp/v2/taxonomies | 6 taxonomies, category and post_tag among them | The term lists a post can be filed under |
| /wp/v2/posts/999999999, a made-up ID | not_found | A wrong ID fails cleanly |
| /wp/v2/no-such-route | not_found | A mistyped path is turned away |
| /wp/v2/types/not_a_type | not_found | Type slugs must come from /wp/v2/types |
| /wp/v2/posts with per_page 101 | HTTP 400, rest_invalid_param | Over 100 items takes more than one request |
| /wp/v2/posts sorted by no_such_field | HTTP 400, rest_invalid_param | Name a sort field the collection supports |
| /wp/v2/types sent with a request body | invalid_arguments, before WordPress was contacted | Filters belong in the query field |
| /yoast/v1 over the WordPress.com connection | not_found | Plugin namespaces need a self-hosted link |
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 uses the primary site unless you name another one.
1. Review recent posts and drafts
List my 10 most recent WordPress posts with title, status, publish date and category, then show which of them are still drafts.
Tools used: wordpress__read on posts
What comes back: A table of posts from your site with the fields you asked for, and a separate list of drafts.
2. Fix a phrase in one post
Search the post about pricing for the old plan name, show me the matching lines, then replace it with the new name in that post only.
Tools used: wordpress__search_content, wordpress__edit_content
What comes back: The matching lines with line numbers and context, then a confirmation of the targeted edit, written back without resending the whole post.
3. Create a draft page
Create a draft WordPress page called Contact with a short intro paragraph and our support email address. Do not publish it.
Tools used: wordpress__write
What comes back: A new page created through the REST API with the status you asked for, which you can open in wp-admin to review.
On a self-hosted site with Yoast SEO or Rank Math, you can also ask Codex to enable the one-time bridge and then update SEO titles and meta descriptions. Codex needs your yes in chat before it installs the Code Snippets plugin.
10 jobs to hand to Codex
Ten jobs you can give Codex once the ryze server is signed in, each with the WordPress tool it calls. Default connection here means a site linked either way, with an application password or a WordPress.com sign-in, through a WordPress user whose role covers the content. Only the post type lookup in the last row rests on a call made for this guide, and that call came from Claude Code.
| Job | What to ask Codex | Tool | On the default connection |
|---|---|---|---|
| Recent posts table | Show my 25 newest posts as a table with title, status, publish date and category. | wordpress__read | Yes. One request returns at most 100 |
| Locate a phrase | In the post with slug my-post-slug, show every line that contains the old brand name, with line numbers. | wordpress__search_content | Yes |
| Swap a phrase in place | Replace that old brand name with the new one in the same post and leave everything else alone. | wordpress__edit_content | Yes, if the user's role may edit the post |
| Draft from the repository | Turn the markdown file I name in this repository into a draft post with my title, and report the new post ID. | wordpress__write | Yes |
| Retitle and refile | Change the title and excerpt of the post with slug my-post-slug, move it to the category I name and add two tags. | wordpress__write | Yes. Categories and tags can be created or renamed as well |
| Image alt text | Write alt text and a caption for the media item with the ID I give you. | wordpress__write | Yes |
| Delete a draft | Delete the draft post with slug old-draft-slug. | wordpress__delete | Yes, if the user's role may delete it. Keep this tool behind an approval |
| Yoast or Rank Math fields | Enable the Rank Math bridge, then set the SEO title and description of the page with slug pricing. | wordpress__enableRankMathRestBridge or wordpress__enableYoastRestBridge, then wordpress__write | No. Self-hosted only, with an administrator's application password and your yes to the Code Snippets install |
| Verification tag | Put this verification meta tag in the head of every page. | wordpress__addHeadCode | No. Self-hosted and administrator only, under the same consent rule |
| Custom post types | List the post types on my site, then show the ten newest items of the one I pick. | wordpress__read | Yes. The /wp/v2/types read was tested on November 14, 2026 |
5 ways to connect Codex to WordPress
Five ways can put a WordPress 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, the WordPress credential stays in Ryze AI, and one hosted address serves self-hosted, WordPress.com and Jetpack sites. The other four were read on their vendors' pages on November 14, 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. WordPress is linked in Ryze AI with an application password or a WordPress.com sign-in | Posts, pages, media, categories, tags and custom post types to read, create, update and delete, plus text search and in-place edits. Plugin installs, the SEO bridges and head code on a self-hosted site with an administrator | SEO Starter, $129 per month with a 3-day free trial; any active Ryze AI plan or trial runs the tools |
| WordPress.com MCP server, Jetpack sites included | Hosted by WordPress.com | codex mcp add wpcom-mcp --url https://public-api.wordpress.com/wpcom/v2/mcp/v1, with codex mcp login wpcom-mcp to sign in by hand. OAuth 2.1 with PKCE and dynamic client registration; you pick Full access or Read only. Codex is named on WordPress.com's developer, help and landing pages and on Jetpack's | All sites on the WordPress.com account and Jetpack-linked sites: content, comments, media, templates, menus, settings, stats, users, plugins and domains, through 8 grouped and 9 standalone tools. New posts start as drafts; WooCommerce prices, stock and orders are not covered | Included on paid WordPress.com plans and with Jetpack AI or Complete. Free sites, and Jetpack sites without those plans, until November 30, 2026 |
| MCP Adapter plugin, from WordPress | On your site; needs WordPress 6.9 and PHP 7.4 | Install from Plugins, Add New. Add the site address followed by /wp-json/mcp/mcp-adapter-default-server as a Streamable HTTP server and authenticate as a WordPress user, which Automattic's proxy README shows as an Authorization: Basic header; Codex sends headers through env_http_headers. STDIO through WP-CLI is the other documented route. The plugin page names no assistant and says any MCP-compatible client can use the endpoint; its CLI guide names Claude Desktop, Claude Code, VS Code and Cursor | Only Abilities API abilities that core or a plugin marks public, through 3 meta-tools on the default server | Free, GPL-2.0-or-later |
| WordPress Studio MCP server | On your computer, in the Studio desktop app | codex plugin marketplace add Automattic/studio-plugins, then codex plugin add wp-studio@studio and a new session. By hand: codex mcp add wordpress-studio -- studio mcp | Local Studio sites, plus the account's WordPress.com sites by the docs. No route to a live self-hosted site is described | No price on the docs page |
| Zapier MCP | Hosted by Zapier | Generate an MCP address in Zapier, choose WordPress actions and add the address to Codex. Zapier lists Codex as a client; its Codex page was not opened | Actions such as Create Post, Update Post, Upload Media, Find Post and API Request | Every Zapier account; 2 tasks per successful call |
Options that do not fit Codex
- WordPress.com's one-click installs. The Claude directory connector, the WordPress plugin for ChatGPT and the Cursor Marketplace plugin each name only their own assistant. OpenAI says ChatGPT and Codex share one plugin directory, but whether the WordPress plugin shows in Codex was not checked; the wpcom-mcp command reaches the same server.
- Composio. Its WordPress.com toolkit lists Claude, ChatGPT and Cursor and needs your own OAuth app registered with WordPress.com. No page for self-hosted WordPress was found.
- AI Engine by Meow Apps. A site plugin whose MCP server has more than 140 tools. Its pages name ChatGPT, Claude, Claude Code and OpenClaw.
- Automattic's mcp-wordpress-remote proxy. A stdio bridge naming Claude Desktop and Claude Code. Its README sends clients that speak streamable HTTP, as Codex does, straight to the site.
- InstaWP/mcp-wp and docdyhr/mcp-wordpress. Open-source servers set up for Claude Desktop; docdyhr also links VS Code and Cline guides.
- WordPress Playground MCP. It names Codex (codex mcp add wordpress-playground -- npx -y @wp-playground/mcp) but works on a Playground instance in a browser tab, not a live site.
- WordPress Agent Skills. Development know-how for Codex and other coding assistants, with no access to a site.
- Automattic/wordpress-mcp and the WordPress 7.0 AI Client. The first is archived and being retired for the MCP Adapter; the second lets site plugins call AI providers, the opposite direction.
Which one to pick
Ryze AI is the best way to connect Codex to WordPress for editing posts, pages and Yoast or Rank Math fields on a self-hosted site, with a caveat: it needs an active Ryze AI plan or trial, its plugin, bridge and head-code tools need an administrator's application password, and robots.txt stays out of reach. A site on WordPress.com or linked through Jetpack can add the WordPress.com server too: it is documented for Codex, included on paid plans, has a Read only level and covers domain and account tools the Ryze AI tools lack. The MCP Adapter suits developers who define their own abilities, Studio suits local development sites, and Zapier suits teams already running their other apps there. Each server gets its own config.toml table, so ryze and wpcom-mcp can sit side by side. The WordPress MCP page has the full Ryze AI tool reference.
Sources: WordPress.com MCP for developers, WordPress.com MCP help, WordPress.com MCP tools reference, WordPress.com AI and MCP page, Jetpack and MCP, MCP Adapter in the plugin directory, WordPress/mcp-adapter, Automattic/mcp-wordpress-remote, Studio and MCP, Zapier for WordPress, Zapier MCP quickstart, WordPress.com in Claude's directory, WordPress.com for ChatGPT, WordPress on the Cursor Marketplace, Composio WordPress.com toolkit, AI Engine plugin, InstaWP/mcp-wp, docdyhr/mcp-wordpress, Playground MCP announcement, WordPress agent skills, WordPress 7.0 release post, OpenAI Codex MCP, OpenAI Codex plugins, OpenAI Codex pricing, Ryze AI WordPress guide. Checked November 14, 2026.
Codex, WordPress and MCP: dates that matter
| Date | What happened |
|---|---|
| November 5, 2020 | WordPress published the application passwords integration guide for version 5.6, the release that brought them into core. |
| October 7, 2025 | WordPress.com announced MCP support, read-only at first. |
| 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. |
| December 2, 2025 | WordPress 6.9 shipped with the Abilities API, the version the MCP Adapter now requires. |
| January 22, 2026 | WordPress.com added OAuth 2.1 sign-in for MCP clients. |
| March 20, 2026 | The WordPress.com server gained 19 writing abilities for posts, pages, comments, categories, tags and media. |
| July 9, 2026 | Codex moved into the ChatGPT desktop app with release 26.707, hence the app's name in OpenAI's steps. |
| October 2, 2026 | MCP Adapter 0.7.0 came out and the plugin joined the wordpress.org directory; 0.7.1 followed on GitHub on October 16. |
| October 7, 2026 | Codex CLI 0.161.0 added /mcp login <name> for signing in from a running session. |
| November 13, 2026 | Codex CLI 0.169.0, newest on the check date, keeps project configuration and MCP servers off for codex exec in untrusted folders. WordPress.com updated its MCP developer page. |
| November 30, 2026 | Last day of MCP access for free WordPress.com sites and for Jetpack sites without Jetpack AI or Complete. |
Sources: Application passwords guide, WordPress.com, October 7, 2025, Codex CLI 0.46.0 release, WordPress 6.9, WordPress.com, January 22, 2026, WordPress.com, March 20, 2026, Codex changelog, MCP Adapter in the plugin directory, MCP Adapter releases, WordPress.com MCP for developers. Checked November 14, 2026.
How this guide was tested
Two sets of checks stand behind this guide. On November 13, 2026 the Ryze AI connector was probed without a sign-in. On November 14, 2026 nine read-only wordpress__read calls went through it from Claude Code, for a site linked with a WordPress.com sign-in. The table lists what ran and what came back.
| What was run | What came back |
|---|---|
| Signed-out request to https://connector.get-ryze.ai/mcp, November 13 | HTTP 401 with a WWW-Authenticate header that points to the sign-in details |
| The connector's two discovery files, November 13 | Both loaded. They name the authorize, token and register endpoints, the authorization code and refresh token grants, PKCE with S256, and the scopes mcp:read and mcp:write |
| WordPress tool definitions, November 14 | All 9 wordpress__ tools returned a definition from the live connector, each with an optional connection_id for choosing a site |
| Schema reads, November 14 | /wp/v2/types answered with 18 post types and /wp/v2/taxonomies with 6 taxonomies |
| Six requests built to fail, November 14 | A missing ID, an unknown path, an unknown type, 101 per page, an unknown sort field and a read with a body. WordPress refused five, and the connector stopped the sixth before WordPress saw it |
| /yoast/v1 over the WordPress.com connection, November 14 | not_found, in line with the Ryze AI facts: WordPress.com connections reach only the core /wp/v2 routes |
| Paging and quota fields, November 14 | Answers carried total and totalPages fields, 0 on the two schema routes, which are not paged lists. No rate limit or quota figure appeared |
No step of this guide was run inside Codex. codex mcp add, codex mcp login, Add server and Authenticate in the app and the IDE extension, a hand-written config.toml table, the bearer_token_env_var route and the approval settings were not tried; those steps follow OpenAI's pages as read on November 14, 2026 and the Ryze AI facts. The WordPress calls went from Claude Code through the same connector and tools. On paper the Codex sign-in fits: OpenAI says Codex takes its scopes from the server's first WWW-Authenticate challenge and registers itself when a register endpoint is offered, and the connector sent such a challenge and lists that endpoint. That comes from reading both documents; no sign-in was run from Codex. No self-hosted site was connected, so no application password was used and no 401 or 403 from WordPress was seen. No call returned posts, pages, media, users or plugins, and wordpress__search_content was not called. The write, edit, delete, plugin, bridge and head-code tools were not run, because they change the site. The other four ways were not tried.
Errors and fixes
Exact messages from the test
WordPress and the connector returned these answers to Claude Code in the test on November 14, 2026. The first five are copied exactly; the sixth is paraphrased. If Codex passes one of them on, the row gives the cause and what to ask next.
| Message | Why it happened | What to do in Codex |
|---|---|---|
| Invalid post ID. | No post on the connected site has that ID. The connector passed it on with the status not_found. | Ask Codex to list posts first and reuse an ID from that list. |
| No route was found matching the URL and request method. | The path is not served on this site or connection. On a WordPress.com connection a plugin namespace such as /yoast/v1 gets the same answer. | Check the path against /wp/v2/types. Plugin routes need the site linked as self-hosted. |
| Invalid post type. | That post type slug is not registered on the site. | Have Codex read /wp/v2/types and choose a slug from it. |
| Invalid parameter(s): per_page | HTTP 400, code rest_invalid_param. The request asked for 101 items per page, and WordPress accepts 1 to 100. | Ask for 100 or fewer and let Codex fetch the next page. |
| Invalid parameter(s): orderby | HTTP 400, code rest_invalid_param. The sort field does not exist. For posts, WordPress's pagination handbook lists date, relevance, id, include, title and slug. | Name one of those fields in the prompt. |
| invalid_arguments, saying a GET request cannot carry a body | The read went out with a body, and the read tool rejected it before WordPress was contacted. | Ask Codex to put the filters in the query field. |
Other problems
- codex mcp login opens no browser
- Run codex mcp login ryze --no-browser, open the printed URL on another device and paste the full redirect URL back into the terminal.
- The server times out on start or on a call
- Codex waits 10 seconds to start a server and 60 seconds per tool call by default. Raise startup_timeout_sec or tool_timeout_sec in the [mcp_servers.ryze] table.
- Credentials rejected in Ryze AI
- Check the username (the one you use for wp-admin), the Site URL with https://, and that you copied the application password exactly. Generate a new one if it was lost, because WordPress shows it only once.
- No Application Passwords section in the profile
- WordPress makes the section available by default on sites served over HTTPS, and filters can turn it off for the whole site or limit it to some users. Ask the site administrator to enable it.
- The connection fails with a firewall or security error
- A security plugin, WAF or host that blocks /wp-json requests stops the connection. Allowlist the requests and reconnect.
- A Jetpack site will not connect
- The Jetpack JSON API module has to be switched on for a Jetpack site. Turn it on, then sign in with WordPress.com again.
- Plugin, bridge or head code tools refuse
- These tools need a self-hosted connection and an administrator user. They do not work on WordPress.com connections; edit those settings in wp-admin.
- Yoast or Rank Math fields do not change
- WordPress silently drops those fields when they are written through the plain REST API. Enable the Yoast or Rank Math bridge first, on a self-hosted site.
- WordPress tools do not appear in Codex
- If WordPress was connected in Ryze AI after the server was added, remove the ryze server, add it again, sign in and start a new session.
- Output is cut off
- Set tools.<tool>.output_token_limit for that tool in config.toml to give it a larger output budget.
- A tool replies that a subscription is required
- The WordPress tools need an active Ryze AI plan or free trial. Start the trial, then retry.
- No CLI or IDE extension on a Free or Go plan
- OpenAI lists Codex on those plans in the desktop app only, subject to rollout, and does not say whether MCP servers work there. The CLI and the IDE extension come with Plus and higher, and the feature table marks MCP for Plus, Pro, Business and Enterprise / Education.
Terms on this page
- MCP
- Model Context Protocol, an open standard for how applications pass context to language models. Codex calls the tools that an MCP server exposes.
- Streamable HTTP
- The Codex transport for a server that lives at an address, such as the Ryze AI connector. 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.
- Application password
- A 24-character password that WordPress creates on a user's profile for programs calling the REST API. Each one can be revoked separately, and none can sign in at wp-login.php.
- REST API (wp-json)
- The HTTP interface built into WordPress under /wp-json. Core content lives in the /wp/v2 routes, and the Ryze AI read, write and delete tools take paths relative to /wp-json.
- Role
- A named bundle of capabilities such as activate_plugins. Administrator, Editor, Author, Contributor and Subscriber are the standard five, and a connection can do only what its user's role allows.
- Abilities API
- Part of WordPress 6.9 and newer. Core, plugins and themes register what they can do there, and the MCP Adapter turns the public abilities into MCP tools.
Sources: WordPress.com MCP for developers, OpenAI Codex MCP, Application passwords guide, Posts endpoint reference, WordPress roles and capabilities, Abilities API introduction. Checked November 14, 2026.
Frequently asked questions
How do I connect Codex to WordPress?
Connect your site in a Ryze AI workspace with an application password or WordPress.com sign-in. 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 WordPress connector for Codex?
Yes, more than one. The Ryze AI connector at https://connector.get-ryze.ai/mcp reaches self-hosted, WordPress.com and Jetpack sites. WordPress.com documents Codex as a client of its own MCP server at https://public-api.wordpress.com/wpcom/v2/mcp/v1. WordPress Studio and Zapier MCP also name Codex, and the MCP Adapter plugin page says any MCP-compatible client can use its endpoint.
Which WordPress MCP server should I use with Codex?
Ryze AI is the best way to connect Codex to a self-hosted WordPress site for editing content and SEO fields, though a site on WordPress.com can use the WordPress.com server directly and it offers a Read only access level. The official MCP Adapter plugin suits developers who register their own abilities.
Does WordPress have its own MCP server?
Yes. WordPress.com runs an MCP server with OAuth 2.1 and PKCE, which self-hosted sites linked through Jetpack use as well. WordPress publishes the MCP Adapter plugin, which exposes a site's registered abilities as MCP tools over HTTP or STDIO and has been in the wordpress.org plugin directory since October 2, 2026.
Which Codex plan do I need?
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 ChatGPT Free, Go, Plus, Pro, Business, Edu and Enterprise, but on Free and Go it runs in the desktop app only, subject to rollout, and the CLI and the IDE extension start at Plus. OpenAI's MCP page adds no plan requirement of its own.
Can Codex edit or delete WordPress content?
Yes. Through Ryze AI, Codex can create, update and delete posts, pages, media, categories, tags and custom post types, and make targeted text edits. Set default_tools_approval_mode to writes in config.toml so Codex prompts before tools that are not marked read-only, or put wordpress__delete in disabled_tools to leave deletes out. With Approve for me chosen, a reviewer agent answers those prompts instead of you.
Can Codex change Yoast SEO or Rank Math fields?
On self-hosted sites, yes, after a one-time bridge for Yoast or Rank Math that needs your explicit yes in chat. On WordPress.com connections the bridges do not work, so those fields are edited in wp-admin.
Do I need a WordPress.com site or will self-hosted work?
Both work in Ryze AI. A self-hosted site connects with its URL, an admin username and an application password. A WordPress.com or Jetpack site connects with WordPress.com sign-in, and for Jetpack the JSON API module must be enabled.
Can I connect more than one WordPress site?
Yes. Click View on the WordPress card in Ryze AI and choose Add one more account. Codex works on the primary site until you name a different one in the prompt. How multiple sites interact with the one-website rule of an SEO plan is not documented, so check with Ryze AI support before relying on it.
Does this work in Codex cloud tasks?
This page does not claim it does. The connector was not tested in Codex cloud, OpenAI's page about Codex Cloud is silent on MCP, and the MCP page cautions, in its part on Work Cloud, that local servers and transports might be missing there.
Do I need to configure the CLI, the app and the IDE extension separately?
No. The ChatGPT desktop app, the Codex CLI and the IDE extension share one MCP configuration. Restart the app or the extension after you add the server.
Are there AI SEO tools that integrate directly with WordPress?
Yes. Ryze AI links straight to a WordPress site, with an application password on a self-hosted site or a WordPress.com sign-in, and its SEO plans publish Content Plan articles there and apply Technical Audit fixes with the agent. Through the connector, Codex works with the same nine WordPress tools, the Yoast and Rank Math bridges on a self-hosted site included.
How do I do programmatic SEO in WordPress?
One route is a planned run of articles published for you: the Content Plan in Ryze AI's SEO Starter plan publishes up to 90 articles per billing cycle, at most 3 a weekday, to the connected WordPress site as posts, automatically by default, or held for you when Publishing mode is set to Manual. From Codex you can add your own, for example by asking it to turn each file in a folder into a draft post with wordpress__write. An SEO plan covers one website.
Which alt text tools work with WordPress without a manual export?
Codex can change alt text in place through the Ryze AI connector: wordpress__write updates the alt text and caption of items in the WordPress media library, with no export or import step. Ask it to read the media items first, then send the new text for each one.
How much does it cost to connect Codex to WordPress?
Connecting the connector is free, but the WordPress 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 itself is billed under your OpenAI plan or API pricing.