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, required for all operations. Obtain from https://app.usemotion.com/settings/api. | |
| MOTION_MCP_TOOLS | No | Comma-separated list of tools to expose, or one of the preset levels: minimal, essential, complete (default), or custom:tool1,tool2. Defaults to complete. | complete |
| MOTION_MCP_SECRET | No | A random secret string used to secure the remote Cloudflare Workers endpoint. Required only for remote deployment. Generate with `openssl rand -hex 16`. |
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 maps to a distinct Motion resource (tasks, workspaces, projects, users, comments, etc.), so an agent can generally tell them apart. There is minor overlap risk between motion_tasks and motion_recurring_tasks, and motion_search overlaps somewhat with task/project lookup, but the descriptions clarify the boundaries.
The naming pattern is largely consistent: motion_ followed by a plural resource noun (motion_tasks, motion_projects, motion_users). The main deviation is motion_search, which uses an action rather than a resource noun, but the overall convention remains predictable.
Ten tools is well-scoped for a Motion integration covering tasks, projects, workspaces, users, search, comments, custom fields, recurring tasks, schedules, and statuses. Each tool earns its place and the count aligns with the breadth of the Motion API being exposed.
The tool surface covers the core Motion lifecycle well: tasks, projects, workspaces, users, comments, custom fields, recurring tasks, schedules, and statuses. Minor gaps exist, such as no dedicated tool for labels/filters or detailed scheduling operations, but agents can accomplish the main workflows with the provided tools.