No user-submitted related servers found.
Scored across 31 tools
The planner_* and todo_* prefixes cleanly separate the two product domains, and within each domain the resource+action combinations are distinct (list_buckets vs list_tasks vs my_tasks). The only mild risk is an agent choosing between planner_create_task and todo_create_task, but the descriptions make the target system explicit.
Almost every tool follows a predictable prefix + verb_noun pattern (planner_create_plan, todo_update_checklist_item, etc.). Minor deviations: planner_list_my_groups breaks the pattern (elsewhere it's list_plans/list_buckets), and the auth tools (login, auto_login, auth_status) use verb-only and noun-first forms instead of the verb_noun convention.
31 tools is heavy for a single MCP server, but it covers two full products (Planner and To Do) each with plans/lists, buckets, tasks, and checklists, so nearly every tool has a genuine role. Still, it sits at the upper edge where an agent faces a large surface and some consolidation (e.g. checklist operations) could trim it.
Both domains have full lifecycle coverage: create/rename/delete for plans, buckets and lists, plus task create/get/list/update/delete/move and checklist add/update/delete for To Do. Gaps are minor: no planner_get_plan or planner_get_bucket, and Planner checklists can only be ticked via planner_update_task with no dedicated add/delete checklist item tools as To Do has.