Other · Local MCP server
Codex Octopus
Spawn multiple specialized Codex agents as MCP servers, each independently configured.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.xiaolai/codex-octopus- Version
- 1.0.1
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-04-02
- Updated
- 2026-04-02
- Publisher
- xiaolai (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/xiaolai) · how
- Repository
- github.com/xiaolai/codex-octopus
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | codex-octopus | 1.0.1 | stdio |
How to connect Codex Octopus
Codex Octopus runs locally from a Node.js package published to the npm registry: codex-octopus version 1.0.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y codex-octopus@1.0.1. It reads these environment variables: CODEX_API_KEY (secret), CODEX_TOOL_NAME, CODEX_MODEL, CODEX_SANDBOX_MODE, CODEX_APPROVAL_POLICY, CODEX_APPEND_INSTRUCTIONS and CODEX_FACTORY_ONLY; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"codex-octopus": {
"command": "npx",
"args": [
"-y",
"codex-octopus@1.0.1"
],
"env": {
"CODEX_API_KEY": "<secret>",
"CODEX_TOOL_NAME": "<value>",
"CODEX_MODEL": "<value>",
"CODEX_SANDBOX_MODE": "<value>",
"CODEX_APPROVAL_POLICY": "<value>",
"CODEX_APPEND_INSTRUCTIONS": "<value>",
"CODEX_FACTORY_ONLY": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from xiaolai (GitHub)
| Server | Runs |
|---|---|
| Claude OctopusSpawn multiple specialized Claude Code agents as MCP servers, each independently configured. | Local · stdio |
More other servers
| Server | Runs |
|---|---|
| CodesignLocal design engine for AI agents: create, edit and export real, editable designs. | Local · stdio |
| codevConnect AI agents to codev for Salesforce projects, builds, releases, validations, and insights. | Remote · HTTP |
| Codewars MCPKeyless MCP server for Codewars: user ranks, honor, kata. | Local · stdio |
| Codex ContaminantsCodex Alimentarius CXS 193 - maximum levels for contaminants and toxins in. | Remote · HTTPLive check: ✓ handshake |
| Codex ServerOps MCPStateful Windows OpenSSH server operations for Codex with local credential handling. | Local · stdio |
| Codexrunledger MCPCodex run receipts your reviewer can trust. | Remote · HTTPLive check: ✗ no handshake |
| Codify MCPEasily create reusable automation tools from casual browser actions using Apify Agent. | Local · stdio |
| Código 07 · Human verification in PeruMarketplace of vetted human verifiers in Peru, hired and paid by AI agents in USDC via x402. | Remote · HTTPLive check: ✓ handshake |