Skip to directory

Chain of Thought Task Manager

liorfranko

stdio15+ documented tools3

About Chain of Thought Task Manager

Task management system that converts natural language into organized development tasks with dependency tracking, implementation guides, and verification criteria through structured reasoning phases.

What you can use it for

  • productivity
Connection and setup
Hosting
Local stdio process
Transport
stdio
Endpoint
Local process; no hosted endpoint documented
Authentication
No credentials were configured; the tested read-only tool “list_tasks” succeeded in an isolated environment. Other tools may have additional requirements.

Requirements

  • Node.js 18+
  • The npm package repository matched the repository linked from the public profile.

Setup steps

  1. npx -y mcp-chain-of-thought@1.0.1
Tools 15+

README lists twelve tool names while catalog has fifteen rows; do not mark complete until reconciling individual tool rows and package version.

  • plan_task

    Initialize and detail the task flow, establish clear goals and success criteria, optionally reference existing tasks for continuation planning

    Parameters: description, requirements, existingTasksReference
    01
  • analyze_task

    Deeply analyze task requirements and systematically check the codebase, evaluate technical feasibility and potential risks. If code is needed, use pseudocode format providing only high-level logic flow and key steps, avoiding complete code.

    Parameters: summary, initialConcept, previousAnalysis
    02
  • reflect_task

    Critically review analysis results, evaluate solution completeness and identify optimization opportunities, ensuring the solution aligns with best practices. If code is needed, use pseudocode format providing only high-level logic flow and key steps, avoiding complete code.

    Parameters: summary, analysis
    03
  • split_tasks

    Decompose complex tasks into independent subtasks, establishing dependencies and priorities. ## updateMode - **append**: Keep existing tasks and add new ones - **overwrite**: Delete unfinished tasks, keep completed ones - **selective**: Intelligently match and update existing tasks based on name - **clearAllTasks**: Clear all tasks and create a backup (preferred mode) ## Key Requirements - **Provide concise pseudocode**: Only provide high-level logic flow and key steps, avoid complete code - **Consolidate when necessary**: Simple modifications can be integrated with other tasks to avoid excessive task count - **Submit in batches**: If there are too many tasks, use the "split_tasks" tool with parameters not exceeding 5000 characters

    Parameters: updateMode, tasks, globalAnalysisResult
    04
  • list_tasks

    Generate a structured task list, including complete status tracking, priority, and dependencies

    Parameters: status
    05
  • execute_task

    Execute a specific task according to the predefined plan, ensuring the output of each step meets quality standards

    Parameters: taskId
    06
  • verify_task

    Comprehensively verify task completion, ensuring all requirements and technical standards are met without missing details

    Parameters: taskId
    07
  • complete_task

    Formally mark a task as completed, generate a detailed completion report, and update the dependency status of related tasks

    Parameters: taskId, summary
    08
  • delete_task

    Delete unfinished tasks, but does not allow deleting completed tasks, ensuring the integrity of system records

    Parameters: taskId
    09
  • clear_all_tasks

    Clear unfinished tasks and reset the task list

    Parameters: confirm
    10
  • update_task

    Update task content, including name, description and notes, dependent tasks, related files, implementation guide and verification criteria. Completed tasks only allow updating summary and related files

    Parameters: taskId, name, description, notes, dependencies, relatedFiles, implementationGuide, verificationCriteria
    11
  • query_task

    Search tasks by keyword or ID, displaying abbreviated task information

    Parameters: query, isId, page, pageSize
    12
  • get_task_detail

    Get the complete detailed information of a task based on its ID, including unabridged implementation guides and verification criteria, etc.

    Parameters: taskId
    13
  • process_thought

    Engage in a flexible and evolving thinking process by creating, questioning, validating, and refining ideas to progressively deepen understanding and generate effective solutions. When needing to gather data, analyze, or research, prioritize reviewing relevant project code; if such code doesn't exist, search the web rather than speculating. Set nextThoughtNeeded to false when thinking is sufficient, otherwise adjust total_thoughts to extend the process

    Parameters: thought, thought_number, total_thoughts, next_thought_needed, stage, tags, axioms_used, assumptions_challenged
    14
  • init_project_rules

    Initialize project rules. Call this tool when the user requests to generate or initialize the project specification file, or if the user requests to change or update the project specification.

    15

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

Limitations and notes
  • Runtime verification covered one read-only tool call (list_tasks); other listed tools were not individually exercised.
Original sources
  • MCP.Directory public profile

    Name, description, publisher identifier, categories, transport, tool inventory, and install configuration.

  • Linked publisher repository

    Repository URL linked from the public profile; npm package repository metadata matched this GitHub repository.

  • npm registry metadata

    Published package version 1.0.1 checked before launch. Registry repository: git+https://github.com/liorfranko/mcp-chain-of-thought.git.

  • maintainer repository documentation

    Maintainer README names 12 tools in planning, task management, execution and thought processing; catalog currently stores 15 rows, so count discrepancy remains unresolved.

Documentation checked 2026-10-28T00:00:00Z. Connection has not been runtime tested.