MCP Task Management Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_TASK_USE_SQLITE | No | Set to 'false' to use legacy JSON storage instead of SQLite. | true |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_taskA | Create a new task with optional group, status, and metadata. AI should use this to track user requests and break down complex work into manageable tasks. |
| update_taskA | Update an existing task. Use this to change status, add progress notes, update estimates, etc. Status changes are automatically tracked with timestamps. |
| get_taskA | Get detailed information about a specific task including its history, references, and metadata. |
| list_tasksB | List tasks with optional filtering. AI should use this to understand current workload, find related tasks, and provide context-aware assistance. |
| delete_taskA | Delete a task and remove all references to it from other tasks. |
| create_groupA | Create a new task group for organizing related tasks (e.g., projects, areas, etc.). |
| list_groupsA | List all task groups with their metadata. |
| delete_groupA | Delete a group. Tasks in the group will be ungrouped but not deleted. |
| create_statusB | Create a custom task status with optional color and description. |
| list_statusesA | List all available task statuses. |
| delete_statusA | Delete a custom status. Cannot delete default status or statuses in use. |
| add_task_referenceA | Create a reference between two tasks (blocks, blocked-by, relates-to, etc.). Use this to model task dependencies and relationships. |
| remove_task_referenceB | Remove a reference between two tasks. |
| get_task_referencesA | Get all incoming and outgoing references for a task to understand dependencies. |
| bulk_create_tasksA | Create multiple tasks at once with shared properties. Ideal for breaking down large projects or importing task lists. |
| bulk_update_tasksA | Update multiple tasks simultaneously with the same changes. Useful for batch operations like changing assignees or priorities. |
| bulk_change_statusA | Change the status of multiple tasks at once with optional note. Perfect for workflow transitions. |
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 17 tools
Each tool targets a distinct resource and action: tasks, groups, statuses, references, and bulk operations are clearly separated. No two tools overlap in purpose, and the singular vs. bulk distinction is explicit.
All tools use a consistent verb_noun pattern in snake_case, with 'bulk_' prefixed for batch operations. This makes the tool set highly predictable and easy to navigate.
With 17 tools, the server covers tasks, groups, statuses, references, and bulk operations comprehensively. While slightly above the ideal 10-15 range, the count is justified by the broad domain and no tools seem redundant.
The task lifecycle (CRUD), references, and bulk operations are fully covered. Minor gaps include missing update operations for groups and statuses (e.g., rename group, change status metadata), but these can be worked around.