What works
Codex supports MCP servers over streamable HTTP and can send custom headers with each request. PageForge authenticates Codex with a personal access token in the X-PageForge-MCP-API-Key header, limited to the scopes you choose.
With PageForge Free, Codex can read templates, generated pages, SEO fields and diagnostics, check rows against a template, and preview pages without creating them. With PageForge Pro, it can also make changes you approve, such as updating SEO titles and descriptions or starting a generation run. Bulk and risky changes are previewed and wait for your confirmation.
Set it up
- In PageForge > Connections, turn on the MCP connection and choose Create personal access token.
- Copy the token and the MCP server URL. PageForge shows the token only once.
- Store the token in an environment variable, for example
PAGEFORGE_MCP_TOKEN. - Add the server to your Codex configuration, usually
~/.codex/config.toml, as shown below, with the URL from Connections. - Start Codex and check that PageForge’s tools are available.
[mcp_servers.pageforge]
url = "https://example.com/wp-json/pageforge/v1/mcp"
env_http_headers = { "X-PageForge-MCP-API-Key" = "PAGEFORGE_MCP_TOKEN" }
Limits and notes
- PageForge’s Client configuration has no Codex preset. Use the example above, or adapt the generic configuration to Codex’s format.
- MCP options belong to Codex and can change. Check OpenAI’s Codex documentation if a key is renamed.
- Tokens do not expire on their own. Revoke a token in Connections when you no longer need it.
Pro Approved changes are available on every Pro plan with an active license.
