taskqueue-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TASK_MANAGER_FILE_PATH | No | Custom path to the tasks.json file. If not provided, defaults to platform-specific locations (Linux: ~/.local/share/taskqueue-mcp/tasks.json, macOS: ~/Library/Application Support/taskqueue-mcp/tasks.json, Windows: %APPDATA%\taskqueue-mcp\tasks.json) |
Schema
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projects | List all projects in the system and their basic information (ID, initial prompt, task counts), optionally filtered by state (open, pending_approval, completed, all). |
| read_project | Read all information for a given project, by its ID, including its tasks' statuses. |
| create_project | Create a new project with an initial prompt and a list of tasks. This is typically the first step in any workflow. |
| delete_project | Delete a project and all its associated tasks. |
| add_tasks_to_project | Add new tasks to an existing project. |
| finalize_project | Mark a project as complete. Can only be called when all tasks are both done and approved. This is typically the last step in a project workflow. |
| list_tasks | List all tasks, optionally filtered by project ID and/or state (open, pending_approval, completed, all). Tasks may include tool and rule recommendations to guide their completion. |
| read_task | Get details of a specific task by its ID. The task may include toolRecommendations and ruleRecommendations fields that should be used to guide task completion. |
| create_task | Create a new task within an existing project. You can optionally include tool and rule recommendations to guide task completion. |
| update_task | Modify a task's properties. Note: (1) completedDetails are required when setting status to 'done', (2) approved tasks cannot be modified, (3) status must follow valid transitions: not started → in progress → done. You can also update tool and rule recommendations to guide task completion. |
| delete_task | Remove a task from a project. |
| approve_task | Approve a completed task. Tasks must be marked as 'done' with completedDetails before approval. Note: This is a CLI-only operation that requires human intervention. |
| get_next_task | Get the next task to be done in a project. Returns the first non-approved task in sequence, regardless of status. The task may include toolRecommendations and ruleRecommendations fields that should be used to guide task completion. |