Connect Codex
Connect Codex to WordPress using its MCP configuration and verify the site.

Video coming soon
Your next step is ready.
Follow the complete written guide below.
The video will join it here when it’s ready.
Before you start
- Complete Install EMCP Free and Pro and Connect an AI agent.
- Have the named app installed with MCP support available.
Let’s do this, step by step.
Step 01
Start the Codex route
Open Setup → Connection → MCP. The current dashboard labels its Codex setup card ChatGPT App. Select that card, choose OAuth or Application password, and use only its Codex instructions.
This lesson connects Codex. The current EMCP dashboard labels this setup card ChatGPT App. Select it, then follow the Codex configuration steps shown here. ChatGPT connectors are a separate setup.
Step 02
Open the Codex configuration
Open ~/.codex/config.toml; on Windows this is %USERPROFILE%\.codex\config.toml. Preserve the existing configuration.
This lesson is for Codex. ChatGPT connectors are a separate setup. We will use Codex's connection configuration so the steps do not depend on a particular settings layout.
Step 03
Add the server address
Add the block below with your own endpoint. Do not add a password header when using browser sign-in.
Give the server a name and paste the complete address. This configuration describes where the site is; sign-in supplies permission to access it.
[mcp_servers.emcp-tools]
url = "https://your-site.example/wp-json/mcp/emcp-tools-server"
Step 04
Authenticate
Reconnect Codex and authenticate the server through its MCP settings or the installed CLI's MCP login command. Approve the WordPress browser prompt.
Complete the connection's sign-in and check the WordPress account before approving. Return to Codex and make sure the server is enabled.
Step 05
Use a generated password configuration if needed
Choose the Codex-compatible client configuration on EMCP Connection, select Application password, and copy the generated TOML header block.
If browser sign-in is unavailable, use the generated Authorization header in the same server configuration. It contains a credential, so never show it on screen or paste it into chat.
Step 06
Confirm Step 4 with a real request
After adding the connection, click I’ve added it, continue in WordPress. Reload the app and send the read-only prompt. Check the wizard’s successful first call and compare records with Pages. On failure or No call yet, inspect the reason and Run a server test.
Return to WordPress and continue to Test the connection. Reload your app, then ask it to list pages. Check the wizard’s result and the actual page titles. A server test is a useful diagnosis if the call fails, but it does not prove the app completed its request.
Identify the connected WordPress site URL. List accessible pages with titles, IDs and status. Do not create, edit or delete anything.
You’re done when…
The app reads real page records from the intended site without changing anything.
Keep the reference handy.
The docs cover tool details and requirements for this lesson.
You only need the guide for the app or builder you use. Ready to build? Try an Elementor draft or use Gutenberg.
A brief becomes a real page.