Divide And Conquer MCP Server

🚀 Divide and Conquer Multi-Step Control Protocol Server Usage Guide

This server is primarily used for the division and management of complex tasks. It allows agents to break down large tasks into multiple smaller ones and track progress across multiple conversations.

✨ Features

Core Features

1. Task Decomposition: Split large tasks into multiple subtasks for step-by-step completion.
2. Progress Tracking: Monitor the execution status of tasks across multiple conversations.
3. Context Maintenance: Preserve key information to prevent loss.
4. Organization Management: Arrange tasks in a logical order.
5. Documentation: Record decisions and resources.

Use Cases

1. Complex software development
2. Project planning and management
3. Research and analysis

📦 Installation

There is no installation content provided in the original document, so this section is skipped.

💻 Usage Examples

There is no usage example code provided in the original document, so this section is skipped.

📚 Documentation

JSON Data Structure

The following is the JSON format for storing task information:

{
  "task_description": "A moderately detailed description of the entire task. The ultimate goal we aim to achieve.",
  
  "checklist": [
    {
      "done": false,
      "task": "A short and comprehensive name for the task",
      "detailed_description": "A longer description of the task's goal",
      "context_and_plan": "Related files, background information, and detailed plans. Usually the longest part of the text."
    }
  ],
  
  "context_for_all_tasks": "Information that all tasks in the checklist should include.",
  
  "metadata": {
    "created_at": "ISO timestamp",
    "updated_at": "ISO timestamp",
    "progress": {
      "completed": 0,
      "total": 1,
      "percentage": 0
    },
    "tags": ["tag1", "tag2"],
    "priority": "high|medium|low",
    "estimated_completion_time": "ISO timestamp or duration"
  },
  
  "notes": [
    {
      "timestamp": "ISO timestamp",
      "content": "Additional notes about the overall task"
    }
  ],
  
  "resources": [
    {
      "name": "Resource name",
      "url": "URL or file path",
      "description": "Resource description"
    }
  ]
}

Configuration Storage Location

By default, the server stores task data in the following locations:

• macOS/Linux: ~/.mcp_config/divide_and_conquer.json (The actual path is /Users/username/.mcp_config/divide_and_conquer.json)
• Windows: C:\Users\username\.mcp_config\divide_and_conquer.json

Handling Situations

1. File does not exist during reading: Return an empty task structure and create the file.
2. Directory does not exist: Automatically create the directory structure when writing.
3. File is corrupted or inaccessible: Return an error message.

🔧 Technical Details

There is no technical details content provided in the original document, so this section is skipped.

🤝 Contribution Guidelines

Contributions are welcome! Please feel free to submit pull requests.

📄 License

This project is licensed under the MIT License - see the LICENSE file for details.