Documentation
Codex
Configure Milkey in Codex using the native MCP server block in your Codex config.
Codex works well with Milkey when you want the agent to resolve and fetch skills during code-editing or review loops without copying large prompt templates into every task.
The cleanest setup is to register Milkey as a remote MCP server in your Codex configuration and keep the auth header inside the MCP server block.
Configure Codex
The client-specific work here is mostly about where the config lives and which field names the client expects.
- Add Milkey to your Codex MCP configuration file, commonly `~/.codex/config.toml` for a personal setup.
- If your team keeps repo-scoped Codex config, add the same block to that project-specific config instead.
~/.codex/config.toml
[mcp_servers.milkey]url = "https://mcp.vexelityai.com/mcp"startup_timeout_sec = 30.0tool_timeout_sec = 90.0[mcp_servers.milkey.http_headers]Authorization = "Bearer mk_sk_your_api_key_id_your_secret"Verify the connection
- Start a fresh Codex session after saving the config so the MCP server list reloads cleanly.
- Confirm Codex can see the `milkey` server and that tools are available before you rely on it in a longer task.
- Run a short prompt that should call Milkey immediately, such as a skill lookup or doc-oriented question.
Test prompt
Use Milkey to find the right skill for FastAPI authentication in this repository and explain the main implementation rules.Operational tips
- Keep the startup and tool timeouts if your network path to Milkey is occasionally slow; they reduce false negatives during server startup.
- Use a dedicated API key for Codex so you can rotate or revoke it independently from other agents.