Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Spawn multiple specialized Codex agents as MCP servers, each independently configured.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
CODEX_API_KEY, CODEX_TOOL_NAME, CODEX_MODEL, CODEX_SANDBOX_MODE, CODEX_APPROVAL_POLICY, CODEX_APPEND_INSTRUCTIONS, CODEX_FACTORY_ONLY标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"codex-octopus": {
"command": "npx",
"args": [
"-y",
"codex-octopus"
],
"env": {
"CODEX_API_KEY": "your-value",
"CODEX_TOOL_NAME": "your-value",
"CODEX_MODEL": "your-value",
"CODEX_SANDBOX_MODE": "your-value",
"CODEX_APPROVAL_POLICY": "your-value",
"CODEX_APPEND_INSTRUCTIONS": "your-value",
"CODEX_FACTORY_ONLY": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add codex-octopus --env CODEX_API_KEY=your-value --env CODEX_TOOL_NAME=your-value --env CODEX_MODEL=your-value --env CODEX_SANDBOX_MODE=your-value --env CODEX_APPROVAL_POLICY=your-value --env CODEX_APPEND_INSTRUCTIONS=your-value --env CODEX_FACTORY_ONLY=your-value -- npx -y codex-octopus运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"codex-octopus": {
"command": "npx",
"args": [
"-y",
"codex-octopus"
],
"env": {
"CODEX_API_KEY": "your-value",
"CODEX_TOOL_NAME": "your-value",
"CODEX_MODEL": "your-value",
"CODEX_SANDBOX_MODE": "your-value",
"CODEX_APPROVAL_POLICY": "your-value",
"CODEX_APPEND_INSTRUCTIONS": "your-value",
"CODEX_FACTORY_ONLY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"codex-octopus": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"codex-octopus"
],
"env": {
"CODEX_API_KEY": "your-value",
"CODEX_TOOL_NAME": "your-value",
"CODEX_MODEL": "your-value",
"CODEX_SANDBOX_MODE": "your-value",
"CODEX_APPROVAL_POLICY": "your-value",
"CODEX_APPEND_INSTRUCTIONS": "your-value",
"CODEX_FACTORY_ONLY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
CODEX_TOOL_NAME envCODEX_MODEL envCODEX_SANDBOX_MODE envCODEX_APPROVAL_POLICY envCODEX_APPEND_INSTRUCTIONS envCODEX_FACTORY_ONLY env这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 xiaolai 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:CODEX_API_KEY
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(1.0.1)于7个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Fomu MCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Kenya government form guides: checklists, draft letters, eCitizen, Huduma, timelines. Sample data.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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.
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.
@openai/codex)CODEX_API_KEY env var) or inherited from parent processnpm install codex-octopus
Or use npx directly in your .mcp.json (see Quick Start below).
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.
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 questions.", "CODEX_EFFORT": "minimal" } } } }
Your MCP client now sees three distinct tools — code_reviewer, test_writer, quick_qa — each purpose-built.
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 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.
Each non-factory instance exposes:
| Tool | Purpose |
|---|---|
| Send a task to the agent, get a response + thread_id |
_reply | Continue a previous conversation by thread_id |
Per-invocation parameters (override server defaults):
| Parameter | Description |
|---|---|
prompt | The task or question (required) |
cwd | Working directory override |
model | Model override |
additionalDirs | Extra directories the agent can access |
effort | Reasoning effort (minimal to xhigh) |
sandboxMode | Sandbox override (can only tighten, never loosen) |
approvalPolicy | Approval override (can only tighten, never loosen) |
networkAccess | Enable network access from sandbox |
webSearchMode | Web search: disabled, cached, live |
instructions | Additional instructions (prepended to prompt) |
All configuration is via environment variables in .mcp.json. Every env var is optional.
| Env Var | Description | Default |
|---|---|---|
CODEX_TOOL_NAME | Tool name prefix ( and _reply) | codex |
CODEX_DESCRIPTION | Tool description shown to the host AI | generic |
CODEX_SERVER_NAME | MCP server name in protocol handshake | codex-octopus |
CODEX_FACTORY_ONLY | Only expose the factory wizard tool | false |
| Env Var | Description | Default |
|---|---|---|
CODEX_MODEL | Model (gpt-5-codex, o3, codex-1, etc.) | SDK default |
CODEX_CWD | Working directory | process.cwd() |
CODEX_SANDBOX_MODE | read-only, workspace-write, danger-full-access | read-only |
CODEX_APPROVAL_POLICY | never, on-failure, on-request, untrusted | on-failure |
CODEX_EFFORT | minimal, low, medium, high, xhigh | SDK default |
CODEX_ADDITIONAL_DIRS | Extra directories (comma-separated) | none |
CODEX_NETWORK_ACCESS | Allow network from sandbox | false |
CODEX_WEB_SEARCH | disabled, cached, live | disabled |
| Env Var | Description |
|---|---|
CODEX_INSTRUCTIONS | Replaces the default instructions |
CODEX_APPEND_INSTRUCTIONS | Appended to the default (usually what you want) |
| Env Var | Description |
|---|---|
CODEX_PERSIST_SESSION | true/false — enable session resume (default: true) |
| Env Var | Description | Default |
|---|---|---|
CODEX_API_KEY | OpenAI API key for this agent | inherited from parent |
workspace-write or danger-full-access.cwd, the agent's configured base directory is automatically added to additionalDirectories.sandboxMode and approvalPolicy can only tighten (e.g., workspace-write → read-only), never loosen.CODEX_PERSIST_SESSION=false.CODEX_API_KEY in generated configs.┌─────────────────────────────────┐
│ MCP Client │ │ (Claude Desktop, Cursor, etc.) │ │ │ │ Sees: code_reviewer, │ │ test_writer, quick_qa │ └──────────┬──────────────────────┘ │ JSON-RPC / stdio ┌──────────▼──────────────────────┐ │ Codex Octopus (per instance) │ │ │ │ Env: CODEX_MODEL=o3 │ │ CODEX_SANDBOX_MODE=... │ │ CODEX_APPEND_INSTRUCTIONS │ │ │ │ Calls: Codex SDK thread.run() │ └──────────┬──────────────────────┘ │ in-process ┌──────────▼──────────────────────┐ │ Codex SDK → Codex CLI │ │ Runs autonomously: reads files,│ │ writes code, runs commands │ │ Returns result + thread_id │ └─────────────────────────────────┘
web_search tools with minimal reasoning effort. Use low or higher if web search is needed.pnpm install
pnpm build # compile TypeScript pnpm test # run tests (vitest) pnpm test:coverage # coverage report
ISC - Xiaolai Li