Task Manager MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SINGLE_AGENT | No | Enable single agent mode where the server tracks which task is currently in progress. Do not enable if multiple agents will use the server simultaneously. | false |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_taskA | Creates a new task that must be executed. If decomposing a complex task is required, must use 'decompose_task' first before executing it. All tasks start in the todo status. Must use 'update_task' before executing this task, and when executing this task has finished. |
| decompose_taskA | Decomposes an existing complex task into smaller, more manageable subtasks. All tasks with complexity higher than low must always be decomposed before execution. Tasks MUST be in todo status to be decomposed. Subtasks with the same sequence order may be executed in parallel. Subtasks should include a verification subtask. Created subtasks may be decomposed later if needed. |
| update_taskA | Updates the status and/or other properties of one or more tasks. Must use this tool before executing tasks, and when finished executing tasks. Should always include lessons learned to inform future tasks. Important: Always update multiple tasks in a single call if dependencies allow it. |
| task_infoC | Returns full details for requested tasks |
| current_taskB | Returns a list of tasks that are currently in progress. |
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 5 tools
Each tool has a distinct, non-overlapping purpose: create_task for creation, current_task for listing in-progress tasks, decompose_task for breaking down complex tasks, task_info for retrieving details, and update_task for modifying task properties. The descriptions clearly differentiate their roles, with no ambiguity about when to use each tool.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., create_task, decompose_task, update_task). The naming is predictable and uniform across all five tools, making it easy for an agent to understand and select the appropriate tool.
With 5 tools, this server is well-scoped for a task management domain. The count is appropriate, covering core operations without being overwhelming or too sparse, and each tool serves a clear, necessary function in the workflow.
The tool set provides strong coverage for task management, including creation, decomposition, status updates, and information retrieval. A minor gap exists in the lack of a delete or archive tool for task lifecycle management, but agents can work around this by using update_task to mark tasks as completed or obsolete.