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, obtainable from https://app.usemotion.com/settings/api. | |
| MOTION_MCP_TOOLS | No | Limit which tools are exposed. Options: 'minimal' (3 tools), 'essential' (7 tools), 'complete' (default, 10 tools), or 'custom:tool_name1,tool_name2'. | complete |
| MOTION_MCP_SECRET | No | A random string (e.g., generated with 'openssl rand -hex 16') used to secure the endpoint when deploying to Cloudflare Workers. |
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 has a clearly distinct purpose targeting specific Motion resources like comments, custom_fields, projects, recurring_tasks, schedules, search, statuses, tasks, users, and workspaces. There is no overlap in functionality, making it easy for an agent to select the correct tool for any operation.
All tools follow a consistent 'motion_' prefix with a descriptive noun (e.g., motion_comments, motion_custom_fields, motion_projects). This uniform naming pattern enhances predictability and readability across the entire tool set.
With 10 tools, the server is well-scoped for managing Motion's project and task management domain. Each tool covers a distinct aspect (e.g., tasks, projects, users, custom fields), ensuring comprehensive coverage without being overwhelming or sparse.
The tool set provides complete CRUD/lifecycle coverage for Motion's core resources, including tasks (create, list, get, update, delete, move, unassign), projects (create, list, get), and supporting operations like custom fields, comments, users, workspaces, and search. There are no obvious gaps that would hinder agent workflows.