Local 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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_task | Create a new task and return the saved task. |
| list_tasksA | List tasks, optionally filtered by completion status. |
| complete_taskB | Mark a task as completed and return the updated task. |
| delete_taskA | Delete a task by ID and return the deleted task. |
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 3 tools
Each tool has a distinct purpose: listing tasks, marking as completed, and deleting. No overlap in functionality.
All tools follow a consistent verb_noun pattern using snake_case: list_tasks, complete_task, delete_task.
Three tools is a reasonable minimal set for a simple task manager, though it could be slightly expanded.
Missing essential operations like create_task and update_task, leaving a significant gap that prevents full task lifecycle management.