# Codex + WordPress MCP: Connect Codex to WordPress, server setup with Respira

> Codex + WordPress MCP: connect Codex to WordPress through Respira's MCP server with two commands and a browser sign-in, no API key in the config. Edits land…

Source: https://www.respira.press/integrations/codex

---

Codex connects to a WordPress site through Respira's MCP server with two commands and a browser sign-in, no API key in the config file. Once connected, Codex reads and edits the site's pages in their own page builder, on a copy first, with 90 days of undo.

1. **Open the dashboard and choose *OpenAI desktop / Codex*.**  
Select the WordPress site you want to connect. Respira generates the exact remote MCP server name and URL for that site.  
[Open dashboard setup](https://www.respira.press/dashboard/mcp)
2. **Run the first command in Terminal.**  
The `codex mcp add` command registers the selected site. It does not contain an API key and leaves your other Codex MCP servers in place.  
```  
codex mcp add respira-my-site --url https://yoursite.com/wp-json/respira/v1/mcp  
```
3. **Run the second command and approve access.**  
The `codex mcp login` command opens your browser. Sign in to Respira, review the requested read and write access, then choose **Approve**.  
```  
codex mcp login respira-my-site  
```
4. **Confirm the connection.**  
Restart the OpenAI desktop app or reopen Codex if the tools do not appear immediately, then ask: *list the MCP servers currently loaded*.
5. **Ask Codex to edit a site.**  
Try: *using Respira, list the last three WordPress pages I edited and tell me which builder they use*.
Prefer manual TOML? 

Codex reads from `~/.codex/config.toml`. The first command writes the equivalent remote-server entry below. After adding it manually, still run `codex mcp login respira-my-site` to authenticate: 

```
[mcp_servers.respira-my-site]
url = "https://yoursite.com/wp-json/respira/v1/mcp"
```

The browser sign-in does not open or finish. 
- Run `codex mcp login respira-my-site` again using the exact server name from the first command.
- Check that the WordPress site is online and its `/wp-json/` address is not blocked by a firewall. **Respira › Troubleshoot** in wp-admin runs that check from the site's own server, along with the sign-in discovery document and the Authorization header, and writes a report for your host when one fails.
- In WordPress, open **Settings → Permalinks**, choose **Post name**, and save once if the MCP address returns 404\.
- Remove and re-add the server if the saved URL points to a different site.

## 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.
- **OAuth instead of copied secrets.** Add each site with two standard Codex commands, then approve it in your browser. No WordPress API key is stored in Codex config.
- **300+ 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.

[Set up in the dashboard](https://www.respira.press/dashboard/mcp) [Pricing](https://www.respira.press/pricing)
