lilt-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LILT_SNAPSHOT_PATH | No | Optional path to point the server at a specific Lilt snapshot.json file. If unset, the server tries the default Lilt container path, the Application Support path, then the iCloud Drive path. |
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 |
|---|---|
| list_tasksA | List the user's tasks in Lilt with their ids. By default shows open tasks only (To Do + In Progress). Use the returned [id] prefix with complete_task / update_task / delete_task. |
| list_projectsA | List the user's projects in Lilt with open-task counts. Use these exact names for the |
| list_habitsA | List the user's habits in Lilt with today's progress, streaks, and the last 7 days. Use the [id] with log_habit. |
| create_taskB | Create a new task in Lilt. It lands in 'To Do' and syncs to all the user's devices via iCloud. |
| complete_taskA | Mark a task done in Lilt. Identify it by id or title. If the task repeats, the next occurrence is created automatically. |
| reopen_taskA | Move a completed task back to 'To Do'. Identify it by id or title (searches done tasks too). |
| snooze_taskA | Snooze an open task: hide it from Lilt's board, menu bar and list_tasks until a wake time. Status, due date, project and recurrence are unchanged. Pass exactly one of |
| unsnooze_taskA | Clear a task's snooze so it reappears in Lilt immediately. Identify it by id or title. |
| update_taskA | Edit a task in Lilt. Only the fields you pass are changed. Identify the task by id or title. Pass an empty string for |
| delete_taskA | Delete a task in Lilt (permanent). Identify it by id or title. For a repeating task, |
| log_habitA | Log a habit completion in Lilt — today by default, or a past date to backfill. Identify the habit by id or name. Omit |
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 11 tools
Most tools map cleanly to a distinct resource+action (create/update/delete/complete/reopen/snooze/unsnooze on tasks, list/log on habits, list on projects). The only mild friction is that update_task's allowed fields are unspecified, so an agent might wonder whether status changes belong there rather than in complete_task/reopen_task. Snooze/unsnooze are explicitly delineated as out-of-band from update_task, which keeps the boundaries largely clear.
Every tool follows the same snake_case verb_noun pattern (list_projects, create_task, log_habit, unsnooze_task). Verb choice is also semantically consistent, with paired opposites (snooze/unsnooze, complete/reopen) named symmetrically.
Eleven tools is well within a comfortable range for a task/habit client. Each tool covers a genuinely distinct operation — the task lifecycle alone justifies seven of them, and no tool looks redundant or vestigial.
The task surface is essentially complete (create, list, update, delete, complete, reopen, snooze, unsnooze). However, habits only have list and log — there is no way to create, edit, or archive a habit — and projects are read-only, so agents will hit dead ends outside the task domain. Workarounds exist (habits/projects presumably managed in the Lilt app), but the surface is uneven.