/ Verzeichnis / Playground / Claude Octopus
● Community nyldn 🔑 Eigener Schlüssel nötig

Claude Octopus

von nyldn · nyldn/claude-octopus

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.

Warum nutzen

Hauptfunktionen

Live-Demo

In der Praxis

bereit

Installieren

Wählen Sie Ihren 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
    }
  }
}

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

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

Cursor nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "claude-octopus": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/nyldn/claude-octopus"
      ],
      "_inferred": true
    }
  }
}

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "Edit Configuration".

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

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

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

Continue nutzt ein Array von Serverobjekten statt einer Map.

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

In context_servers hinzufügen. Zed lädt beim Speichern neu.

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

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: Claude Octopus

Multi-model design review

👤 Claude Code users ⏱ ~15 min intermediate

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

Ablauf
  1. Brief
    Provide the design doc + question.✓ Kopiert
    → Octopus dispatches to N models
  2. Read disagreements
    Skim only where models disagree.✓ Kopiert
    → Real risks surface
  3. Decide
    Resolve disagreements with a focused follow-up.✓ Kopiert
    → Documented decision

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

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

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✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

WerkzeugEingabenWann aufrufenKosten
octopus-run (see docs) Dispatch to N model providers 1 call

Kosten & Limits

Was der Betrieb kostet

API-Kontingent
Per-provider limits
Tokens pro Aufruf
N × normal
Kosten in €
Pay-per-call across providers
Tipp
Set the cost cap; use cheap models for the panel and one premium

Sicherheit

Rechte, Secrets, Reichweite

Minimale Scopes: multi-provider keys
Credential-Speicherung: API keys per provider in env
Datenabfluss: Each configured provider
Niemals gewähren: ship customer data through every provider blindly — review egress

Fehlerbehebung

Häufige Fehler und Lösungen

One provider 401s

Octopus continues with the rest; log shows which key

Alternativen

Claude Octopus vs. andere

AlternativeWann stattdessenKompromiss
Single-model with self-critiqueCost-sensitiveMisses provider-specific blindspots

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen