Tasks Organizer

🚀 MCP Tasks Organizer

An MCP server that transforms Cursor agent plans into structured Markdown task lists and organizes them in your repository. This server helps you track AI-generated plans and suggestions as actionable specifications.

✨ Features

• Automatically extract tasks from Cursor agent plans.
• Create a .tasks folder in the repository for task management.
• Use descriptive file names (e.g., "refactor-authentication.md") for easy identification.
• Automatically mark completed task lists with the ✅ prefix.
• Format plans in the correct Markdown structure.
• Organize content into overviews, implementation details, and next steps.
• Integrate with Claude for Desktop and other MCP clients.

📦 Installation

Prerequisites

• Python 3.10 or higher.
• pip or other Python package managers.

Quick Installation

For Unix-based systems (macOS, Linux):

# Clone the repository
git clone https://github.com/yourusername/mcp-tasks-organizer.git
cd mcp-tasks-organizer

# Run the installation script
./install.sh

For Windows:

# Clone the repository
git clone https://github.com/yourusername/mcp-tasks-organizer.git
cd mcp-tasks-organizer

# Run the installation script
.install.bat

Manual Installation

1. Clone the repository:

   git clone https://github.com/yourusername/mcp-tasks-organizer.git
   cd mcp-tasks-organizer
   

2. Create and activate a virtual environment (optional but recommended):
   • For macOS/Linux:

     python -m venv venv
     source venv/bin/activate
     

   • For Windows:

     python -m venv venv
     .\venv\Scripts\activate
     

3. Install dependencies:

   pip install -r requirements.txt
   

4. Run the server:

   python app.py
   

💻 Usage Examples

Tool List

1. convert_plan_to_tasks: Convert plan text into a task list.
2. mark_task_complete: Mark a specific task in the task list as completed.
3. check_all_tasks_complete: Check if all tasks in the task list are completed.
4. list_task_files: List all task files in the .tasks directory.

Example Workflow

1. The agent proposes changes to your authentication system.
2. Convert this plan into a task list: convert_plan_to_tasks(plan_text, "Auth System Refactor", "auth-refactor").
3. The tasks are saved to .tasks/auth-refactor.md.
4. After completing the tasks, mark them: mark_task_complete("auth-refactor", 1).
5. After all tasks are completed: check_all_tasks_complete("auth-refactor").
6. The file is renamed to .tasks/✅auth-refactor.md.

🔧 Technical Details

1. The server creates a .tasks folder in the root directory of the repository.
2. Task lists are stored using file names based on 2 - 3 word descriptions.
3. When all tasks in a task list are completed, the file is renamed with a ✅ prefix.
4. The server parses tasks from the Cursor agent's input text.
5. Multiple pattern - matching techniques are used to extract tasks:
   • Numbered steps (1. First step).
   • List items (* Item one).
   • Sentences similar to "should", "must", "need".
6. If no clear tasks are found, the content is organized into logical sections.
7. The results can track and update task progress.

📄 License

MIT