No user-submitted related servers found.
Scored across 10 tools
Each tool targets a distinct Motion resource (tasks, projects, workspaces, users, search, comments, custom fields, recurring tasks, schedules, statuses), with operations namespaced inside each tool. There is no meaningful overlap that would cause misselection; even search vs. list is clearly separated by intent.
All tool names follow a consistent motion_<resource> snake_case pattern. The convention is uniform across all 10 tools, making the set predictable and easy to scan.
10 tools map cleanly to the major Motion API resource groups. The count is well within the ideal 3–15 range, and each tool covers a distinct area without redundant wrappers.
Tasks are thoroughly covered (create, list, get, update, delete, move, unassign, list all uncompleted), but projects only support create/list/get with no update or delete, and recurring tasks plus custom fields lack update operations. These are notable lifecycle gaps that could force agents to work around missing operations.