MotionMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MOTION_API_KEY | Yes | Your Motion API key | |
| MOTION_MCP_TOOLS | No | Limits which tools are exposed. Options: minimal, essential, complete, or custom:tool1,tool2,... | complete |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| motion_tasksC | Manage Motion tasks - supports create, list, get, update, delete, move, unassign, and list_all_uncompleted operations |
| motion_projectsC | Manage Motion projects - supports create, list, and get operations |
| motion_workspacesA | Manage Motion workspaces - supports list and get operations |
| motion_usersC | Manage users and get current user information |
| motion_searchB | Search Motion tasks and projects by query |
| motion_commentsC | Manage comments on tasks |
| motion_custom_fieldsB | Manage custom fields for tasks and projects. Required params per operation: list: workspaceId or workspaceName. create: workspaceId/workspaceName + name + field (type); options[] also required for select/multiSelect. delete: workspaceId/workspaceName + fieldId. add_to_project: projectId + fieldId. remove_from_project: projectId + valueId. add_to_task: taskId + fieldId. remove_from_task: taskId + valueId. |
| motion_recurring_tasksA | Manage recurring tasks. Required params per operation: list: workspaceId or workspaceName. create: workspaceId/workspaceName + name + assigneeId + frequency (with frequency.type). delete: recurringTaskId. |
| motion_schedulesA | Get all schedules showing each day's working hours (start-end per day) and time zones. The Motion API returns all schedules with no filtering options. These are recurring working-hour templates only — they do NOT expose actual calendar events or meetings, so they cannot by themselves show a true free/busy picture; combine with tasks' scheduledStart/scheduledEnd to see what Motion has auto-booked. |
| motion_statusesA | Get available task/project statuses for a workspace |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
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.