lilt-mcp
Related Servers
Alternatives to lilt-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables Claude to read, create, update, and complete tasks across lists, including grouped context for overdue, upcoming, and undated items.7MIT
- AlicenseBqualityDmaintenanceEnables Claude to interact with task management data in the Things app, including creating tasks, managing projects, searching, and organizing priorities.211MIT
- FlicenseBqualityDmaintenanceEnables Claude to interact with Things 3 on macOS, allowing users to create, update, and manage to-dos and projects, list tasks, search items, and navigate through Things lists using natural language.2016-
- AlicenseNot gradedqualityBmaintenanceEnables Claude to locally read and manage Things 3 tasks, projects, areas, headings, tags, checklists, deadlines, and reminders, including creating, editing, searching, completing, canceling, and trashing items.MIT
- AlicenseBqualityDmaintenanceEnables Claude to interact with Things 3 task management, allowing natural language task creation, project analysis, and GTD workflow automation.2473 PyPI44MIT
- FlicenseNot gradedqualityFmaintenanceEnables Claude Desktop and other MCP clients to manage Todoist tasks, projects, and labels through natural language.3-
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.