
Codex Octopus
io.github.xiaolaiPublished by GitHub account xiaolaiv1.0.1Updated Oct 24, 2026
Spawn multiple specialized Codex agents as MCP servers, each independently configured.
The publisher's own server: Octopus.do
Overview
Wraps the OpenAI Codex SDK so an assistant can run one or more separately configured Codex agents as tools, each with its own model, sandbox and instructions.
- What you can do
- Send a task or question to a configured Codex agent and get a response plus a thread_id for follow-up turns, with per-call overrides for working directory, model, reasoning effort, extra directories, sandbox and approval policy, network access and web search mode. Continue an earlier agent conversation by thread_id when session persistence is enabled. Run several instances side by side, each exposed under its own tool name with its own model, sandbox, effort and appended instructions. Use a factory instance that exposes a single wizard tool which generates a ready-made configuration entry from a plain description of the agent you want.
- When to use it
- Useful when you want several differently tuned coding agents in one MCP client, for example a read-only strict reviewer, a test writer with workspace write access and a cheap quick-answer helper, instead of a single general-purpose Codex instance.
- Requirements
- Local process run through npx or npm; needs Node.js 18 or newer and the Codex CLI package installed, since the SDK spawns it. An OpenAI API key is supplied through the CODEX_API_KEY environment variable or inherited from the parent process. All configuration is via environment variables.
Installation
In SourceWeft
- Open Codex Octopus in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
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 (
CODEX_API_KEYenv var) or inherited from parent process
Install
Or use npx directly in your .mcp.json (see Quick Start below).
Quick Start
Add to your .mcp.json:
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:
Your MCP client now sees three distinct tools — code_reviewer, test_writer, quick_qa — each purpose-built.
Agent Factory
Don't want to write configs by hand? Add a factory instance:
This exposes a single create_codex_mcp 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:
Per-invocation parameters (override server defaults):
Configuration
All configuration is via environment variables in .mcp.json. Every env var is optional.
Identity
Agent
Instructions
Advanced
Authentication
Security
- Sandbox defaults to
read-only— the agent can't write files unless you explicitly setworkspace-writeordanger-full-access. cwdoverrides preserve agent knowledge — when the host overridescwd, the agent's configured base directory is automatically added toadditionalDirectories.- Security overrides narrow, never widen — per-invocation
sandboxModeandapprovalPolicycan only tighten (e.g.,workspace-write→read-only), never loosen. _replytool respects persistence — not registered whenCODEX_PERSIST_SESSION=false.- API keys are redacted — the factory wizard never exposes
CODEX_API_KEYin generated configs.
Architecture
Known Limitations
minimaleffort + web_search: OpenAI does not allowweb_searchtools withminimalreasoning effort. Uselowor higher if web search is needed.
Development
License
ISC - Xiaolai Li
Source: README.md at commit c504a77
Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Octopus integrations
Octopus.do
do.octopusOfficial publisher
A remote MCP server that lets an assistant read and edit Octopus.do visual sitemaps — pages, blocks and review notes — as the signed-in user.

Octopus Energy (octopus-mcp)
Published by GitHub account mattoddie
Unofficial MCP server for UK Octopus Energy customers: lets an assistant read smart meter usage, costs, tariffs and bills, and optionally manage EV charging…

Claude Octopus
Published by GitHub account xiaolai
Wraps the Claude Agent SDK so an assistant can run multiple separately configured Claude Code agents as MCP tools, with timelines, transcripts and reports.

Octopus Energy
Published by GitHub account pipeworx-io
Octopus Energy's hosted MCP server; no sign-in required; Streamable HTTP; 48 tools.

Octopus Blackboard
Published by GitHub account octoryn
A local-first shared blackboard that lets multiple AI coding agents record claims, tasks, decisions, messages and commit attribution on one repo.