Motion MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MOTION_API_KEY | No | Your Motion API key, obtained from https://app.usemotion.com/settings/api | |
| MOTION_MCP_TOOLS | No | Tool configuration level: minimal, essential, complete, or custom:tool1,tool2,... Default is complete | complete |
| MOTION_MCP_SECRET | No | A random secret used to secure the remote MCP endpoint (required for Cloudflare Workers deployment) |
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 resource: tasks, schedules, projects, workspaces, users, search, comments, custom fields, recurring tasks, and statuses. There is no overlap in purpose, and even tasks vs recurring tasks are clearly differentiated by their descriptions.
All tool names follow a consistent motion_<resource> pattern using plural nouns. This uniform convention makes the tool set predictable and easy to navigate.
With 10 tools, the server is well-scoped for the Motion API domain. Each tool covers a core entity or operation without unnecessary redundancy or bloat.
Tasks have full lifecycle coverage, and most entities have list/create/delete/update as appropriate. However, projects lack update/delete operations and recurring tasks lack update, leaving minor gaps that agents can work around.