Mini Task 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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_taskC | Add a new task to the local task manager. |
| list_tasksC | List all tasks or filter them by pending or completed status. |
| get_taskB | Get the complete details of one task using its task ID. |
| update_taskA | Update the title or description of an existing task using its task ID. |
| complete_taskC | Mark an existing task as completed. |
| delete_taskB | Delete an existing task using its task ID. |
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 6 tools
Each tool has a unique action (add, complete, delete, get, list, update) with no overlap, making selection unambiguous.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., add_task, complete_task), adhering perfectly to the convention.
With 6 tools covering core task operations (CRUD + status), the count is well-scoped for a local task manager.
Covers the full lifecycle except for a 'reopen' or 'set pending' operation; update_task only modifies title/description, not status, which is a minor gap.