Reclaim.ai MCP Server
Related Servers
Alternatives to Reclaim.ai MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables interaction with TickTick task management system through MCP, allowing users to view, create, update, complete, and delete tasks and projects via natural language.-
- FlicenseNot gradedqualityCmaintenanceEnables natural language interaction with Taskwarrior tasks through the MCP. Supports project-scoped task management including adding, searching, modifying, completing, and annotating tasks.-
- FlicenseNot gradedqualityDmaintenanceEnables interacting with TickTick tasks and projects through natural language via Claude and other MCP clients.-
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Todoist through the MCP interface, providing full CRUD operations for tasks and projects including creating, updating, completing, and filtering tasks with natural language commands.9 npmMIT
- AlicenseBqualityCmaintenanceEnables natural-language management of Motion tasks, projects, schedules, comments, custom fields, and more, bridging Motion's API to LLM clients via MCP.10Apache 2.0
- AlicenseAqualityCmaintenanceEnables AI assistants to browse task groups, list open or completed todos, create new tasks, mark them done, and update their content or status through a token-authenticated MCP connection.5MIT
TDQS
Scored across 13 tools
Each tool targets a distinct action on Reclaim.ai tasks: creating, reading, updating, deleting, time management, prioritization, and status changes. No two tools overlap in purpose; even similar verbs like 'add_time' and 'log_work' are clearly differentiated.
All tools follow a consistent 'reclaim_verb_noun' pattern (e.g., reclaim_create_task, reclaim_list_tasks, reclaim_start_timer). The naming is uniform, with clear verbs that describe the action, making it easy to predict tool behavior.
With 13 tools, the server is well-scoped for task management. Each tool covers a necessary operation without being overwhelming. The count is typical for a domain-specific MCP server, providing sufficient functionality without redundancy.
The server covers core CRUD, lifecycle (complete/incomplete), time tracking (add, log, start/stop timer), prioritization, and exception handling. Minor gaps exist, such as no bulk operations or filtering by date range, but the essential workflows are supported.