agent-todo-mcp
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 | {} |
| logging | {} |
| prompts | {} |
| resources | {} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_todoA | Create a new TODO item with optional metadata. IMPORTANT: Before creating your first TODO, call list_projects to check existing workspaces, then call switch_project to set up your project workspace. |
| list_todosB | List TODOs with optional filtering and sorting |
| update_todoB | Update an existing TODO item |
| delete_todoA | Delete a TODO item |
| get_todoA | Get detailed information about a specific TODO |
| search_todosA | Search TODOs by title, description, or metadata |
| generate_reportC | Generate a comprehensive progress report |
| get_statsB | Get quick statistics about TODOs |
| get_project_infoB | Get current project workspace information |
| switch_projectA | Switch to a different project workspace or create a new one. IMPORTANT: You must call this tool to set up a project before creating any TODOs. Recommendation: Call list_projects first to see existing workspaces and avoid creating duplicates. Each project isolates its TODO data completely. |
| list_projectsA | List all available project workspaces. RECOMMENDED: Call this first to see existing projects before creating new ones with switch_project. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| daily-standup | Generate a daily standup summary based on current TODOs |
| sprint-planning | Create a sprint planning summary with TODO prioritization |
| project-review | Generate a comprehensive project review and analysis |
| todo-prioritization | Help prioritize TODOs based on urgency and importance |
| blocked-items-review | Review and analyze blocked items with suggested actions |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Current project summary | Summary of the current project with stats and recent activity |
| All TODOs in JSON format | Complete list of TODOs in JSON format |
| All TODOs in Markdown format | Complete list of TODOs formatted as Markdown |
| All TODOs in CSV format | Complete list of TODOs in CSV format for spreadsheet import |
| Project progress report | Comprehensive project progress report with metrics and analysis |
| Project metrics and analytics | Detailed project metrics and analytics in JSON format |
TDQS
Scored across 11 tools
Most tools have clear, distinct purposes: CRUD operations for TODOs are separate (create, list, get, update, delete, search). Potential overlap exists between generate_report and get_stats, as both provide aggregate views, but report is more comprehensive while stats are quick numbers, so they are distinguishable.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_todo, list_projects, get_stats). There are no mixed conventions or vague verbs, making the naming predictable and easy to navigate.
With 11 tools, the count is well-scoped for a TODO management server with project workspace support. Each tool serves a distinct need, and the number is neither too sparse nor overwhelming for the apparent functionality.
The TODO lifecycle is fully covered with create, read, update, delete, list, and search operations. Project management is sufficient with list, switch/get info, though there is no explicit delete or rename project tool, which is a minor gap but not critical for core workflows.