A
licenseNot graded
qualityD
maintenanceEnables LLMs to interact with Things 3 task manager on macOS via AppleScript, allowing users to list and create todos across different lists through natural language.
13 npm
MIT
things3-mcp-server
by Schimmilab
Related Servers
Alternatives to things3-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables 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.205 npm17ISC
- AlicenseBqualityDmaintenanceEnables Claude to interact with Things 3 task management, allowing creation, analysis, and management of tasks, projects, and tags via natural language.22MIT
- AlicenseBqualityDmaintenanceEnables Claude to interact with task management data in the Things app, including creating tasks, managing projects, searching, and organizing priorities.211MIT
- AlicenseBqualityDmaintenanceEnables Claude to interact with Things 3 task management, allowing natural language task creation, project analysis, and GTD workflow automation.2443MIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with the Things app for task management, allowing natural language task creation, project analysis, and priority management.MIT
TDQS
A3.6/5.0
Scored across 14 tools
Disambiguation2/5
There are five ways to retrieve to-do lists (list_todos, get_today, get_inbox, get_completed, search_todos), and list_todos is vague about what 'one scope' means, creating unclear boundaries. The update/complete/cancel/add_tags tools also share the same todo_id-or-query targeting pattern, which could lead an agent to pick the wrong mutating operation without careful reading.
Naming Consistency4/5
Names uniformly use lowercase verb_noun patterns: list_*, get_*, search_*, create_*, update_*, complete_*, cancel_*, add_tags. The main deviation is that get_* mixes single-item lookup (get_todo) with list-returning operations (get_today, get_completed, get_inbox), so the verb prefix does not strictly predict the return shape, but the overall style is predictable.
Tool Count4/5
14 tools is reasonable for a Things 3 server and stays within the expected range, covering to-do read/write plus area/project/tag lookup. The count is slightly inflated by the many overlapping read/list routes for to-dos, but each still has a concrete intended use.
Completeness4/5
The to-do lifecycle is well covered: create, read/list/search, update, complete, cancel, and tag management are all present. The main gaps are a lack of direct deletion (mitigated by cancel_todo) and write support for projects/areas/tags, but these are reasonable for a to-do-focused server.
Maintenance
ActivityMaintained
ResponsivenessNo issues