powerplan

io.github.CynaConsPublished by GitHub account CynaConsv0.10.0Updated Oct 29, 2026

MCP server that makes PLAN.md the operational backbone of agentic development

Overview

AI-generated overview

Local MCP server that gives assistants a structured API over a project's PLAN.md: read iterations, add and complete tasks, and report progress.

What you can do
  • Read the plan: show the current iteration as raw text or JSON, fetch one version, list iterations, find tasks and view the backlog.
  • Create and edit: bootstrap a PLAN.md, add majors, iterations and tasks, complete, reopen, remove or defer tasks, optionally tagging the agent.
  • Manage lifecycle: start and close iterations and lint the plan structure.
  • Report status: produce a compact plan skim and a turn-end status view to paste into the chat.
When to use it
Useful when agents work from a PLAN.md roadmap and you want them to update tasks and iterations through scoped tools instead of hand-editing the file, especially with several agents writing to the same plan.
Requirements
Runs locally over stdio; needs uv (uvx) or Python 3.10+, or a pip install of powerplan-mcp. Optional environment variables PYTHONIOENCODING and PYTHONUNBUFFERED are recommended for stdio. No accounts or API keys. Tools default to the nearest PLAN.md found by walking up from the working directory, or accept a plan_path.
Before you install
Tools write to PLAN.md: create_plan with force overwrites an existing file, and task and iteration mutations change the plan in place. The server presents itself as the single writer, so avoid other tools editing the same file concurrently. It also asks clients to append a status report to every major turn, which adds output to replies.

Installation

In SourceWeft

  1. Open powerplan in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

powerplan

PLAN.md as the operational backbone of agentic development.

powerplan is an MCP server that gives coordinators and worker agents a human-language API over your project’s PLAN.md: show progress, create iterations, complete tasks, keep the header truthful — without freeform file thrash.

mcp-name: io.github.CynaCons/powerplan

MCP server namepowerplan
PyPIpowerplan-mcp (powerplan is a different, unrelated package)
Registryio.github.CynaCons/powerplan
Statusv0.10.0 — miniplan turn report (PLAN.md)
SiteGitHub Pages
Pairs withPowerSpawn (optional)

Install

You need uv (provides uvx) or Python 3.10+.

bash
uvx powerplan-mcp

That is the stdio MCP server. Point your client at it:

Claude Code / Cursor / .mcp.json

json
{  "mcpServers": {    "powerplan": {      "command": "uvx",      "args": ["powerplan-mcp"],      "env": {        "PYTHONIOENCODING": "utf-8",        "PYTHONUNBUFFERED": "1"      }    }  }}

Claude Desktop

Same block in claude_desktop_config.json (mcpServers).

Grok (~/.grok/config.toml or project config)

toml
[mcp_servers.powerplan]command = "uvx"args = ["powerplan-mcp"]env = { PYTHONUNBUFFERED = "1", PYTHONIOENCODING = "utf-8" }enabled = true

pip (no uv)

bash
pip install powerplan-mcp
json
{  "mcpServers": {    "powerplan": {      "command": "python",      "args": ["-m", "powerplan"],      "env": {        "PYTHONIOENCODING": "utf-8",        "PYTHONUNBUFFERED": "1"      }    }  }}

Agent guide

Prefer scoped tools. Do not read all of PLAN.md to figure out what to do.

  1. If tools fail with “no PLAN.md” → create_plan first.
  2. show_miniplan — what to work on now, in the plan's own format: the current iteration verbatim with the neighbouring headers. Start every session here.
  3. get_current_iteration — the same, as JSON.
  4. get_iteration(version) — one iteration’s tasks and progress.
  5. Mutate with add_task / add_tasks / complete_task (indexes for several) / start_iteration / close_iteration.
  6. show_plan is a human skim, not a dump.
  7. End every major turn (files changed, tasks ticked or added, a check run, an iteration closed) with a miniplan in the chat, then show_current_iteration pasted verbatim in a code block, so the user sees status and progress at a glance. The server sends this rule to every client in its MCP instructions.

A miniplan is a turn-end task report in the plan's own format, printed in the reply and never written to a file: the show_miniplan block verbatim with its checkboxes flipped, plus an ## Off-plan section for quick items the turn is tracking that are not in PLAN.md yet, each marked → plan, → backlog or → drop. Format and example: docs/MINIPLAN.md. Ships as the miniplan skill for Claude Code, Cursor, Codex and Grok (.claude/skills/, .cursor/skills/, .codex/skills/, .grok/skills/).

Every tool accepts optional plan_path (relative or absolute). Default: walk up from cwd to the nearest PLAN.md.

Optional agent on mutations writes a trailing [agent: id] tag on the touched line.


Why

Agents often edit PLAN.md by hand. Headers drift, “COMPLETE” gets stamped without proof, and multi-agent swarms step on each other. powerplan is the single writer: tolerant reader, surgical writer, optional [agent: …] tags.


Tools

ToolBehavior
create_planBootstrap ./PLAN.md (or plan_path) when missing; force to overwrite
show_miniplanSession opener — raw PLAN.md snippet: the current (or named) iteration byte-for-byte, neighbours collapsed to header lines (before/after). Also seeds the turn-end miniplan report
get_current_iterationPreferred for agents — scoped JSON for current work
get_iterationJSON for one version (tasks, progress)
list_iterations / find_task / get_backlogNavigate without full-file reads
create_major / create_iteration / add_task / add_tasksSurgical mutations (batch add in one write)
complete_task / reopen_task / remove_task / defer_taskOne or many (indexes / tasks); optional [agent: id]
start_iteration / close_iterationACTIVE/current vs COMPLETE lifecycle
check_planStructure lint
show_current_iterationTurn closer — status view (status, progress count, goal, tasks) to paste at the end of every major turn
show_planCompact human skim (not a full dump)

Managed plan format

ConstructPattern
Major## vX.Y — Title
Iteration### vX.Y.Z — Title
Goal**Goal:** …
Tasks- [ ] / - [x]
Backlog## Backlog

Phase-like headers and other prose are preserved as opaque blocks.


From source

Clone, editable install, or PowerSpawn submodule — for contributors.

bash
git clone https://github.com/CynaCons/powerplan.gitcd powerplanpip install -e ".[dev]"python -m powerplan          # same stdio server# or: powerplan-mcp

PowerSpawn can vendor this repo as a git submodule. Register both MCP servers — they do not merge:

json
{  "mcpServers": {    "powerplan": {      "command": "uvx",      "args": ["powerplan-mcp"]    },    "powerspawn": {      "command": "python",      "args": ["-m", "powerspawn.mcp_server"]    }  }}

Path-only (no install): python /path/to/powerplan/powerplan_server.py

Landing page: cd site && npm ci && npm run dev


Releasing (maintainers)

Full procedure, identities, and failure history: docs/RELEASING.md. Agent checklist: project skill release-powerplan (/release-powerplan).

Short path: bump every version file listed in that guide → pytest -q → tag vX.Y.Z → push the tag. .github/workflows/publish.yml uploads powerplan-mcp to PyPI, then server.json to the MCP Registry as io.github.CynaCons/powerplan.


License

MIT — see LICENSE.

Source: README.md at commit da1423c

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

4
  1. v0.10.0LatestOct 29, 2026
  2. v0.9.0Oct 8, 2026
  3. v0.8.0Sep 19, 2026
  4. v0.7.0Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts