task-manager-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TASK_MANAGER_ROOT | No | Root directory for task storage. If not set, defaults to ~/task-manager. | ~/task-manager |
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 |
|---|---|
| init_projectC | Initialize a new project with task management structure |
| create_taskC | Create a new task in a project |
| get_taskC | Get full details of a specific task |
| list_tasksC | List all tasks in a project |
| update_taskC | Update an existing task |
| complete_taskA | Mark a task as completed and move it to completed directory |
| list_projectsA | List all available projects |
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 maps to a distinct resource/action pair: project setup, task CRUD, and task completion. complete_task is a specific state transition rather than a duplicate of update_task, so there is no real ambiguity.
All tools follow a consistent verb_noun snake_case pattern, such as create_task, get_task, list_tasks, and init_project. The list_* prefix consistently indicates collection queries, making the set predictable.
Seven tools is a well-scoped size for a task manager. Each tool serves a clear purpose without redundancy or bloat.
The core task lifecycle is covered: create, read, list, update, and complete, plus project initialization and listing. Missing delete operations and deeper project management are gaps, but agents can still complete typical task management workflows.