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 to authenticate with the Motion API. | |
| MOTION_MCP_TOOLS | No | Comma-separated list of tools to expose, or preset names like 'minimal', 'essential', 'complete'. Defaults to 'complete'. Example: 'custom:motion_tasks,motion_projects'. | |
| MOTION_MCP_SECRET | No | A random string used to secure the remote MCP endpoint. Only needed when deploying as a Cloudflare Worker. |
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 or action: tasks, users, projects, workspaces, search, comments, custom fields, recurring tasks, schedules, and statuses. There is no ambiguity between tools, as even motion_tasks and motion_recurring_tasks are clearly differentiated by their descriptions.
All tools follow a consistent motion_<plural_resource> naming pattern. This makes the tool set predictable and easy to navigate, with no mixing of conventions or verb styles.
With 10 tools, the server covers a broad domain (Motion project management) without being bloated. Each tool serves a clear purpose, and the count is well within the ideal 3-15 range.
The set covers core CRUD for tasks, project creation and retrieval, user and workspace info, search, comments, custom fields, recurring tasks, schedules, and statuses. However, project update/delete is missing, and recurring tasks lack an update operation, which are minor gaps that agents could work around.