Skip to main content
Glama

Software Planning Tool πŸš€ (Deprecated)

WARNING

Deprecated and no longer maintained. The source and manual installation instructions remain available for reference.

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: Memory Bank MCP Server

Installation πŸ› οΈ

For existing users who still need to run this unmaintained project, use the manual/local setup below rather than Smithery.

Manual / Local Installation

  1. Clone the repository

  2. Install dependencies:

pnpm install
  1. Build the project:

pnpm run build
  1. 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": []
    }
  }
}

Smithery installation notice

The previous Smithery CLI installation route is no longer recommended. Smithery is shutting down its connection management services on October 31, 2026 and deprecating its current CLI and SDK versions. Smithery remains a public, non-proxied MCP registry; use the manual/local setup above instead of the former Smithery install command.

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 required

update_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:

  1. Start a planning session:

await client.callTool("software-planning-tool", "start_planning", {
  goal: "Create a React-based dashboard application"
});
  1. 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
  `
});
  1. Update todo status:

await client.callTool("software-planning-tool", "update_todo_status", {
  todoId: todo.id,
  isComplete: true
});
  1. 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.json

Building

pnpm run build

Testing

Test all features using the MCP inspector:

pnpm run inspector

License πŸ“„

MIT


Made with ❀️ using the Model Context Protocol

Available Tools

6 tools
add_todoB

Add a new todo item to the current plan

Inputs: title (required), description (required), complexity (required), codeExample.

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_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

    A3.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: add_todo, get_todos, remove_todo, and update_todo_status handle CRUD operations for todos, while save_plan and start_planning manage the planning session lifecycle. The descriptions make it easy to differentiate between todo management and session control functions.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case, such as add_todo, get_todos, and save_plan. This uniformity makes the toolset predictable and easy to understand, with no deviations in naming conventions.

    Tool Count5/5

    With 6 tools, the server is well-scoped for a software planning tool, covering todo management and session operations without being overly sparse or bloated. Each tool serves a clear purpose, making the count appropriate for the domain.

    Completeness5/5

    The toolset provides complete coverage for the software planning domain: start_planning initiates sessions, add_todo/get_todos/update_todo_status/remove_todo handle full todo lifecycle management, and save_plan allows persistence. There are no obvious gaps, enabling agents to perform all essential planning workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that provides structured workflow tools for managing software development projects through different complexity levels, offering specialized modes for project planning, design, implementation, and documentation.
      5
      35 npm
      2
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Facilitates software development planning through interactive sessions that break down projects into manageable tasks with complexity scoring, code examples, and implementation plan management.
      6
      34 npm
      MIT