Motion MCP Server
Related Servers
Alternatives to Motion MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceThis MCP server bridges Motion's API with LLMs like Claude and ChatGPT via the Model Context Protocol, so you can manage tasks, search projects, check your schedule, and more — all through natural conversation.10326 npm30Apache 2.0
- AlicenseBqualityDmaintenanceThis MCP server bridges Motion's API with LLMs like Claude and ChatGPT via the Model Context Protocol, so you can manage tasks, search projects, check your schedule, and more — all through natural conversation.10Apache 2.0
- AlicenseBqualityDmaintenanceBridges Motion's API with LLMs via the Model Context Protocol, so you can manage tasks, search projects, check your schedule, and more — all through natural conversation.10Apache 2.0
- AlicenseBqualityDmaintenanceEnables natural language management of Motion tasks, projects, schedules, and more via the Model Context Protocol, integrating with LLMs like Claude and ChatGPT.10Apache 2.0
- AlicenseBqualityDmaintenanceBridges Motion's API with LLMs via the Model Context Protocol, enabling natural language task, project, and schedule management.10Apache 2.0
- AlicenseNot gradedqualityNot gradedmaintenanceBridges Motion's AI-powered calendar and task management API with LLMs via the Model Context Protocol. It enables users to manage tasks, projects, schedules, and custom fields through natural language conversation.-
TDQS
Scored across 10 tools
Each tool is organized around a distinct Motion resource (tasks, projects, workspaces, users, comments, custom fields, recurring tasks, schedules, statuses), so selection is mostly clear. The main overlap is that motion_tasks bundles many actions while motion_search and motion_comments also operate on tasks, but the descriptions make the boundaries understandable.
All tools follow the same motion_<resource> pattern with plural resource nouns. There are no mixed verb styles, casing inconsistencies, or vague names.
Ten tools is well-scoped for a project/task management integration, with one tool per major resource area. The count avoids excessive fragmentation while still separating distinct domains.
Core task operations are well covered (create, list, get, update, delete, move, unassign), and several supporting resources are present. However, projects only support create/list/get with no update or delete, and recurring tasks lack update, leaving notable lifecycle gaps that could block agents.