Motion MCP Server
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 | Tool configuration level: minimal, essential, complete, or custom:tool1,tool2,... | |
| MOTION_MCP_SECRET | No | A random secret string for remote deployment via Cloudflare Workers. |
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_workspacesC | 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_tasksB | 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 weekly working hours and time zones. The Motion API returns all schedules with no filtering options. |
| 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, schedules, statuses, projects, workspaces, users, search, comments, custom fields, recurring tasks). No two tools appear to do the same thing, and recurring tasks are clearly distinguished from general tasks.
All tool names follow a consistent pattern: motion_ followed by a plural noun (e.g., motion_tasks, motion_projects). This makes the API predictable and easy to navigate.
10 tools is well-scoped for the breadth of Motion's API, covering core resources (tasks, projects, workspaces, users), cross-cutting features (search, comments, custom fields), and specialized entities (recurring tasks) without being bloated.
The tool surface covers the main task lifecycle comprehensively (create, list, get, update, delete, move, unassign). Minor gaps exist: projects lack update/delete operations, and user management is vaguely described, but these are workable for most workflows.