tasks-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TASKS_MCP_DB | No | SQLite database path (parent dir is created) | ~/.local/share/tasks-mcp/tasks.db |
| TASKS_MCP_TRANSITIONS | No | Transition policy. `free` = any column to any column. Hook for a future `linear` policy. | free |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_taskA | Add a new task to the board. It lands in the 'backlog' column. |
| list_tasksB | List tasks, optionally filtered. All filters combine with AND. |
| get_taskA | Get the full detail of one task by its numeric id. Works for archived tasks too. |
| edit_taskA | Edit a task's title, description, priority, and/or tags. Only the fields you pass are changed; omitted fields keep their current value. Pass an empty string for description to clear it. Passing tags replaces the whole tag list. To change a task's column, use move_task instead. Returns the updated task. |
| move_taskB | Move a task to another kanban column. |
| archive_taskA | Archive a task (soft delete): it disappears from listings and the board but stays in the database. There is no hard delete. Returns the archived task. |
| get_boardA | Get the whole kanban board: unarchived tasks grouped by column. Always returns all four columns in board order — backlog, in_progress, testing, done — even when empty: Use this to render or summarize the board. |
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 7 tools
Each tool has a distinct purpose: adding, archiving, editing, viewing board/getting task/list filtering, and moving. No overlap in functionality.
All tool names follow the verb_noun pattern using snake_case, e.g., add_task, archive_task, move_task. Completely consistent.
Seven tools is well-suited for a kanban task management server, covering all essential operations without being excessive or insufficient.
Core CRUD and board viewing are present. Missing an unarchive tool for soft-deleted tasks, otherwise the surface is complete for basic kanban usage.