holdon-todo
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOLDON_PAT | Yes | Your HoldOn Personal Access Token (PAT). Create a token by signing in at todo.holdon.ltd and selecting Extensions & tokens → Create Cursor MCP token. | |
| HOLDON_API_BASE | No | Optional base URL for the HoldOn API. | https://api.holdon.ltd/api/v1 |
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_groups_listA | List HoldOn todo groups (for matching group uuids when organizing items). |
| todo_listB | List HoldOn todos. status: 1=open, 2=done; omit for all. |
| todo_createA | Create a HoldOn todo. Use when the user asks to add a reminder or task. New items are ungrouped; use todo_list to verify. |
| todo_completeA | Mark a HoldOn todo as done (status=2). Call todo_list first if uuid is unknown. |
| todo_updateC | Update a HoldOn todo content or status. status: 1=open, 2=done. |
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 5 tools
Most tools target clearly distinct operations (list groups, list todos, create, update). However, todo_complete (mark done via status=2) substantially overlaps with todo_update, which can also set status=2, so an agent could reasonably reach for either when closing a task. Descriptions hint at the distinction but the boundary is not fully sharp.
All names are snake_case and share a consistent 'todo' prefix, which is highly predictable. The one deviation is todo_groups_list, which puts the resource before the verb (noun_noun_verb) while every other tool follows todo_<verb>. Minor but noticeable pattern break.
Five tools is a well-scoped surface for a todo server: listing groups, listing items, and create/update/complete cover the core interaction loop without redundancy or bloat. Each tool earns its place for the stated purpose.
The surface covers create, read, update, and completion of todos plus group listing, which handles most todo workflows. The notable gap is deletion (no todo_delete or group creation), so users cannot remove tasks or create groups; agents can partially work around this by marking items done.