Before you start
- Codex with Streamable HTTP MCP support
- Permission to add a local client configuration
Add the public server URL
The installed Codex CLI and official documentation support adding an HTTP MCP server with the --url option. Run the example below only if you choose to change your own client configuration. No API key is required by LazyCoder’s public retrieval service.
Inspect the actual tools
Use Codex’s MCP controls to inspect LazyCoder. Confirm a real list_recipes/get_recipe tool call returns current public content. A configuration entry alone is not a connection test.
Keep retrieval and generation distinct
Copy a starter from the selected recipe, verify its version and release, then provide your private facts to the assistant. A successful protocol retrieval does not prove the promised result was generated correctly in Codex.
Codex CLI example
This example uses the server you are viewing. Local clients on this computer can reach localhost; hosted clients require a publicly reachable endpoint. It changes your client only if you run or save it yourself.
Loading this page’s endpoint…
Guidance checked October 28, 2026. Current real-host first-use and generated-output acceptance are pending. Official Codex MCP documentation ↗
Your next step
Confirm tool retrieval in your own client and review the result against the recipe checklist.