Overture MCP — Anwendungsfälle, Installieren & Live-Demo

Warum nutzen

Hauptfunktionen

Interactive React Flow canvas — pan, zoom, node-level controls
Dynamic inputs (text, number, boolean, secret, file attachment)
Branch comparison with pros/cons before choosing
One-line install across Claude Code, Cursor, Cline, Copilot

Live-Demo

In der Praxis

overture.replay ▶ bereit

0/0

Installieren

Wählen Sie Ihren Client

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

{
  "mcpServers": {
    "overture": {
      "command": "npx",
      "args": [
        "-y",
        "Overture"
      ],
      "_inferred": true
    }
  }
}

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

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

{
  "mcpServers": {
    "overture": {
      "command": "npx",
      "args": [
        "-y",
        "Overture"
      ],
      "_inferred": true
    }
  }
}

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

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "overture": {
      "command": "npx",
      "args": [
        "-y",
        "Overture"
      ],
      "_inferred": true
    }
  }
}

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

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "overture": {
      "command": "npx",
      "args": [
        "-y",
        "Overture"
      ],
      "_inferred": true
    }
  }
}

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

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "overture",
      "command": "npx",
      "args": [
        "-y",
        "Overture"
      ]
    }
  ]
}

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json

{
  "context_servers": {
    "overture": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "Overture"
        ]
      }
    }
  }
}

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

claude mcp add overture -- npx -y Overture

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

Anwendungsfälle

Praxisnahe Nutzung: Overture

Review your agent's plan in a flowchart before it writes code

👤 Anyone running coding agents on real repos ⏱ ~15 min beginner

Wann einsetzen: You've been burned by an agent confidently writing 800 lines of wrong code — you want a gate.

Voraussetzungen

Claude Code or equivalent agent — claude.ai/code

Ablauf

Install

Run claude mcp add overture-mcp -- npx overture-mcp to wire it into Claude Code.✓ Kopiert

→ Overture web UI reachable at shown URL
Ask for a feature; plan opens in canvas

Implement an auth middleware. Before coding, use overture to produce a plan graph.✓ Kopiert

→ Nodes for each step appear in the Overture UI
Approve or redirect nodes

Node 3 looks wrong — reject it with a comment 'use existing middleware at ./lib/auth.ts instead'✓ Kopiert

→ Plan regenerates; agent only codes after you press approve

Ergebnis: Agent writes code you actually asked for — you caught the wrong assumption at step 3, not commit 3.

Fallstricke

Canvas becomes noisy on huge features — Break feature into sub-plans; Overture supports multi-project tabs

Kombinieren mit: claude-code

Compare two implementation approaches side by side

👤 Engineers choosing between designs ⏱ ~20 min intermediate

Wann einsetzen: You're torn between two approaches (Redis cache vs in-memory) and want the agent to plan both.

Ablauf

Ask for two branches

Plan this caching feature in two branches: (A) Redis, (B) in-memory LRU. Show pros/cons for each.✓ Kopiert

→ Overture renders two branches with comparison
Pick and execute

Approve branch B. Execute only that path.✓ Kopiert

→ Only the chosen branch runs

Ergebnis: Informed decision between alternatives without committing code to both.

Inject secrets into a plan node without committing them

👤 Anyone scripting deploy plans ⏱ ~10 min intermediate

Wann einsetzen: A step needs an API key; you want to provide it at run-time, not in the prompt history.

Ablauf

Mark the node as needing a secret

The deploy node needs DEPLOY_TOKEN as a secret input. Pause until provided.✓ Kopiert

→ Overture shows a secret field awaiting input
Paste into the UI; node unlocks

(in Overture UI) paste token and click resume✓ Kopiert

→ Plan continues; secret not in chat history

Ergebnis: Agents run privileged steps without secrets leaking into transcripts.

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

overture + claude-code

Use Overture as the approval layer for every Claude Code task

From now on, for any task estimated >30 min, use overture to plan before coding.✓ Kopiert

overture + vibe-check

Plan → sanity check → execute

After Overture produces a plan, run vibe_check on it before I approve.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

Werkzeug	Eingaben	Wann aufrufen	Kosten
plan_create	goal: str, context?: str	Start of any multi-step coding task	LLM tokens for planning
plan_update	plan_id, node_changes	React to user approve/reject	0
plan_execute	plan_id, from_node?	After user approval	tool calls + tokens
plan_branch	plan_id, from_node, alt_goal	Compare alternatives	LLM tokens

Kosten & Limits

Was der Betrieb kostet

API-Kontingent: None — local app
Tokens pro Aufruf: Planning adds ~1-3k tokens up front; saves more in avoided wrong code
Kosten in €: Free, open source
Tipp: Use plans only for non-trivial features; trivial edits don't need a graph

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: Secrets entered in the UI, stored in local browser storage per plan

Datenabfluss: None by default — runs on localhost

Fehlerbehebung

Häufige Fehler und Lösungen

Canvas URL returns ERR_CONNECTION_REFUSED

Overture UI port (default 3939) not bound; check MCP server logs or set OVERTURE_PORT

Prüfen: curl http://localhost:3939

Plan generation hangs

Your agent is waiting on LLM; check the agent's own logs for rate limit / token exhaustion

Node rejections not taking effect

Some agents cache plans — explicitly say 'regenerate the plan from node X with my feedback'

Alternativen

Overture vs. andere

Alternative	Wann stattdessen	Kompromiss
sequentialthinking-tools	You want a text plan, not a canvas	No visual comparison of branches
shrimp-task-manager	You want persistent tasks, not interactive approval	Different loop — more async, less gated

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen