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 |
|---|---|
| create_taskB | Create a new task |
| list_tasksB | List all tasks with optional filtering |
| get_taskC | Get a specific task by ID |
| update_taskB | Update an existing task |
| delete_taskC | Delete a task |
| complete_taskC | Mark a task as completed |
| get_task_summaryB | Get summary statistics for all tasks |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| daily_planning | Create a daily planning prompt with current task context Args: focus_area: What to focus on today (e.g., "development", "meetings", "research") |
| task_breakdown | Create a conversation for breaking down a complex task Args: task_title: The task that needs to be broken down complexity: Task complexity level (simple, medium, complex) |
| weekly_review | Generate a weekly review prompt with task statistics |
| project_planning | Create a project planning prompt Args: project_name: Name of the project to plan deadline: Project deadline (YYYY-MM-DD format) team_size: Number of people on the team |
| task_prioritization | Create a prompt for task prioritization using current tasks |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| all_tasks | Get all tasks as a formatted list |
| task_summary | Get formatted task summary statistics |
| overdue_tasks | Get all overdue tasks |
TDQS
Scored across 7 tools
Most tools have clearly distinct purposes (create, list, get, update, delete), but complete_task overlaps with update_task since the latter can also set status to completed. The descriptions make the distinction clear enough, but it's a minor point of confusion.
All tool names follow a consistent snake_case verb_noun pattern: create_task, list_tasks, get_task, update_task, delete_task, complete_task, get_task_summary. No deviations or mixed conventions.
Seven tools provide a well-scoped set covering standard task management operations plus a summary helper. Each tool earns its place without redundancy.
The toolset provides full CRUD coverage (create, read, list, update, delete), a dedicated complete action, and summary statistics. No obvious lifecycle gaps for a task manager; filters are available on list_tasks.