things-turbo
Related Servers
Alternatives to things-turbo
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables MCP clients to read and manage a local Things 3 database on macOS through Things' supported scripting interface, listing, searching, creating, updating, moving, scheduling, and completing tasks, projects, and areas without any hosted service or network telemetry. Reads are paged and filtered, writes are confirmed by read-back verification, and an optional read-only mode blocks all mutations.8MIT
- AlicenseBqualityCmaintenanceAn MCP server for Things 3 on macOS that enables reading and writing tasks, projects, and more via Claude, using read-only SQLite and the official Things URL scheme.201MIT
- AlicenseNot gradedqualityDmaintenanceRead-only MCP server for Things 3 to retrieve completed tasks by date, weekly summaries, and project reports for analysis and reflection.15 npmISC
- AlicenseAqualityAmaintenanceEnables MCP clients to manage Things 3 tasks locally on macOS, including searching, creating, editing, scheduling, moving, completing, and trashing tasks through supported automation interfaces.2015 npm10MIT
- AlicenseAqualityCmaintenanceAn MCP server for Things 3 on macOS that enables AI assistants to create, read, update, and manage tasks and projects. It utilizes the Things URL scheme for write operations and AppleScript for querying data from the app.1511 npm2MIT
- AlicenseBqualityCmaintenanceMCP server that gives AI agents read/write access to your Things3 tasks via the Things API.321Apache 2.0
TDQS
Scored across 8 tools
The read tools (get_context, get_dashboard, get_review_data, get_project_health) are clearly distinct in their aggregation purposes. The write tools are also named by intent, though batch_update overlaps some with bulk_complete and bulk_reschedule since it can set completed and when, creating mild ambiguity.
Reads consistently use get_ and batch operations use bulk_ or batch_/update_. The pattern is readable and predictable, though batch_update and update_checklist break the bulk_ convention for write operations.
8 tools is a well-scoped size for a Things integration that provides both high-level read aggregation and targeted update operations. No tool feels redundant enough to remove, and the count is not overwhelming.
The server covers read aggregation, checklist updates, bulk completion, and rescheduling, but there are notable gaps: no tools for creating new todos, projects, areas, or tags, and no explicit delete/cancel operation beyond a canceled flag in batch_update. For a task-management server, lack of creation is a significant missing lifecycle operation.