Docket
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TODO_MCP_WEB_PORT | No | Port for the web UI. Overrides the default port 8787. | 8787 |
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 |
|---|---|
| todo_addA | Add a new item to the shared global TODO list. Use list="backlog" for things to park and not hold in context (deferred findings, low-priority follow-ups); list="todo" (default) for near-term actionable items. |
| todo_editA | Edit an existing item's title/description/category/priority/dueDate/list by id. Only fields you pass are changed. Pass an empty string ("") for description/category/priority/dueDate to clear that field. |
| todo_claimA | Mark an item as actively being worked on by you (the calling agent). Advisory, not a lock — check todo_list(inProgress: true) before starting new work to avoid duplicating another agent's active item. Call todo_release or todo_complete when you stop. |
| todo_releaseA | Clear the in-progress claim on an item without completing it (e.g. you're pausing this work). |
| todo_listA | List items from the shared global TODO list, formatted as a checklist. |
| todo_completeA | Mark a todo as done by id. |
| todo_historyA | Show the change history (create/edit/claim/release/complete) for one item, who made each change and when. |
| todo_versionA | Report this todo-mcp process's data format version and start time. Use to sanity-check whether your MCP connection is running stale code (e.g. right after an update) — if todo_list output looks wrong (missing/undefined fields), check this first and reconnect if the process looks old. |
| todo_deleteA | Permanently remove a todo by id. |
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 9 tools
Each tool maps to a distinct action in the todo lifecycle: add, list, edit, claim, release, complete, delete, history, and version. Even close concepts like release and complete are clearly differentiated in their descriptions, so there is little risk of an agent selecting the wrong tool.
All tools share the consistent todo_ prefix and use snake_case with single-word command names. Most are verb-based (add, edit, claim, release, complete, list, delete), but history and version are noun-based, which is a minor deviation from the otherwise predictable pattern.
Nine tools is well within the ideal range for this domain and each tool serves a clear, non-redundant purpose. The count feels neither too thin nor bloated for a shared todo-list server.
The tool set provides full CRUD coverage (add/list/edit/delete) plus lifecycle actions for claiming, releasing, and completing items. The history and version tools add useful diagnostics, and there are no obvious missing operations that would block an agent from managing todos end-to-end.