Overview
What is Taskqueue?
Taskqueue is a Model Context Protocol (MCP) server for AI task management. It helps AI assistants handle multi-step tasks in a structured way, with user approval checkpoints. It is designed for use with MCP clients like Claude Desktop or Cursor.
How to use Taskqueue?
Configure the tool in your MCP client using the command npx -y taskqueue-mcp. Optionally set the TASK_MANAGER_FILE_PATH environment variable to specify a custom storage location. Use the CLI utility (npx task-manager-cli --help) for task approval and listing.
Key features of Taskqueue
- Task planning with multiple steps
- Progress tracking through task statuses
- User approval of completed tasks
- Project completion approval
- Task details visualization
- CLI for task inspection and management
- Enforced status transition rules
Use cases of Taskqueue
- AI assistant managing a multi-step project (e.g., website creation)
- Structured task breakdown with human-in-the-loop approval
- Tracking and documenting completion of subtasks
- Project finalization after all tasks are approved
FAQ from Taskqueue
What runtime does Taskqueue require?
Taskqueue requires Node.js to run. It is executed via npx, which downloads and runs the taskqueue-mcp package.
Where does Taskqueue store its data?
Data is stored in a JSON file in a platform-specific default location: ~/.local/share/taskqueue-mcp/tasks.json (Linux), ~/Library/Application Support/taskqueue-mcp/tasks.json (macOS), or %APPDATA%\taskqueue-mcp\tasks.json (Windows). A custom path can be set via the TASK_MANAGER_FILE_PATH environment variable.
What are the valid task status transitions?
Tasks follow a workflow: not started → in progress → done. You can move back from in progress to not started, and from done to in progress if additional work is needed. Approved tasks cannot be modified.
How does user approval work?
Task approval is controlled exclusively by the human user through the CLI command npm run approve-task -- <projectId> <taskId>. Tasks must be marked as "done" with completed details before they can be approved (unless using the --force option).
What authentication or transport does Taskqueue use?
The README does not specify authentication or transport details. It uses the standard MCP protocol over stdio (implied by the client configuration). No authentication mechanism is mentioned.
