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. Required for both local and remote deployments. | |
| MOTION_MCP_TOOLS | No | Tool selection mode: 'minimal', 'essential', 'complete' (default), or 'custom:tool1,tool2,...'. | |
| MOTION_MCP_SECRET | No | A random string used to secure the remote MCP endpoint. Required only 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 entity (tasks, projects, workspaces, users, schedules, search, comments, custom fields, recurring tasks, statuses). Even with overlapping concepts like tasks and recurring tasks, descriptions clarify the boundary. No two tools appear to serve the same purpose.
All tools follow the consistent 'motion_<plural_noun>' pattern in snake_case. The prefix 'motion_' unifies the set, and each resource name is intuitive. There are no stylistic deviations or mixed conventions.
Ten tools is appropriate for a project management API covering major resources and capabilities. The count is neither excessive nor thin, and each tool represents a meaningful domain. Some tools bundle many operations, but this is reasonable.
The surface covers core entities: tasks, projects, workspaces, users, schedules, search, comments, custom fields, recurring tasks, and statuses. However, project management is incomplete with only create/list/get for projects, missing update/delete. Also, user management might lack full CRUD, but it's less critical. Overall, minor gaps but most workflows are covered.