Developer · Local MCP server

Claude Octopus

Spawn multiple specialized Claude Code 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/claude-octopus
Version
1.1.10
Status
Active
Category
developer
Transport
stdio (local process)
Package
npm
Published
2026-05-20
Updated
2026-05-20
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/claude-octopus
Source
Registry API entry

Packages

RegistryPackageVersionTransportEnvironment variables
npmclaude-octopus1.1.10stdioANTHROPIC_API_KEY (secret), CLAUDE_TOOL_NAME, CLAUDE_MODEL, CLAUDE_PERMISSION_MODE, CLAUDE_ALLOWED_TOOLS, CLAUDE_APPEND_PROMPT, CLAUDE_FACTORY_ONLY

How to connect Claude Octopus

Claude Octopus runs locally from a Node.js package published to the npm registry: claude-octopus version 1.1.10. 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 claude-octopus@1.1.10. It reads these environment variables: ANTHROPIC_API_KEY (secret), CLAUDE_TOOL_NAME, CLAUDE_MODEL, CLAUDE_PERMISSION_MODE, CLAUDE_ALLOWED_TOOLS, CLAUDE_APPEND_PROMPT and CLAUDE_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": {
    "claude-octopus": {
      "command": "npx",
      "args": [
        "-y",
        "claude-octopus@1.1.10"
      ],
      "env": {
        "ANTHROPIC_API_KEY": "<secret>",
        "CLAUDE_TOOL_NAME": "<value>",
        "CLAUDE_MODEL": "<value>",
        "CLAUDE_PERMISSION_MODE": "<value>",
        "CLAUDE_ALLOWED_TOOLS": "<value>",
        "CLAUDE_APPEND_PROMPT": "<value>",
        "CLAUDE_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)

All 2 →
ServerRunsEndpoint or package
Codex OctopusSpawn multiple specialized Codex agents as MCP servers, each independently configured.Local · stdionpm: codex-octopus

More developer servers

All 5,152 →
ServerRunsEndpoint or package
Claude FindPull Deep Memory from across your Claude Code Sessions - when you need it.Local · stdionpm: claude-find
Claude HandoffSession handoff for Claude Code: list sessions and build handoff docs another agent continues from.Local · stdioPyPI: claude-handoff
Claude MCP BridgeWraps Claude Code CLI as MCP tools: query, search, structured, ping, listSessions.Local · stdionpm: claude-mcp-bridge
Claude Memory ManagerCross-session memory for Claude Code - context capture, semantic search, recall.Local · stdioPyPI: claude-memory-manager
Claude Prompt OptimizerScores, compiles & optimizes prompts for any LLM. Zero AI calls inside. Freemium.Local · stdionpm: claude-prompt-optimizer-mcp
Claude Prompts MCPReusable prompt templates, multi-step workflow chains, and quality gates for any MCP client.Local · stdionpm: claude-prompts
Claude Remind MCPSearch past Claude Code conversations. Local BM25 over JSONL with one-click claude --resume.Local · stdionpm: claude-remind-mcp
Claude ReplaySession checkpoint & recovery for Claude Code: resume, search, tag, and export recorded sessions.Local · stdioPyPI: claude-replay