A
licenseB
qualityC
maintenanceMCP server that gives AI agents read/write access to your Things3 tasks via the Things API.
32
1
Apache 2.0
Things MCP
by mathiswrong
Related Servers
Alternatives to Things MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables integration with Things3, allowing the creation and management of tasks and projects via the MCP protocol, including synchronization with Agenda projects.74-
- AlicenseAqualityDmaintenanceAn 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.154 npm2MIT
- AlicenseAqualityCmaintenanceComposite MCP server for Things 3 on macOS that bundles multiple read calls into single requests, enables batch writes, and provides a self-healing read path to handle TCC protection issues.8MIT
- AlicenseAqualityBmaintenanceA minimal MCP server for Things 3 on macOS that enables listing projects and tasks, creating tasks, and updating task status or metadata via natural language.4MIT
- AlicenseNot gradedqualityDmaintenanceA CLI MCP server for Things 3, enabling programmatic access to todos and projects with filtering by due date.4Apache 2.0
TDQS
A3.7/5.0
Scored across 20 tools
Disambiguation4/5
Most tools map to a distinct resource and action, and the paired destructive preview/apply flow is clearly separated. Minor overlap exists between create_item and create_from_template, and between schedule_item and edit_extras, so an agent must read descriptions carefully to pick the right one.
Naming Consistency4/5
All tools share the things_ prefix and use snake_case, with mostly verb_noun names like get_item, create_item, and restore_item. A few names are noun-only or less conventional (things_capabilities, things_health, things_exists, things_request_status), making the pattern slightly inconsistent.
Tool Count3/5
20 tools falls into the 16-25 range that feels heavy for a server. That said, each tool addresses a distinct operation or safety gate, so the count is still defensible for a full Things integration.
Completeness4/5
The surface covers create, read, update, move, schedule, duplicate, trash/restore, and reviewed destructive actions, which is strong lifecycle coverage for the domain. Minor gaps remain, such as no direct read-back for template-created items, no project-to-Logbook move, and disabled global destructive gates.
Maintenance
ActivityMaintained
ResponsivenessNo issues