MCP Tools
Task management operations are declared as Model Context Protocol (MCP) tools in tasksAgent/mcp-config.json and executed through tasksAgent/tools/tasks_tool.sh.
Tool Groups
| Group | Tools | Purpose |
|---|---|---|
| Configuration and discovery | task_config, task_list, task_history_list |
Read task config and list task/history records with filters. |
| Task read/write operations | task_get, task_create, task_update, task_delete |
Manage individual task records in backlog files. |
| Ordering control | task_reorder |
Apply explicit task ordering by id list. |
Common Input Rules
repoPath is required and must resolve to an existing absolute directory. backlogPath must be absolute, must stay inside repoPath, and must end in .backlog, while history listing applies parallel .history constraints. The file content is Markdown, not JSON, and each task keeps a persisted task id.
Execution Characteristics
Each call is process-isolated and envelope-normalized before execution. Backlog and history content are parsed directly from Markdown on disk, and failures always return explicit JSON payloads instead of silent success states.