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 from https://app.usemotion.com/settings/api | |
| MOTION_MCP_TOOLS | No | Optional. Comma-separated list of enabled tools or a preset name (minimal, essential, complete). Default is complete. | |
| MOTION_MCP_SECRET | No | Optional. A random secret string for remote deployment (Cloudflare Workers). Not needed for local use. |
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 (comments, custom fields, projects, recurring tasks, schedules, search, statuses, tasks, users, workspaces). No two tools have overlapping purposes; even 'motion_tasks' and 'motion_recurring_tasks' are clearly separated as general vs. recurring tasks.
All tool names follow a consistent 'motion_[resource_plural]' pattern using snake_case. The prefix and plural noun style is uniform across all 10 tools, making the naming predictable and easy to navigate.
With 10 tools covering tasks, projects, users, workspaces, comments, custom fields, recurring tasks, schedules, search, and statuses, the count is well-balanced for a project management API. Each tool serves a clear purpose without being overwhelming or sparse.
The tool surface covers all major entities and operations for task management: CRUD for tasks, projects, users, workspaces, comments, and custom fields, plus search, schedules, and status reads. There are no obvious gaps in core workflows.