Skip to main content
Glama
enesjakozh
NightTrek

Software Planning Tool

by NightTrek
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

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

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

  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": []
    }
  }
}

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

ParametersJSON Schema
NameRequiredDescriptionDefault
titleYesTitle of the todo item
descriptionYesDetailed description of the todo item
complexityYesComplexity score (0-10)
codeExampleNoOptional code example

TDQS

B3.4/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description bears the full burden of behavioral disclosure. It only states the action, omitting prerequisites (e.g., existence of a current plan), side effects (e.g., modifies in-memory plan vs saved plan), and error behavior. This is insufficient for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no wasted words. It front-loads the primary purpose effectively, which is exactly what a concise description should do.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is too terse for a mutation tool with no annotations. It does not explain the dependency on a current plan, the workflow in which add_todo fits, or what happens if the plan state is invalid. This lack of context could lead to incorrect usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema provides 100% coverage with descriptions for all four parameters. The tool description adds no additional parameter meaning, so the schema carries the load. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb-resource pair ('Add a new todo item') and clarifies scope ('to the current plan'). This clearly distinguishes it from siblings like remove_todo, get_todos, and update_todo_status, which deal with different actions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: it is for adding new todo items to the current plan. However, there is no explicit guidance on when to use this instead of update_todo_status or what conditions must exist (e.g., an active plan). No alternatives or exclusions are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_todosA

Get all todos in the current plan

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It clearly indicates a read-only operation and adds the 'current plan' scope, but it does not disclose return format, ordering, or behavior when no plan is active. For a simple getter, this is adequate but minimal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence ('Get all todos in the current plan') that conveys all essential information without redundancy or filler. Every word contributes to the meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter read-only tool, this description is nearly complete. It states the resource and scope. There is no output schema, so the description could theoretically mention the return format, but 'get all todos' sufficiently implies the response. Sibling tool names further clarify context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the schema fully covers parameter semantics. With 0 params, the baseline is 4; the description adds no parameter-related detail, but none is needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Get'), identifies the resource ('all todos'), and scopes it ('current plan'). It clearly distinguishes this from sibling tools like get_plan (plan-level data) and add_todo/remove_todo/update_todo_status (mutating operations).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'in the current plan' implies this is the read-only counterpart to the todo mutation tools, but the description does not explicitly state when to use this tool over alternatives or mention exclusions. No direct alternative or when-not-to-use guidance is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

remove_todoA

Remove a todo item from the current plan

ParametersJSON Schema
NameRequiredDescriptionDefault
todoIdYesID of the todo item to remove

TDQS

A3.9/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must convey behavioral traits. The verb 'Remove' clearly signals a mutating operation, and no contradictory behavior is stated. However, it does not disclose whether the removal is permanent, any required prerequisites, or side effects on the plan.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, direct sentence with no redundancy. It is appropriately sized and front-loaded with the action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter mutation with no output schema or annotations, the description clearly states the action and scope. However, it omits details about return values, error conditions, or prerequisites, and the meaning of 'current plan' is left implicit. These gaps limit its completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema fully documents todoId, and the description adds the important context that removal occurs 'from the current plan', which hints that todoId must belong to an active plan. This contextualizes the parameter beyond its basic ID label.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses the specific verb 'Remove' with resource 'a todo item' and scope 'from the current plan', clearly distinguishing it from sibling tools like add_todo, get_todos, and update_todo_status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies a use case (removing an item) but provides no explicit guidance on when to use this tool over alternatives such as update_todo_status (which changes status) or explicit exclusions. Sibling tools exist but are not referenced.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

save_planC

Save the current implementation plan

ParametersJSON Schema
NameRequiredDescriptionDefault
planYesThe implementation plan text to save

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must disclose behavioral traits. It only says 'save' without indicating whether it overwrites an existing plan, persists to storage, requires an active planning session, or returns any confirmation. This omission leaves significant ambiguity for a write operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence that efficiently communicates the core action. No filler words or redundant information are present.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple, but the description omits important context such as prerequisites, side effects, and how it fits into the overall planning workflow. Given the lack of annotations and output schema, the description alone is insufficient for an agent to fully understand usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single 'plan' parameter, which already explains 'The implementation plan text to save'. The description adds no additional meaning beyond the schema, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Save') and the resource ('current implementation plan'), which distinguishes it from siblings like get_plan (retrieve) and add_todo. However, 'current' is somewhat ambiguous and does not explicitly clarify the scope relative to other planning tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, such as after start_planning or for saving a draft versus a finalized plan. No context or exclusions are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

start_planningB

Start a new planning session with a goal

ParametersJSON Schema
NameRequiredDescriptionDefault
goalYesThe software development goal to plan

TDQS

B3.4/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, and the description only states the action without disclosing behavioral traits such as whether it overwrites an existing session, requires a prerequisite, or has side effects. This leaves the agent without critical safety/state information.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no filler. Every word contributes to conveying the tool's purpose, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a session-initiating tool, the description lacks important context about what happens to an existing session, whether the operation is destructive, and how it relates to sibling tools like get_plan or save_plan. The absence of annotations makes this gap more significant.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already provides 100% coverage for the single parameter 'goal' with a clear description. The tool description adds no additional semantic detail beyond mentioning 'goal', so the baseline score of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Start a new planning session with a goal' uses a specific verb ('start') and resource ('planning session'), and clearly distinguishes from sibling tools like save_plan or update_goal, which imply saving or modifying rather than initiating.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'new planning session' implies usage when beginning a fresh session, but it does not explicitly state when to use versus alternatives or mention exclusions. There is no guidance about using update_goal for existing sessions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

update_todo_statusB

Update the completion status of a todo item

ParametersJSON Schema
NameRequiredDescriptionDefault
todoIdYesID of the todo item
isCompleteYesNew completion status

TDQS

B3.3/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It implies a mutating action but doesn't disclose side effects, error handling, permissions, or response behavior. For a write operation, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence that is front-loaded with the specific action. Every word earns its place, with no unnecessary detail or verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter update tool, the description is minimally adequate. However, it lacks usage context and behavioral details that would be helpful given the absence of annotations and output schema, leaving gaps around expected results and side effects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has complete descriptions for both parameters (todoId and isComplete), so the description adds no additional meaning beyond what the schema provides. Baseline 3 is appropriate given the 100% schema description coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it updates the completion status of a todo item, which is a specific action on a specific resource. This distinguishes it from sibling tools like add_todo/remove_todo and update_goal, which handle different aspects.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention that this should be used for toggling completion status rather than adding/removing todos or updating other goal properties.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 6 tool updates
    • First observedadd_todo
    • First observedget_todos
    • First observedremove_todo
    • First observedsave_plan
    • First observedstart_planning
    • First observedupdate_todo_status
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

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

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • Memory Bank MCP Server

    nicavcrm
    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
    52 npm
    2
    MIT

  • Software Planning Tool

    PhilippMT
    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
    12 npm
    MIT

Appeared in Searches