Task Manager MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATA_DIR | No | Data storage directory | ./data |
| NODE_ENV | No | Node environment | development |
| LOG_LEVEL | No | Log level | info |
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 |
|---|---|
| create_taskC | Create a new task |
| list_tasksC | List tasks with optional filters |
| update_taskC | Update an existing task |
| delete_taskC | Delete a task by ID |
| complete_taskC | Mark a task as completed |
| search_tasksC | Search tasks by title or description |
| get_task_statsC | Get statistics about all tasks |
| clear_completedB | Remove all completed tasks |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| All Tasks (JSON) | Get all tasks in JSON format |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose with no ambiguity. For example, create_task, update_task, delete_task, and complete_task handle different lifecycle actions, while list_tasks, search_tasks, and get_task_stats serve distinct querying functions. The clear separation prevents misselection.
All tool names follow a consistent verb_noun pattern using snake_case, such as create_task, update_task, and list_tasks. This uniformity makes the tool set predictable and easy to understand, with no deviations in naming conventions.
With 8 tools, the server is well-scoped for task management, covering essential operations like CRUD, querying, and statistics. Each tool earns its place without feeling excessive or insufficient for the domain.
The tool surface provides complete coverage for task management, including create, read (list/search), update, delete, and lifecycle actions (complete/clear). There are no obvious gaps, ensuring agents can handle full workflows without dead ends.