Overture MCP Server

Agent Plan Visualizer - An Open-Source MCP Server by Sixth

Local serverstdioTypeScript

What is the Overture MCP server?

Most developer tooling work still happens through a UI a human drives. Overture MCP server moves it into the conversation instead. Agent Plan Visualizer - An Open-Source MCP Server by Sixth.

The short version

Getting it running

The server ships on npm as overture-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

The tools it exposes

The server publishes 12 tools. What each one is for:

  • submit_plan — Submit complete plan as XML
  • get_approval — Wait for user approval (blocks until approved)
  • update_node_status — Update node status + output during execution
  • plan_completed — Mark plan as successfully completed
  • plan_failed — Mark plan as failed with error message
  • check_rerun — Check if user requested a node re-run
  • check_pause — Check if user paused execution
  • get_resume_info — Get full context for resuming a paused plan
  • request_plan_update — Request incremental plan modifications
  • create_new_plan — Signal creation of a new plan
  • get_usage_instructions — Get agent-specific instructions
  • Cursor — More Agents (Cline, Copilot, Sixth AI)

What it needs from you

Configuration is passed through the environment: OVERTURE_HTTP_PORT, OVERTURE_WS_PORT, OVERTURE_AUTO_OPEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Before you can approve, Overture shows what's needed: - Empty required fields — counted per node - Branch selections — which decisions are pending - Progress indicator — visual completion tracking - Expandable items — click to see details - Color coding — Green (done) / Orange (pending) The Approve button stays disabled until all requirements are met. ---

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 12 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Overture.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Overture's toolset — submit_plan, get_approval, update_node_status and 9 more — is a fair guide to whether it matches your workflow. It is maintained by sixhq; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Available tools

ToolWhat it does
submit_planSubmit complete plan as XML
get_approvalWait for user approval (blocks until approved)
update_node_statusUpdate node status + output during execution
plan_completedMark plan as successfully completed
plan_failedMark plan as failed with error message
check_rerunCheck if user requested a node re-run
check_pauseCheck if user paused execution
get_resume_infoGet full context for resuming a paused plan
request_plan_updateRequest incremental plan modifications
create_new_planSignal creation of a new plan
get_usage_instructionsGet agent-specific instructions
Cursor<details> <summary><strong>More Agents (Cline, Copilot, Sixth AI)</strong></summary>

How to install the Overture MCP server

{
  "mcpServers": {
    "overture": {
      "command": "npx",
      "args": ["-y", "overture-mcp"],
      "env": {
        "OVERTURE_HTTP_PORT": "your-value",
        "OVERTURE_WS_PORT": "your-value",
        "OVERTURE_AUTO_OPEN": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

Before you can approve, Overture shows what's needed: - Empty required fields — counted per node - Branch selections — which decisions are pending - Progress indicator — visual completion tracking - Expandable items — click to see details - Color coding — Green (done) / Orange (pending) The Approve button stays disabled until all requirements are met. ---

VariableDescriptionRequired
OVERTURE_HTTP_PORTConfiguration value read at startup.Optional
OVERTURE_WS_PORTConfiguration value read at startup.Optional
OVERTURE_AUTO_OPENConfiguration value read at startup.Optional

Example prompts to try

  • Use Overture to submit plan.
  • Use Overture to get approval.
  • Use Overture to update node status.

Frequently asked questions

It connects Overture to MCP-compatible AI assistants such as Claude and Cursor, exposing 12 tools (submit_plan, get_approval, update_node_status, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Overture directly.