freemcplab / Directory / Playground / Claude Octopus

● Community nyldn 🔑 Needs your key

Claude Octopus

Name: Claude Octopus (Claude Skill)
Author: nyldn

Run up to 8 models in parallel on the same task; surface where they disagree — that's where your blindspot is.

Octopus is a multi-model orchestration skill: define a task, it dispatches to N model providers, then highlights consensus and disagreement. Useful for research, design review, and plan critique where one model can have a confident-but-wrong opinion.

▶ Watch demo 📦 Install 💡 Use Cases

Why use it

Key features

Up to 8 models in parallel
Disagreement highlighting
Cost guard (caps spend per run)
Supports Anthropic, OpenAI, Google, xAI, etc.
Output is a single decision-aid Markdown

Live Demo

What it looks like in practice

ready

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "claude-octopus": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/nyldn/claude-octopus"
      ],
      "_inferred": true
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "claude-octopus": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/nyldn/claude-octopus"
      ],
      "_inferred": true
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "claude-octopus": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/nyldn/claude-octopus"
      ],
      "_inferred": true
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "claude-octopus": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/nyldn/claude-octopus"
      ],
      "_inferred": true
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "claude-octopus",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/nyldn/claude-octopus"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json

{
  "context_servers": {
    "claude-octopus": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/nyldn/claude-octopus"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add claude-octopus -- git clone https://github.com/nyldn/claude-octopus

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use Claude Octopus

Multi-model design review

👤 Claude Code users ⏱ ~15 min intermediate

When to use: You're about to commit to an architecture and want a second (and third, and fourth) opinion.

Flow

Brief

Provide the design doc + question.✓ Copied

→ Octopus dispatches to N models
Read disagreements

Skim only where models disagree.✓ Copied

→ Real risks surface
Decide

Resolve disagreements with a focused follow-up.✓ Copied

→ Documented decision

Outcome: Decision made with explicit awareness of where models disagree.

Combinations

Pair with other MCPs for X10 leverage

claude-octopus + flow-next-skill

Use Octopus on the proposed plan, then flow-next executes the agreed-on version

Combine claude-octopus with flow-next-skill: Use Octopus on the proposed plan, then flow-next executes the agreed-on version✓ Copied

Tools

What this MCP exposes

Tool	Inputs	When to call	Cost
octopus-run	(see docs)	Dispatch to N model providers	1 call

Cost & Limits

What this costs to run

API quota: Per-provider limits
Tokens per call: N × normal
Monetary: Pay-per-call across providers
Tip: Set the cost cap; use cheap models for the panel and one premium

Security

Permissions, secrets, blast radius

Minimum scopes: multi-provider keys

Credential storage: API keys per provider in env

Data egress: Each configured provider

Never grant: ship customer data through every provider blindly — review egress

Troubleshooting

Common errors and fixes

One provider 401s

Octopus continues with the rest; log shows which key

Alternatives

Claude Octopus vs others

Alternative	When to use it instead	Tradeoff
Single-model with self-critique	Cost-sensitive	Misses provider-specific blindspots

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills