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 分