mcp-code-todo
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": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| set_workspaceA | Set the workspace root directory for scanning TODOs. Call this first if the default workspace detection doesn't work. |
| get_workspaceA | Get the current workspace root directory that will be used for scanning. |
| scan_todosA | Scan the codebase for TODO comments. Returns all found TODOs with their locations and metadata. |
| explain_todoA | Get more context for a specific TODO item, including surrounding code lines. |
| group_todos_by_topicC | Group TODOs by various criteria including file paths, priority, and ownership. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| find_todos_in_app | Guide the client through discovering TODOs in the current app and investigating the most relevant ones. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| todo-list |
TDQS
Scored across 5 tools
Each tool targets a distinct action: workspace retrieval/setting, scanning, grouping, and explaining TODOs. No two tools appear to serve the same purpose.
All tool names follow a consistent verb_noun pattern in snake_case (get_workspace, scan_todos, group_todos_by_topic, explain_todo, set_workspace). This is predictable and clear.
With 5 tools, the set is well-scoped for a TODO scanning and analysis server. Each tool covers a necessary operation without redundancy or bloat.
The surface covers workspace configuration, scanning, grouping, and context explanation—a complete workflow for TODO analysis. No obvious missing operations for the stated purpose.