iflow-mcp_kky42-codex-as-mcp

# codex-as-mcp [中文版](./README.zh-CN.md) `codex-as-mcp` is a small **Model Context Protocol (MCP)** server that lets MCP clients (Claude Code, Cursor, etc.) delegate work to the **Codex CLI**. It exposes two tools that run Codex in the server's current working directory: - `spawn_agent(prompt: str)` - `spawn_agents_parallel(agents: list[dict])` Under the hood, each agent runs something like: `codex exec --cd <server cwd> --skip-git-repo-check --dangerously-bypass-approvals-and-sandbox "<prompt>"`. Note: `--dangerously-bypass-approvals-and-sandbox` disables sandboxing and confirmation prompts. Use this server only in repos you trust. ## Use it in Claude Code There are two tools in codex-as-mcp  You can spawn parallel codex subagents using prompt.  Here's a sample Codex session delegating two tasks in parallel.  ## Quick start ### 1. Install Codex CLI **Requires Codex CLI >= 0.46.0** ```bash npm install -g @openai/codex@latest codex login # Verify installation codex --version ``` Make sure Codex CLI can run non-interactively on your machine (provider + credentials in `~/.codex/config.toml`, or via the provider-specific env var it references). #### Example: third-party provider + `env_key` If you're using a third-party provider, configure it in Codex `config.toml` and point `model_provider` at it. When a provider uses `env_key`, Codex CLI expects that env var to be present when it runs. Example: ```toml model_provider = "custom_provider" [model_providers.custom_provider] name = "custom_provider" base_url = "https://..." wire_api = "responses" env_key = "PROVIDER_API_KEY" show_raw_agent_reasoning = true ``` When using `codex-as-mcp`, make sure the MCP server process has that env var set, so it can pass it through to the spawned `codex` process. The env var name **must match** the `env_key` value above (here: `PROVIDER_API_KEY`). **Option A (recommended): set e…