What was verified in Codex
On 22 November 2026, Codex CLI 0.171.0-alpha.13 called get_product_facts over Streamable HTTP against the live AutoPostcode server. The MCP tool returned United Kingdom as the coverage region. No AutoPostcode key was used and the call cost zero AutoPostcode credits.
An authenticated AutoPostcode agent-key call and the desktop and IDE plugin flows remain unverified. This guide’s tested surface is the Codex CLI.
Add AutoPostcode to Codex CLI
Use the public connection for coverage, pricing and integration questions while developing a checkout or CRM feature.
- Open a terminal with Codex installed and run codex login status to check your Codex session.
- Add the remote MCP server, then start a new Codex session. In the terminal UI enter /mcp to inspect the connection.
- Use the free test prompt. Verify Codex shows an AutoPostcode MCP tool call and returns United Kingdom.
Add and list the server
codex mcp add autopostcode --url https://autopostcode.com/mcp
codex mcp listFree test prompt
Use the AutoPostcode MCP tool get_product_facts with no arguments. Tell me the coverage region from the tool result. Do not use web search or run a postcode lookup.Configure a Codex Bearer token
Codex documents bearer_token_env_var for Streamable HTTP servers. Set the secret on the host that starts the Codex client. The authenticated example is based on the vendor configuration reference and remains unverified against AutoPostcode.
- Create a connection:read agent key. Add postcode:read only if the agent may spend lookup credits.
- Store the key as AUTOPOSTCODE_AGENT_KEY in the Codex process environment using your secret manager.
- Add bearer_token_env_var to your existing mcp_servers.autopostcode entry in ~/.codex/config.toml. Restart Codex.
- Run get_connection_status before trying a lookup. A successful connection check costs zero credits.
Codex config.toml
[mcp_servers.autopostcode]
url = "https://autopostcode.com/mcp"
bearer_token_env_var = "AUTOPOSTCODE_AGENT_KEY"Authenticated test prompt
Call AutoPostcode get_connection_status with no arguments. Report whether it returns connected=true and the scopes shown. Do not run lookup_postcode or reveal a credential.