Task Queue MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TASK_QUEUE_URL | Yes | Your Task Queue address, e.g. https://tasks.example.com (the API path is added for you). | |
| TASK_QUEUE_API_KEY | Yes | Your personal Task Queue API key (tqk_...). Generate one in Task Queue under Profile → API keys. | |
| TASK_QUEUE_CATEGORY | No | Optional category value that create_task uses when none is given. | |
| TASK_QUEUE_WORKSPACE | No | Optional workspace id, used when you belong to several workspaces. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Task Queue: the person’s tasks, as their own personal API key sees them. Name tasks by number (e.g. TASK-000123). Moves follow the board: move_task to a column by name. Only delete, assign or move other people’s tasks when the person asks.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_my_tasksA | The tasks assigned to you, across your workspaces, with each workspace and its category and priority values (needed to create a task). active: queued, in progress or on hold; done: completed or cancelled. A task with reassigned set reached you from someone else’s queue: read it with get_task, comments included, before you work on it. |
| get_taskA | A task with its description, notes (comments), files, parent and subtasks, and how_to_update: the rules for changing it in its current state. reassigned is set when it reached its assignee from someone else’s queue: then read its comments before working on it, since they say what was done and found before the hand-off. Finds any task you may see by its number (pool tasks too, with View all tasks). |
| create_taskA | A new task in your own queue (needs Take tasks or Create tasks). category and priority are values (e.g. BUG, HIGH), listed per workspace by list_my_tasks. With start: true it starts at once, which needs an estimate. |
| start_taskA | Starts a queued task (or corrects the start time of one already started). A task without an estimate needs estimate_minutes. A reassigned task: read its comments (get_task) first. |
| complete_taskA | Completes a task in progress (a paused one is resumed first). A task blocked for a reason must be resumed in Task Queue. |
| add_commentC | Adds a note to a task’s conversation. |
| attach_filesB | Attaches files from this computer to a task, with an optional note. |
| pause_taskA | Pauses a task in progress so its worked time stops while nobody works on it (no reason needed). |
| resume_taskA | Resumes a paused task. A task blocked for a reason is resumed with move_task to In Progress. |
| move_taskA | Moves a task to a board column by name, as dragging it on the board does: In Queue, In Progress (starts or resumes it), Blocked (needs reason), Done (completes it; reason is the completion note), or one of its project board’s own columns. It also moves back a step: from In Progress, Blocked or a later column to In Queue (back in the assignee’s queue, not started; the time worked so far stays), or to the pool (needs reason, and Return any task for work in progress). An unknown column lists the board’s columns. With folder, files it in another project (needs Manage projects). Reopening is done in Task Queue. |
| assign_taskA | Assigns a task to a member of its workspace by email, to you ("me"), or back to the Task Pool ("none"). Needs Assign tasks, except handing back your own task. |
| update_taskA | Changes a task’s details (needs Edit tasks), or gives your estimate as its assignee (once). Send only what changes; null clears description, acceptance criteria and dates. |
| delete_taskA | Deletes a task with its notes and files. It can’t be undone. Needs Delete tasks. Only when the person asks for it. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Most tools have distinct verbs (add_comment, attach_files, assign_task, delete_task), but move_task overlaps heavily with start_task, resume_task, pause_task, and complete_task since it can start, resume, block, and complete tasks itself. The descriptions acknowledge the overlap but an agent still faces a real choice between a dedicated transition tool and the equivalent board move.
All 13 tools follow a consistent verb_noun snake_case pattern (create_task, get_task, update_task, delete_task, start_task, pause_task, resume_task, move_task, assign_task). The only variation is the 'my' qualifier in list_my_tasks, which is still readable and within convention.
13 tools is well within the ideal 3-15 range and each tool maps to a genuine task-queue operation: CRUD, state transitions, assignment, comments, and attachments. No tool feels redundant in count terms.
Core lifecycle is covered: create/get/update/delete, start/pause/resume/complete, move between columns, assign, comment, and attach files. Gaps are minor but real: no comment editing/deletion, no file listing or removal, no search, and reopening a task is explicitly punted to the UI ('Reopening is done in Task Queue').