task-manager-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TASK_MANAGER_DB_PATH | No | Path to the SQLite database file used by the Task Manager MCP Server. Default location varies by OS: Windows `%APPDATA%/task-manager/taskmanager.db`, macOS `~/Library/Application Support/task-manager/taskmanager.db`. Must point to a database file that has already been initialized by the Electron app (this server does not create tables). |
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 |
|---|---|
| task_listA | 获取任务列表。支持按状态、项目ID、标签ID、关键词筛选。不传参数则返回所有任务。 |
| task_getB | 获取指定任务的详细信息，包含标签和项目信息 |
| task_addB | 添加一个新任务。标题为必填，其他字段可选。tag_ids 用于关联标签。 |
| task_updateA | 更新任务信息。只需传入要修改的字段。tag_ids 传入新列表会覆盖原有标签。 |
| task_change_statusC | 变更任务状态。可选状态: not_started(未开始), paused(暂停), in_progress(进行中), completed(完成), archived(归档) |
| task_deleteA | 删除指定任务（不可恢复） |
| tag_listA | 获取所有标签列表 |
| tag_createA | 创建新标签。name 必填，color 可选（hex 颜色值，默认 #6366f1） |
| tag_deleteA | 删除指定标签（不会删除已关联的任务） |
| category_listA | 获取所有分类列表，每个分类包含其下的项目列表 |
| category_createC | 创建新分类 |
| category_deleteA | 删除指定分类（会级联删除其下所有项目，但不会删除任务） |
| project_listA | 获取项目列表。可选按分类ID、名称关键词筛选，不传则返回所有项目。 |
| project_createB | 创建新项目，需要指定所属分类ID |
| project_deleteA | 删除指定项目（项目下的任务不会被删除，但会失去项目关联） |
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 15 tools
Tools are clearly separated by resource (task, project, category, tag). The only potential confusion is task_update and task_change_status, since status could be considered a task field, and category_list versus project_list when retrieving projects with category context. Descriptions help disambiguate, but there is minor overlap.
Most tools follow a consistent entity_action pattern (category_create, project_delete, tag_list). However, task_add deviates from the create convention used elsewhere, and task_change_status is a multi-word verb unlike the simple single-action names.
15 tools for a task manager with tasks, projects, categories, and tags is well-scoped. Each tool covers a distinct need and none feel redundant or unnecessary.
Tasks have full lifecycle coverage (create/read/update/delete/status), but categories, projects, and tags lack update operations entirely. There is no way to rename a project or recolor a tag without delete/recreate, which is a notable gap in the resource management surface.