planner

The Task Planner MCP Server provides a set of tools to create, manage, and monitor hierarchical tasks and subtasks. It helps AI assistants break down complex goals into actionable steps, track progress, and keep a structured task list with priorities. You can create tasks, break them into subtasks, list tasks and their relationships, update details, mark tasks as complete, and delete tasks along with their subtasks. The server exposes tools such as create-task, list-tasks, get-task, update-task, delete-task, complete-task, and break-down-task, each designed to be invoked via MCP protocol requests with the appropriate parameters. This enables seamless task management within AI workflows and conversational agents like Claude Desktop or other MCP-enabled clients.

Prerequisites:

• Node.js (recommended LTS)
• pnpm or npm installed on your system
• Git (for cloning the repository)

Installation steps:

1. Clone the repository: git clone https://github.com/yourusername/task-planner-mcp.git cd task-planner-mcp

2. Install dependencies (pnpm): pnpm install

3. Build the project: pnpm run build

4. Start the MCP server: pnpm start

Note: If you prefer npm, adapt the commands accordingly (npm install, npm run build, npm start) unless the project explicitly relies on pnpm workspaces or pnpm-specific scripts.

Helpful tips:

• Ensure the absolute path to your built server file is correctly configured in clients (e.g., Claude Desktop) as /absolute/path/to/task-planner-mcp/dist/index.js.
• The data model stores tasks in a local JSON file (tasks.json) in the project root; ensure the server has write permissions to this file path.
• Supported priorities: low, medium, high. Use them consistently to avoid confusion in task lists.
• When using break-down-task, you can specify a parentId to link subtasks to a parent task.
• If you encounter issues starting the server, verify that your Node environment matches the required version and that build artifacts exist in dist/index.js.
• If you deploy in a container or cloud environment, map volumes for persistent storage of tasks.json and ensure the working directory aligns with the server’s expectations.