Claude Octopus

Created By
xiaolai2 months ago
One brain, many arms. Spawn multiple specialized Claude Code agents as MCP servers via the Agent SDK. Each instance gets its own model, tools, prompt, and personality.
Overview

Claude Octopus

One brain, many arms.

An MCP server that wraps the Claude Agent SDK, letting you run multiple specialized Claude Code agents — each with its own model, tools, system prompt, and personality — from any MCP client.

Why

Claude Code is powerful. But one instance does everything the same way. Sometimes you want a strict code reviewer that only reads files. A test writer that defaults to TDD. A cheap quick helper on Haiku. A deep thinker on Opus.

Claude Octopus lets you spin up as many of these as you need. Same binary, different configurations.

Quick Start

{
  "mcpServers": {
    "claude": {
      "command": "npx",
      "args": ["claude-octopus"],
      "env": {
        "CLAUDE_PERMISSION_MODE": "bypassPermissions"
      }
    }
  }
}

Key Features

  • Multi-instance — run several agents with different configs simultaneously
  • 18 env vars — model, tools, effort, permissions, plugins, prompts, and more
  • Per-invocation overrides — change model, tools, effort, permissions per call
  • Session continuity — follow up on previous conversations via _reply tool
  • Factory wizard — generate .mcp.json configs interactively
  • Hot-configurable — plugins, effort, permissions adjustable per invocation

Server Config

{
  "mcpServers": {
    "claude": {
      "command": "npx",
      "args": [
        "claude-octopus"
      ],
      "env": {
        "CLAUDE_PERMISSION_MODE": "bypassPermissions"
      }
    }
  }
}
Project Info
Created At
2 months ago
Updated At
2 months ago
Author Name
xiaolai
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Crevio

a day ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

19 hours ago