Software Planning Tool
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Software Planning Tool Create a plan for a React dashboard"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Software Planning Tool π
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
Related MCP server: Development Workflow MCP Server
Installation π οΈ
Clone the repository
Install dependencies:
pnpm installBuild the project:
pnpm run buildAdd 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 // The software development goal to plan
}add_todo
Add a new todo item to the current plan.
{
title: string, // Title of the todo item
description: string, // Detailed description
complexity: number, // Complexity score (0-10)
codeExample?: string // Optional code example
}get_todos
Retrieve all todos in the current plan.
// No parameters requiredupdate_todo_status
Update the completion status of a todo item.
{
todoId: string, // ID of the todo item
isComplete: boolean // New completion status
}save_plan
Save the current implementation plan.
{
plan: string // The implementation plan text
}remove_todo
Remove a todo item from the current plan.
{
todoId: string // ID of the todo item to remove
}Example Usage π
Here's a complete example of using the software planning tool:
Start a planning session:
await client.callTool("software-planning-tool", "start_planning", {
goal: "Create a React-based dashboard application"
});Add a todo item:
const todo = await client.callTool("software-planning-tool", "add_todo", {
title: "Set up project structure",
description: "Initialize React project with necessary dependencies",
complexity: 3,
codeExample: `
npx create-react-app dashboard
cd dashboard
npm install @material-ui/core @material-ui/icons
`
});Update todo status:
await client.callTool("software-planning-tool", "update_todo_status", {
todoId: todo.id,
isComplete: true
});Save the implementation plan:
await client.callTool("software-planning-tool", "save_plan", {
plan: `
# Dashboard Implementation Plan
## Phase 1: Setup (Complexity: 3)
- Initialize React project
- Install dependencies
- Set up routing
## Phase 2: Core Features (Complexity: 5)
- Implement authentication
- Create dashboard layout
- Add data visualization components
`
});Development π¨
Project Structure
software-planning-tool/
βββ src/
β βββ index.ts # Main server implementation
β βββ prompts.ts # Planning prompts and templates
β βββ storage.ts # Data persistence
β βββ types.ts # TypeScript type definitions
βββ build/ # Compiled JavaScript
βββ package.json
βββ tsconfig.jsonBuilding
pnpm run buildTesting
Test all features using the MCP inspector:
pnpm run inspectorLicense π
MIT
Made with β€οΈ using the Model Context Protocol
Available Tools
8 toolsadd_todoB
Add a new todo item to the current plan
Inputs: title (required), complexity (required), description (required), codeExample.
get_planA
Get the current implementation plan as formatted text
Inputs: no named parameters.
get_todosA
Get all todos in the current plan
Inputs: no named parameters.
remove_todoA
Remove a todo item from the current plan
Inputs: todoId (required).
save_planC
Save the current implementation plan
Inputs: plan (required).
start_planningB
Start a new planning session with a goal
Inputs: goal (required).
update_goalA
Update the description of the current goal
Inputs: description (required).
update_todo_statusB
Update the completion status of a todo item
Inputs: todoId (required), isComplete (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
TDQS
Scored across 8 tools
Each tool targets a distinct action: session management (start, save), goal editing, todo CRUD (add, remove, get, update status), and plan retrieval. There is no ambiguity about which tool to use for a given operation.
All tool names follow a consistent verb_noun pattern in snake_case (start_planning, add_todo, update_goal). The verbs are clear and predictable, with only minor gerund deviation in start_planning that does not hinder readability.
Eight tools is well-scoped for a planning session domain, covering lifecycle operations without redundancy or bloat. Each tool earns its place in the set.
The surface covers the full planning lifecycle: creating a session, saving, updating the goal, managing todos (add, remove, update status), and retrieving the plan. There are no obvious missing operations for the intended purpose.
Related MCP Connectors
MCP server for generating rough-draft project plans from natural-language prompts.
An MCP server that automatically collects feedback on your MCP server.
A MCP server built for developers enabling Git based project management with project and personalβ¦
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server that assists with the orchestration of new software projects by applying standardized templates and best practices in design patterns and software architecture.17MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enforces development discipline and workflow best practices, guiding users through a structured process of coding, testing, documenting, committing, and releasing.28 npm1MIT
- AlicenseAqualityDmaintenanceMCP server providing feedback-oriented development workflows with a Web UI and desktop application for interactive user confirmation, session tracking, and smart prompt management.2MIT
- AlicenseAqualityDmaintenanceAn MCP server that helps AI agents plan and track software projects using the Conducted Development methodology, providing artifact validation, kickoff guidance, and project rituals.751 npm1MIT