MCP Tasks
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tasks_setupA | Initializes an source file from a path
|
| tasks_searchB | Search tasks from specific statuses with optional text & ID filtering |
| tasks_addB | Add new tasks with a specific status. It's faster and cheaper if you use this in batch. User can add atomically while AI works using the CLI add tool |
| tasks_updateA | Update tasks in bulk by ID to a different status. Returns complete summary no need to call tasks_summary afterwards. Prevents AI accidentally rename or deleting tasks during mass updates, not even possible |
| tasks_summaryA | Get per-status task counts and the WIP task(s). Redundant right after tasks_add/tasks_update |
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
Most tools have distinct purposes: add, search, update, and summary are clearly differentiated. However, tasks_setup is ambiguous—it initializes a source file but overlaps conceptually with tasks_add for task creation, which could cause confusion about when to use each. The descriptions help but don't fully resolve this overlap.
All tool names follow a consistent 'tasks_' prefix with a verb suffix pattern (add, search, setup, summary, update). This uniformity makes the tool set predictable and easy to navigate, with no deviations in naming style.
With 5 tools, this server is well-scoped for task management. Each tool serves a specific function (adding, searching, updating, summarizing, and setup), and the count is appropriate for covering core operations without being overwhelming or insufficient.
The tool set covers basic CRUD-like operations (add, update, search, summary) but has notable gaps. There is no tool for deleting tasks, which limits lifecycle coverage. Additionally, tasks_setup's role is unclear—it initializes files but doesn't integrate cleanly with other task operations, creating potential dead ends in workflows.