powerplan

io.github.CynaCons由 GitHub 帳號 CynaCons 發布v0.10.0更新於 Oct 29, 2026

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

已驗證STDIO僅桌面效率與工作流開發者工具

概覽

AI 產生的概覽

本機 MCP 伺服器,為助理提供操作專案 PLAN.md 的結構化介面:檢視迭代、新增與完成任務並回報進度。

可以做什麼
  • 讀取計畫:以原始文字或 JSON 顯示目前迭代、取得指定版本、列出迭代、尋找任務並檢視待辦清單。
  • 建立與編輯:初始化 PLAN.md,新增主版本、迭代與任務,完成、重開、移除或延後任務,可選擇標註執行代理。
  • 管理生命週期:啟動與關閉迭代,並檢查計畫結構。
  • 回報狀態:產生精簡的計畫概覽與回合結束時的狀態檢視,方便貼進對話中。
適用情境
適合以 PLAN.md 作為路線圖、希望助理透過受控工具而非手動編輯來更新任務與迭代的情況,尤其是多個代理同時寫入同一份計畫時。
執行需求
以 stdio 在本機執行;需要 uv(uvx)或 Python 3.10+,也可用 pip 安裝 powerplan-mcp。建議設定環境變數 PYTHONIOENCODING 與 PYTHONUNBUFFERED 以配合 stdio。不需帳號或 API 金鑰。工具預設從目前目錄往上尋找最近的 PLAN.md,也可傳入 plan_path。
安裝前請注意
工具會寫入 PLAN.md:create_plan 搭配 force 會覆寫既有檔案,任務與迭代操作會直接修改計畫。伺服器自稱唯一寫入者,應避免其他工具同時編輯同一檔案。它也會要求用戶端在每個重要回合結尾附加狀態報告,使回覆內容增加。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 powerplan,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

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.

來源:README.md,提交 da1423c

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

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

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分