TaskFlow 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 | |
| update_task_statusA | |
| get_task_detailsB | Get detailed information about a specific task |
| list_tasks_by_userA | List all tasks assigned to a specific user, optionally filtered by status |
| get_overdue_tasksA | Get all tasks that are past their due date and not completed |
| search_tasksB | Search tasks by title, description, or tags |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| task-creation-assistant | Prompt to help create well-structured tasks |
| daily-standup | Prompt for generating daily standup reports |
| project-planning | Prompt for project planning and task breakdown |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_dashboard_summary | Get task dashboard summary |
TDQS
Scored across 6 tools
Each tool has a distinct purpose: create, update status, get details, list by user, list overdue, and search. The retrieval tools are differentiated by filter criteria (user, overdue, search terms), so there is no meaningful overlap.
The naming follows a consistent verb_noun snake_case pattern. The only minor inconsistency is mixing 'get' and 'list' for retrieval operations, but this is common and does not cause confusion.
Six tools is appropriate for a focused task management server, covering the essential operations without unnecessary bloat. This is well within the ideal 3-15 range.
The server covers create, status update, read, list by user, overdue, and search, but lacks update for task details (e.g., priority, due date) and no delete operation. This means agents cannot fully manage task lifecycle, leaving notable gaps.