Software Planning ToolSAFE
An experiment in software planning using MCP
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
[](https://smithery.ai/server/@NightTrek/Software-planning-mcp)
A Model Context Protocol (MCP) server designed to facilitate software development planning through an interactive, structured approach. This tool helps break down complex software projects into manageable tasks, track implementation progress, and maintain detailed development plans.
Features ✨
- Interactive Planning Sessions: Start and manage development planning sessions
- Todo Management: Create, update, and track development tasks
- Complexity Scoring: Assign complexity scores to tasks for better estimation
- Code Examples: Include relevant code snippets in task descriptions
- Implementation Plans: Save and manage detailed implementation plans
Installation 🛠️
Installing via Smithery
To install Software Planning Tool for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @NightTrek/Software-planning-mcp --client claude
Manual Installation
- Clone the repository
- Install dependencies:
pnpm install
- Build the project:
pnpm run build
- Add to your MCP settings configuration (typically located at
~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json):
{
"mcpServers": {
"software-planning-tool": {
"command": "node",
"args": [
"/path/to/software-planning-tool/build/index.js"
],
"disabled": false,
"autoApprove": []
}
}
}Available Tools 🔧
start_planning
Start a new planning session with a specific goal.
{
goal: string c65e83451a2eOBSERVED · 2026-10-01Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add software-planning-tool -- npx -y [email protected]
{
"mcpServers": {
"software-planning-tool": {
"command": "npx",
"args": [
"-y",
"[email protected]"
]
}
}
}Exposed tools (6)
1 read · 4 write · 1 destructive. Blast radius: 1 tool can delete or overwrite — an agent that can be talked into calling a tool can be talked into calling this one.
| Tool | Risk | Description |
|---|---|---|
add_todo | write | Add a new todo item to the current plan |
get_todos | read | Get all todos in the current plan |
remove_todo | destructive | Remove a todo item from the current plan |
save_plan | write | Save the current implementation plan |
start_planning | write | Start a new planning session with a goal |
update_todo_status | write | Update the completion status of a todo item |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | WARN |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (1 observation(s))
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (2)
remove_todo
@types/node, typescript
Gates applied: no_behavioural_pass.
c65e83451a2efull audit observations/trust-audit/mcp-server/nighttrek__software-planning-tool.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-01 | c65e83451a2e | SAFE | B | 89 | first audit |
Questions
What is the Software Planning Tool MCP server?
An experiment in software planning using MCP
What tools does Software Planning Tool expose?
6 in total: 1 read-only, 4 that write, and 1 that can delete or overwrite (remove_todo). Every one is listed on this page with its risk.
Is Software Planning Tool safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B. Separately from the audit: 1 of its tools can destroy data, so scope the token you give it to what you actually need.
What credentials does Software Planning Tool need?
No credential environment variables were found in its source, so it appears to need none.
How does Software Planning Tool run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as software-planning-tool at 0.1.0.
How current is this page?
The grade is for one exact copy of the source (c65e83451a2e), read on 2026-10-01. The repository is watched and re-audited when it changes.