add_checklist_item
Adds a new item to the checklist.
LABSCO SUMMARY
The plan lives outside the context window, so the next step survives a conversation that does not.
get_current_task_details is what the rest is arranged around: it returns the first uncompleted item together with the context shared by every item, which is what lets a fresh session pick the work up without re-reading a whole thread. Each item carries a detailed description and its own context and plan, so a checklist entry is a briefing rather than a line of text. Only one task is held at a time, and clearing it is how the next one begins.
What it is
A single-task workspace holding a description, context that applies to every item, an ordered checklist, notes, resources and metadata.
What you get
- A task initialised with a description, context for all its items, and an optional starting checklist.
- Checklist items added at a position, updated, marked done or undone, removed and reordered, each carrying its own detailed description and its own context and plan.
- Notes, and resources recorded with a name, URL and description.
- Metadata: priority, tags and an estimated completion time.
- A checklist summary with completion status, and the current item — the first uncompleted one — returned with its full context.
- The whole task cleared when the work is finished.
Requirements
Nothing — no account, no key.
Setup effort
One command — npx -y @landicefu/divide-and-conquer-mcp-server
USE CASES
01
Handing a long job to a session that will not remember how it started
The shared context and the current item come back together, so resuming does not depend on the earlier conversation still being in the window.
02
Keeping a plan honest as the work changes it
Items are added at a position, rewritten in place and reordered, so the checklist tracks reality instead of the original guess.
03
Recording what you found out partway through
Notes and links attach to the task rather than to a message, which is what makes them survive into the next session.
15 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
add_note
Adds a note to the task.
add_resource
Adds a resource to the task.
clear_task
Clears the current task data.
get_checklist_summary
Returns a summary of the checklist with completion status.
get_current_task_details
Retrieves details of the current task (first uncompleted task) with full context. This is the recommended tool to use when working with tasks.
initialize_task
Creates a new task with the specified description and optional initial checklist items.
mark_task_done
Marks a checklist item as done.
mark_task_undone
Marks a checklist item as not done.
remove_checklist_item
Removes a checklist item.
reorder_checklist_item
Moves a checklist item to a new position.
update_checklist_item
Updates an existing checklist item.
update_context
Updates the context information for all tasks.
update_metadata
Updates the task metadata.
update_task_description
Updates the main task description.
BEFORE YOU INSTALL
What to know first
Tools you get
15 tools when we connected.
Requires
npx on PATH
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 15 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
Build from source
Clone the repository
TERMINAL
git clone https://github.com/landicefu/divide-and-conquer-mcp-server.git
cd divide-and-conquer-mcp-serverInstall dependencies
TERMINAL
npm installBuild the server
TERMINAL
npm run buildnpx
TERMINAL
npx -y @landicefu/divide-and-conquer-mcp-serverMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"divide-and-conquer": {
"command": "npx",
"args": [
"-y",
"@landicefu/divide-and-conquer-mcp-server"
],
"disabled": false
}
}
}
