Overture MCP — Casos de uso, Instalar & Demo ao vivo

Por que usar

Principais recursos

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

Demo ao vivo

Como fica na prática

overture.replay ▶ pronto

0/0

Instalar

Escolha seu cliente

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

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

Abra Claude Desktop → Settings → Developer → Edit Config. Reinicie após salvar.

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

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

Cursor usa o mesmo esquema mcpServers que o Claude Desktop. Config de projeto vence a global.

VS Code → Cline → MCP Servers → Edit

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

Clique no ícone MCP Servers na barra lateral do Cline, depois "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

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

Mesmo formato do Claude Desktop. Reinicie o Windsurf para aplicar.

~/.continue/config.json

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

O Continue usa um array de objetos de servidor em vez de um map.

~/.config/zed/settings.json

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

Adicione em context_servers. Zed recarrega automaticamente ao salvar.

claude mcp add overture -- npx -y Overture

Uma linha só. Verifique com claude mcp list. Remova com claude mcp remove.

Casos de uso

Usos do mundo real: Overture

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

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

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

Pré-requisitos

Claude Code or equivalent agent — claude.ai/code

Fluxo

Install

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

→ 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.✓ Copiado

→ 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'✓ Copiado

→ Plan regenerates; agent only codes after you press approve

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

Armadilhas

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

Combine com: claude-code

Compare two implementation approaches side by side

👤 Engineers choosing between designs ⏱ ~20 min intermediate

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

Fluxo

Ask for two branches

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

→ Overture renders two branches with comparison
Pick and execute

Approve branch B. Execute only that path.✓ Copiado

→ Only the chosen branch runs

Resultado: 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

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

Fluxo

Mark the node as needing a secret

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

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

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

→ Plan continues; secret not in chat history

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

Combinações

Combine com outros MCPs para 10× de alavancagem

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.✓ Copiado

overture + vibe-check

Plan → sanity check → execute

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

Ferramentas

O que este MCP expõe

Ferramenta	Entradas	Quando chamar	Custo
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

Custo e limites

O que custa rodar

Cota de API: None — local app
Tokens por chamada: Planning adds ~1-3k tokens up front; saves more in avoided wrong code
Monetário: Free, open source
Dica: Use plans only for non-trivial features; trivial edits don't need a graph

Segurança

Permissões, segredos, alcance

Armazenamento de credenciais: Secrets entered in the UI, stored in local browser storage per plan

Saída de dados: None by default — runs on localhost

Solução de problemas

Erros comuns e correções

Canvas URL returns ERR_CONNECTION_REFUSED

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

Verificar: 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'

Alternativas

Overture vs. outros

Alternativa	Quando usar	Troca
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

Mais

Recursos

📖 Leia o README oficial no GitHub

🐙 Ver issues abertas

🔍 Ver todos os 400+ servidores MCP e Skills