Connect Codex to WordPress and give it the half of the site that isn't code

Updated October 31, 2026

A WordPress site is mostly not a codebase, which is why Codex alone only ever sees a sliver of it.

Codex is good at reading a repo and making careful changes. But the pages, menus, options, products and plugin settings on a WordPress site live in a database that never shows up in your repo. A template that calls get_option( 'menu_layout' ) tells Codex nothing until it can see what that option actually holds on the live site. Connect the site over MCP and Codex can read and change that part too.

Kitepod is the remote MCP server that makes that connection. It's free, it signs in with OAuth, and it treats database work with the suspicion it deserves.

Three jobs across a restaurant group's sites

For example, say a small restaurant group has three WordPress sites, and the flagship's menu page is a mess of copy-pasted tables.

Codex reads the page and the theme over MCP. The new synced pattern is a design change, so it's staged with a preview link and goes live when you publish it. The page rebuild itself is a content edit: it runs directly, with a snapshot taken first so you can undo it.

This goes through WP-CLI's search-replace, which handles PHP serialized data, so URLs stored inside serialized settings don't get mangled. A search-replace always waits for a person's approval, whatever the site's policy says.

Every connected site is reachable from the same session, so this is one request. It's read-only, so nothing on any of the three sites changes yet. When you do update, plugin updates wait for approval under the default policy, and each gets a checkpoint so any single one can be rolled back.

Setup

1. Put the Kitepod plugin on each site (Plugins → Add New → Upload). Minimum versions: WordPress 6.4, PHP 7.4.
2. Click Connect in wp-admin and choose the WordPress user Codex will act as. Codex can't do anything that user can't.
3. Add the server to Codex, then log in.

Adding Kitepod to Codex

The quickest way is the setup prompt in your Kitepod dashboard. Paste it into Codex and it adds the remote streamable HTTP server as "kitepod" for you.

To do it by hand, add this to ~/.codex/config.toml:

[mcp_servers.kitepod]
url = "https://kitepod.com/mcp"

OpenAI's Codex docs list url as the only required key, and OAuth as the default auth. Then run:

codex mcp login kitepod

That opens a browser window. Sign in and approve the connection.

The CLI, the IDE extension and the ChatGPT desktop app share that one config, according to OpenAI's docs. You can also add the server from the UI: Settings → MCP servers in the desktop app, or the gear menu → MCP servers in the IDE extension. Pick Add server, choose Streamable HTTP and enter the URL.

Why the database half gets the strictest rules

In a repo, a bad change is one commit away from being reversed. In a WordPress database there's no such thing, and one wrong UPDATE can rewrite every post on the site.

So that's where Kitepod is strict. Codex can run read-only SQL directly (30-second limit, 500 rows, secrets redacted), which means it can investigate as much as it likes. Any SQL write waits for a person, who sees a dry-run row count before approving. User and role changes, search-replace and core updates wait too, on every policy.

Everyday edits outside the database's danger zone (a page, a menu item, an SEO field) run directly. Each one is snapshotted first, so the history the repo would normally give you exists for the database side as well.

Who it's for, and when to skip it

Developers who already use Codex and look after WordPress sites with more database than code: content-heavy sites, WooCommerce stores, sites built in a page builder.

But it isn't a deploy tool. Theme edits happen on the server in a draft theme, not in your Git repo, so pull those changes back if your theme is version-controlled. WordPress version control covers how the two fit together.

Prefer Cursor or Claude Code? The server's the same, only the client changes: see Cursor and WordPress or Claude and WordPress. There's a broader comparison of WordPress MCP options at WordPress MCP.

Finer points

Does Codex support remote MCP servers with OAuth?

Yes, as of October 2026. OpenAI's docs describe streamable HTTP servers configured with a url, and codex mcp login <server-name> for servers that support OAuth.

Is there a WordPress password in my Codex config?

There isn't. Codex logs in to Kitepod with OAuth, and the config file holds only the URL.

Where does the config live?

In ~/.codex/config.toml, or .codex/config.toml inside a trusted project. The CLI, IDE extension and ChatGPT desktop app share it.

Can Codex run WP-CLI on my site?

Yes. Real WP-CLI commands go through Kitepod. Read-only ones run straight away; ones that write need a person's approval.

What if a long Codex run goes wrong halfway?

You don't have to unpick it edit by edit. Kitepod groups the work, so you can roll back a single change, everything from one task, or the entire session in one request. Snapshots are kept for 90 days, and anything that needed approval only happened if a person said yes.

Is Kitepod free with Codex?

Yes, with no cap on sites or tool calls. Codex usage comes out of your OpenAI plan as usual.

Your repo already has a history. Now the database does too.