powerplan
PYPI · POWERPLAN-MCP
MCP server that makes PLAN.md the operational backbone of agentic development
Available components
Last scanned (3 hours ago)
Scores higher than 95% of PyPI servers
Category Project Management
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to CynaCons/powerplan). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2921 tokens (~121/item across 24 items; 24 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 68% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "remove_task" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 25 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- Security disclosure: unverified → fail ▼ functional
- 4 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 2 Nov 26 +1
- Stability: 0.97 → pass security
- 1 Nov 26 −1
- Stability: pass → 0.97 functional
- 29 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.9.0 → 0.10.0 functional
- 26 Oct 26 0
- Stability: 0.97 → pass security
- 25 Oct 26 0
- Stability: pass → 0.97 functional
- 21 Oct 26 +10
- Provenance: unverified → pass ▲ security
- The attested source repository moved: CynaCons/powerplan security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed pypi/powerplan-mcp@0.10.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | CynaCons/powerplan |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/CynaCons/powerplan/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3572249368 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:9a8fe6082999e8875dd5a4f1d8986cba315828cb945ba7cea1b89d42887d60c0 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_task ~88
Append a checkbox task to an iteration.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | Optional agent id tag written as [agent: id] on touched lines. |
| done | boolean | – | – |
| plan_path | string | – | Optional path to PLAN.md (relative to cwd or absolute). Default: walk up from cwd to nearest PLAN.md. |
| text | string | yes | – |
| version | string | yes | – |
No output schema declared.
No examples provided.
add_tasks ~119
Append several checkbox tasks in one write. Prefer this over repeated add_task. Shared done/agent apply to every item.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | Optional agent id tag written as [agent: id] on touched lines. |
| done | boolean | – | Mark every added task done (default false). |
| plan_path | string | – | Optional path to PLAN.md (relative to cwd or absolute). Default: walk up from cwd to nearest PLAN.md. |
| tasks | array | yes | Task texts to append, in order. |
| version | string | yes | – |
No output schema declared.
No examples provided.
add_to_backlog ~115
Append one (text) or many (texts) items to Future (Backlog) in one write.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | Optional agent id tag written as [agent: id] on touched lines. |
| checkbox | boolean | – | – |
| plan_path | string | – | Optional path to PLAN.md (relative to cwd or absolute). Default: walk up from cwd to nearest PLAN.md. |
| text | string | – | One backlog item. |
| texts | array | – | Several backlog items, in order. One write. |
No output schema declared.
No examples provided.
append_prose ~54
Append freeform markdown at top level.
| Name | Type | Req | Description |
|---|---|---|---|
| plan_path | string | – | Optional path to PLAN.md (relative to cwd or absolute). Default: walk up from cwd to nearest PLAN.md. |
| text | string | yes | – |
No output schema declared.
No examples provided.
check_plan ~52
Structure lint: duplicates, multiple current, complete-with-open-tasks.
| Name | Type | Req | Description |
|---|---|---|---|
| plan_path | string | – | Optional path to PLAN.md (relative to cwd or absolute). Default: walk up from cwd to nearest PLAN.md. |
No output schema declared.
No examples provided.
close_iteration ~83
Mark iteration COMPLETE. Requires force=true if open tasks remain. Optional stamp (e.g. date) appended to title.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | – |
| plan_path | string | – | Optional path to PLAN.md (relative to cwd or absolute). Default: walk up from cwd to nearest PLAN.md. |
| stamp | string | – | – |
| version | string | yes | – |
No output schema declared.
No examples provided.
complete_task ~222
Tick one or many tasks in one write. For several, pass indexes (preferred after get_iteration) or tasks. For exactly one, index or task still work.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | Optional agent id tag written as [agent: id] on touched lines. |
| expect | string | – | Optional guard for a single task: current text must match or the edit is refused. Ignored/rejected with tasks/indexes. Agent tags are ignored in the comparison. |
| index | integer | – | One 1-based position. One addressing mode. |
| indexes | array | – | Several 1-based positions. Prefer this after get_iteration. One write. One addressing mode. |
| plan_path | string | – | Optional path to PLAN.md (relative to cwd or absolute). Default: walk up from cwd to nearest PLAN.md. |
| task | string | – | One task (exact, else unique substring). One addressing mode. |
| tasks | array | – | Several task texts (exact, else unique substring). One write. One addressing mode. |
| version | string | yes | – |
No output schema declared.
No examples provided.
create_iteration ~111
Create ### vX.Y.Z — Title iteration.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | Optional agent id tag written as [agent: id] on touched lines. |
| description | string | – | – |
| goal | string | – | – |
| major | string | – | – |
| plan_path | string | – | Optional path to PLAN.md (relative to cwd or absolute). Default: walk up from cwd to nearest PLAN.md. |
| status | string | – | – |
| title | string | yes | – |
| version | string | yes | – |
No output schema declared.
No examples provided.
create_major ~69
Create ## vX.Y — Title major section.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| plan_path | string | – | Optional path to PLAN.md (relative to cwd or absolute). Default: walk up from cwd to nearest PLAN.md. |
| title | string | yes | – |
| version | string | yes | – |
No output schema declared.
No examples provided.
create_plan ~127
Bootstrap a new PLAN.md when none exists (powernote-style skeleton). Default path: ./PLAN.md in cwd. Refuses overwrite unless force=true.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | Overwrite existing file if true. |
| goal | string | – | – |
| philosophy | string | – | – |
| plan_path | string | – | Optional path to PLAN.md (relative to cwd or absolute). Default: walk up from cwd to nearest PLAN.md. |
| seed_major | boolean | – | Include v0.1 / v0.1.0 starter shell (default true). |
| title | string | yes | – |
No output schema declared.
No examples provided.
defer_task ~233
Move one or many tasks to the backlog in one write. For several, pass indexes or tasks. Shared reason/agent apply to every item.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | Optional agent id tag written as [agent: id] on touched lines. |
| expect | string | – | Optional guard for a single task: current text must match or the edit is refused. Ignored/rejected with tasks/indexes. Agent tags are ignored in the comparison. |
| index | integer | – | One 1-based position. One addressing mode. |
| indexes | array | – | Several 1-based positions. Prefer this after get_iteration. One write. One addressing mode. |
| plan_path | string | – | Optional path to PLAN.md (relative to cwd or absolute). Default: walk up from cwd to nearest PLAN.md. |
| reason | string | – | Optional why, appended to the backlog entry. |
| task | string | – | One task (exact, else unique substring). One addressing mode. |
| tasks | array | – | Several task texts (exact, else unique substring). One write. One addressing mode. |
| version | string | yes | – |
No output schema declared.
No examples provided.
find_task ~53
Locate tasks by substring match (JSON).
| Name | Type | Req | Description |
|---|---|---|---|
| plan_path | string | – | Optional path to PLAN.md (relative to cwd or absolute). Default: walk up from cwd to nearest PLAN.md. |
| text | string | yes | – |
No output schema declared.
No examples provided.
get_backlog ~46
Backlog section items (JSON).
| Name | Type | Req | Description |
|---|---|---|---|
| plan_path | string | – | Optional path to PLAN.md (relative to cwd or absolute). Default: walk up from cwd to nearest PLAN.md. |
No output schema declared.
No examples provided.
get_current_iteration ~64
JSON for the *current* iteration (what to work on now). Preferred agent entry — avoids reading all of PLAN.md.
| Name | Type | Req | Description |
|---|---|---|---|
| plan_path | string | – | Optional path to PLAN.md (relative to cwd or absolute). Default: walk up from cwd to nearest PLAN.md. |
No output schema declared.
No examples provided.
get_iteration ~58
JSON for one iteration by version (goal, tasks, progress).
| Name | Type | Req | Description |
|---|---|---|---|
| plan_path | string | – | Optional path to PLAN.md (relative to cwd or absolute). Default: walk up from cwd to nearest PLAN.md. |
| version | string | yes | – |
No output schema declared.
No examples provided.
list_iterations ~55
List iterations filtered by open | complete | all.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | – |
| plan_path | string | – | Optional path to PLAN.md (relative to cwd or absolute). Default: walk up from cwd to nearest PLAN.md. |
No output schema declared.
No examples provided.
remove_task ~195
Delete one or many tasks in one write. For several, pass indexes or tasks. Resolve-all then drop (indexes do not shift).
| Name | Type | Req | Description |
|---|---|---|---|
| expect | string | – | Optional guard for a single task: current text must match or the edit is refused. Ignored/rejected with tasks/indexes. Agent tags are ignored in the comparison. |
| index | integer | – | One 1-based position. One addressing mode. |
| indexes | array | – | Several 1-based positions. Prefer this after get_iteration. One write. One addressing mode. |
| plan_path | string | – | Optional path to PLAN.md (relative to cwd or absolute). Default: walk up from cwd to nearest PLAN.md. |
| task | string | – | One task (exact, else unique substring). One addressing mode. |
| tasks | array | – | Several task texts (exact, else unique substring). One write. One addressing mode. |
| version | string | yes | – |
No output schema declared.
No examples provided.
reopen_task ~217
Untick one or many tasks in one write. For several, pass indexes or tasks. For exactly one, index or task still work.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | Optional agent id tag written as [agent: id] on touched lines. |
| expect | string | – | Optional guard for a single task: current text must match or the edit is refused. Ignored/rejected with tasks/indexes. Agent tags are ignored in the comparison. |
| index | integer | – | One 1-based position. One addressing mode. |
| indexes | array | – | Several 1-based positions. Prefer this after get_iteration. One write. One addressing mode. |
| plan_path | string | – | Optional path to PLAN.md (relative to cwd or absolute). Default: walk up from cwd to nearest PLAN.md. |
| task | string | – | One task (exact, else unique substring). One addressing mode. |
| tasks | array | – | Several task texts (exact, else unique substring). One write. One addressing mode. |
| version | string | yes | – |
No output schema declared.
No examples provided.
set_iteration_goal ~63
Set/replace **Goal:** on an iteration.
| Name | Type | Req | Description |
|---|---|---|---|
| goal | string | yes | – |
| plan_path | string | – | Optional path to PLAN.md (relative to cwd or absolute). Default: walk up from cwd to nearest PLAN.md. |
| version | string | yes | – |
No output schema declared.
No examples provided.
show_current_iteration ~83
Status view of the current iteration: status, progress count, goal and tasks. Paste it verbatim in a ``` code block at the end of every major turn so the user sees the plan's state at a glance.
| Name | Type | Req | Description |
|---|---|---|---|
| plan_path | string | – | Optional path to PLAN.md (relative to cwd or absolute). Default: walk up from cwd to nearest PLAN.md. |
No output schema declared.
No examples provided.
show_miniplan ~172
Raw PLAN.md snippet: the current (or named) iteration byte-for-byte under its major header, with the neighbouring iterations collapsed to their header lines. The plan's own format is the view — start every session here instead of reading the whole file, and seed the turn-end miniplan report from this block (verbatim, checkboxes flipped, plus an "## Off-plan" section for items not in PLAN.md).
| Name | Type | Req | Description |
|---|---|---|---|
| after | integer | – | Following iterations shown as header lines only. |
| before | integer | – | Preceding iterations shown as header lines only. |
| plan_path | string | – | Optional path to PLAN.md (relative to cwd or absolute). Default: walk up from cwd to nearest PLAN.md. |
| version | string | – | Iteration to show; default = the current iteration. |
No output schema declared.
No examples provided.
show_plan ~62
Compact index: counts + current iteration. Agents should prefer get_current_iteration / get_iteration over this or full PLAN.md.
| Name | Type | Req | Description |
|---|---|---|---|
| plan_path | string | – | Optional path to PLAN.md (relative to cwd or absolute). Default: walk up from cwd to nearest PLAN.md. |
No output schema declared.
No examples provided.
start_iteration ~56
Mark iteration ACTIVE / current; clears other current markers.
| Name | Type | Req | Description |
|---|---|---|---|
| plan_path | string | – | Optional path to PLAN.md (relative to cwd or absolute). Default: walk up from cwd to nearest PLAN.md. |
| version | string | yes | – |
No output schema declared.
No examples provided.
update_task ~257
Rewrite task text, preserving done state. One task: text + index/task. Several: changes[{text, index|task, expect?}].
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | Optional agent id tag written as [agent: id] on touched lines. |
| changes | array | – | Several rewrites in one write. Do not mix with the singular text + index/task shape. |
| expect | string | – | Optional guard for a single task: current text must match or the edit is refused. Ignored/rejected with tasks/indexes. Agent tags are ignored in the comparison. |
| index | integer | – | One 1-based position. One addressing mode. |
| indexes | array | – | Several 1-based positions. Prefer this after get_iteration. One write. One addressing mode. |
| plan_path | string | – | Optional path to PLAN.md (relative to cwd or absolute). Default: walk up from cwd to nearest PLAN.md. |
| task | string | – | One task (exact, else unique substring). One addressing mode. |
| tasks | array | – | Several task texts (exact, else unique substring). One write. One addressing mode. |
| text | string | – | New text for a single task. |
| version | string | yes | – |
No output schema declared.
No examples provided.
How do I install the powerplan MCP server?
powerplan runs locally as a PyPI package, launched with uvx powerplan-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · powerplan-mcp
claude mcp add cynacons-powerplan -- uvx powerplan-mcp
What is the powerplan MCP server?
powerplan is an MCP server listed in the public MCP registry as io.github.CynaCons/powerplan. MCP server that makes PLAN.md the operational backbone of agentic development. This page covers its PyPI package (powerplan-mcp).
Is the powerplan MCP server safe to use?
powerplan scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the powerplan MCP server expose?
powerplan exposes 24 tools: get_current_iteration, get_iteration, list_iterations, find_task, get_backlog, and 19 more. Their descriptions and schemas cost roughly 2,654 tokens of context every time the server is loaded.
Is the powerplan MCP server still maintained?
powerplan is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the powerplan MCP server under?
powerplan declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.