Codex Octopus MCP server
io.github.xiaolai/codex-octopus·v1.0.1·20 starsSpawn multiple specialized Codex agents as MCP servers, each independently configured.
20 stars43 downloads/wk
Reviews
Write oneNobody has reviewed Codex Octopus yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Codex Octopus tools (1, 1 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
create_codex_mcpwrite action
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan25 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 2 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Codex Octopus compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 83/100
- higher than 65% of 48,255 servers
- Tools
- 1
- the typical server has 7
- Tools that change things
- 100%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 20
- more than 91% of 28,688 servers
- Downloads a week
- 43
- more than 35% of 12,191 servers with a package
What its tools let an agent do: 1 create
Install Codex Octopus in Claude Code, Cursor or VS Code
Runs npx -y codex-octopus on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add codex-octopus -- npx -y codex-octopus
What the publisher says
From the Codex Octopus repository's README, as published. We do not edit it. Read it on GitHub
Codex Octopus
One brain, many arms.
An MCP server that wraps the OpenAI Codex SDK, letting you run multiple specialized Codex agents — each with its own model, sandbox, effort, and personality — from any MCP client.
Why
Codex is powerful. But one instance does everything the same way. Sometimes you want a strict code reviewer in read-only sandbox. A test writer with workspace-write access. A cheap quick helper on minimal effort. A deep thinker on xhigh.
Codex Octopus lets you spin up as many of these as you need. Same binary, different configurations. Each one shows up as a separate tool in your MCP client.
Prerequisites
- Node.js >= 18
- Codex CLI — the Codex SDK spawns the Codex CLI under the hood, so you need it installed (@openai/codex)
- OpenAI API key (CODEXAPIKEY env var) or inherited from parent process
Install
npm install codex-octopusOr use npx directly in your .mcp.json (see Quick Start below).
Quick Start
Add to your .mcp.json:
{
"mcpServers": {
"codex": {
"command": "npx",
"args": ["codex-octopus@latest"],
"env": {
"CODEX_SANDBOX_MODE": "workspace-write",
"CODEX_APPROVAL_POLICY": "never"
}
}
}
}This gives you two tools: codex and codex_reply. That's it — you have Codex as a tool.
Multiple Agents
The real power is running several instances with different configurations:
{
"mcpServers": {
"code-reviewer": {
"command": "npx",
"args": ["codex-octopus@latest"],
"env": {
"CODEX_TOOL_NAME": "code_reviewer",
"CODEX_SERVER_NAME": "code-reviewer",
"CODEX_DESCRIPTION": "Strict code reviewer. Read-only sandbox.",
"CODEX_MODEL": "o3",
"CODEX_SANDBOX_MODE": "read-only",
"CODEX_APPEND_INSTRUCTIONS": "You are a strict code reviewer. Report real bugs, not style preferences.",
"CODEX_EFFORT": "high"
}
},
"test-writer": {
"command": "npx",
"args": ["codex-octopus@latest"],
"env": {
"CODEX_TOOL_NAME": "test_writer",
"CODEX_SERVER_NAME": "test-writer",
"CODEX_DESCRIPTION": "Writes thorough tests with edge case coverage.",
"CODEX_MODEL": "gpt-5-codex",
"CODEX_SANDBOX_MODE": "workspace-write",
"CODEX_APPEND_INSTRUCTIONS": "Write tests first. Cover edge cases. TDD."
}
},
"quick-qa": {
"command": "npx",
"args": ["codex-octopus@latest"],
"env": {
"CODEX_TOOL_NAME": "quick_qa",
"CODEX_SERVER_NAME": "quick-qa",
"CODEX_DESCRIPTION": "Fast answers to quick coding Your MCP client now sees three distinct tools — codereviewer, testwriter, quick_qa — each purpose-built.
Agent Factory
Don't want to write configs by hand? Add a factory instance:
{
"mcpServers": {
"agent-factory": {
"command": "npx",
"args": ["codex-octopus@latest"],
"env": {
"CODEX_FACTORY_ONLY": "true",
"CODEX_SERVER_NAME": "agent-factory"
}
}
}
}This exposes a single createcodexmcp tool — an interactive wizard. Tell it what you want ("a strict code reviewer with read-only sandbox") and it generates the .mcp.json entry for you.
Tools
Each non-factory instance exposes:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Codex Octopus: common questions
- Is Codex Octopus MCP server safe?
- Mostly: it is graded B (83/100). Read the Codex Octopus safety report
- How do I install Codex Octopus?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Codex Octopus need an API key?
- Yes. The registry entry asks for
CODEX_API_KEY. - Is Codex Octopus maintained?
- The last commit was 39 days ago (2026-09-26). The latest release is v1.0.1.
- How does Codex Octopus compare with other MCP servers?
- safety score 83/100 (higher than 65% of 48,255 servers); tools 1 (the typical server has 7); tools that change things 100% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.