Task Manager MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_taskA | Add a new task to the to-do list |
| list_tasksA | List all tasks, optionally filtered by completion status |
| complete_taskB | Mark a task as complete by its ID |
| delete_taskB | Delete a task by its ID |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| tasks | The full current to-do list as JSON |
TDQS
Scored across 4 tools
Each tool targets a distinct action on tasks: add, list, complete, or delete. No overlap in purpose, and the descriptions are clear.
All tools follow the consistent 'verb_task' pattern with snake_case, making the API predictable and easy to navigate.
Four tools cover the essential task management operations without unnecessary bloat, perfectly scoped for a focused utility.
Provides CRUD operations for tasks except for update. Missing generic update functionality (e.g., edit description) but the core workflow is complete.