Install Respira for WordPress in Codex
Click Install in Codex on the dashboard, paste the copied command in Terminal,
and Respira writes ~/.codex/config.toml for you. Every WordPress site on your
account is pre-wired with the access scope you selected.
- Open the dashboard and click Install in Codex.
The dashboard mints a short-lived install token and copies one command. The token carries your selected access scope, so read-only, content, builder, and full installs all use the same button.
- Paste the copied command in Terminal.
The command runs Respira's installer, redeems the token, and writes only the
respira-wordpressMCP entry into~/.codex/config.toml. Existing Codex MCP servers stay in place. - Restart Codex.
Quit and reopen Codex so it loads the new server. Codex prints any MCP errors on startup, so keep the terminal visible for the first launch.
- Confirm the server is live.
In Codex, ask: list the MCP servers currently loaded. You should see
respira-wordpress. - Ask Codex to edit a site.
Try: using respira-wordpress, list my connected sites and pick the first one. then show me the last three pages I edited.
Prefer manual TOML?
Codex reads from ~/.codex/config.toml on macOS and Linux, and
%USERPROFILE%\.codex\config.toml on Windows. Download the Codex config from
the dashboard, or paste this block and replace the placeholder:
[mcp_servers.respira-wordpress]
command = "npx"
args = ["-y", "@respira/wordpress-mcp-server"]
[mcp_servers.respira-wordpress.env]
RESPIRA_CONFIG_B64 = "<paste from dashboard>" Codex says "server failed to start".
-
Check
node -v. Codex spawnsnpxwhich needs Node 18+. -
Run
npx @respira/wordpress-mcp-server --doctorin any shell. It prints what is wrong: missing base64 value, bad API key, unreachable site, etc. -
The TOML must contain one
[mcp_servers.respira-wordpress]block. If you already have a Respira entry, replace it. Two entries with the same name will collide. -
Make sure
RESPIRA_CONFIG_B64is on one line with no line breaks inside the quotes.
Prefer single-site config (no dashboard)?
If you just want one site and no dashboard involvement, swap
RESPIRA_CONFIG_B64 for two env lines:
[mcp_servers.respira-wordpress.env]
WORDPRESS_URL = "https://yoursite.com"
WORDPRESS_API_KEY = "respira_your_api_key" The API key is the per-site token from your WordPress admin (Respira, Settings, API tokens). You can rotate it anytime.
Things to ask Codex, once it is connected
- using respira-wordpress, list my connected sites and which builder each one runs
- on site A, scan the homepage for accessibility issues and list WCAG violations
- duplicate the pricing page on site B and change every price ending in 99 to 95
- find every page that still mentions the old company name and list them with URLs
- translate the menu titles on site C into Spanish and save as a new menu
- show the last ten snapshots on site D and roll back the one at 11pm last night
- build me a shortlist of pages that load slower than 2 seconds on mobile
Every write lands as a duplicate or draft. Codex asks before each tool call, so you stay in control.
Why Codex plus Respira fits
- Codex is a fast CLI agent. Respira is a patient WordPress backend. Together you can edit production sites without slowing the agent down for confirmation pings.
- One installer command, every site. The dashboard token carries the access scope and site inventory; the installer writes the right TOML for you.
- 187+ tools. Full read/write across posts, pages, menus, ACF, Woo catalog, media. Codex can plan a multi-page refactor and execute it.
- Snapshots on every write. Codex loops move fast. Respira keeps a safety net so rollback is one sentence away.