donetick-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Log level (DEBUG, INFO, WARNING, ERROR) | INFO |
| RATE_LIMIT_BURST | No | Burst capacity | 10 |
| DONETICK_BASE_URL | Yes | Donetick instance URL | |
| DONETICK_PASSWORD | Yes | Donetick password | |
| DONETICK_USERNAME | Yes | Donetick username | |
| RATE_LIMIT_PER_SECOND | No | API rate limit | 10.0 |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_choresA | List all chores. Filter by active status or assigned user. Use detail_level='brief' for compact output. |
| get_choreB | Get full details of a specific chore by ID, including subtasks and labels. |
| create_choreA | Create a new chore. Use simple inputs like usernames and day names. EXAMPLES:
If no usernames provided, chore is assigned to ANYONE in the circle (round-robin). |
| update_choreB | Update any chore fields. Only provide fields you want to change. Supports: name, description, schedule/frequency, assignees, priority, labels (add/remove/set by name), notifications, and more. |
| delete_choreA | Delete a chore permanently. Only the creator can delete. |
| list_archived_choresA | List all archived (hidden) chores. |
| complete_choreC | Mark a chore as complete. |
| skip_choreA | Skip a chore without completing. For recurring chores, schedules the next occurrence. |
| archive_choreA | Archive a chore (soft-delete / hide). Can be unarchived later. |
| unarchive_choreA | Restore a previously archived chore. |
| approve_choreB | Approve a chore completion that requires approval. |
| reject_choreC | Reject a chore completion that requires approval. |
| update_due_dateA | Quickly reschedule a chore's due date without a full update. |
| start_chore_timerB | Start the time tracker for a chore. |
| pause_chore_timerB | Pause the time tracker for a chore. |
| update_subtask_completionB | Mark a subtask complete or incomplete. |
| create_subtaskB | Add a new subtask/checklist item to an existing chore. |
| delete_subtaskB | Remove a subtask from a chore. |
| convert_chore_to_subtaskA | Convert a standalone chore into a subtask of another chore. Deletes the original chore and creates a subtask with its name on the target. |
| list_labelsA | List all labels in the circle. |
| create_labelB | Create a new label for categorizing chores. |
| update_labelA | Rename a label or change its color. |
| delete_labelA | Delete a label. Removes it from all chores. |
| list_circle_membersA | List all members in the circle with IDs, usernames, roles, and points. Use this to find user IDs for assignment. |
| get_user_profileA | Get the current user's profile (points, storage, notification config). |
| get_chore_historyA | Get completion history. If chore_id provided, returns history for that chore. Otherwise returns all chores history with pagination. |
| get_chore_detailsA | Get chore with completion statistics: total count, last completion, average duration, recent history. |
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 27 tools
Each tool targets a distinct action on a specific resource (chore, label, subtask, user, timer). Overlaps like get_chore, get_chore_details, and get_chore_history are clearly differentiated by the type of data returned. The descriptions provide enough detail to avoid confusion.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., create_chore, list_chores, delete_label). Slight variations like convert_chore_to_subtask or update_subtask_completion still adhere to the pattern, ensuring predictability.
With 27 tools, the set is comprehensive for a chore management domain, covering creation, updates, deletion, completion, approval, archiving, timers, and labels. While slightly on the higher side, each tool serves a clear purpose and none are redundant.
The tool set provides full CRUD for chores, labels, and subtasks, along with lifecycle management (completion, approval, archiving, timers, history). There are no obvious gaps for core operations in a chore management application.