Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MOTION_API_KEYNoYour Motion API key.
MOTION_MCP_TOOLSNoControls which tools are exposed: minimal, essential, complete (default), or custom:motion_tasks,motion_projects,motion_search.
MOTION_MCP_SECRETNoA random secret used for remote deployment; it is placed at the end of the MCP URL path or sent as a Bearer token in the Authorization header.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Motion MCP Server — AI-powered task and project management.

Use this server to interact with Motion (usemotion.com), an auto-scheduling calendar and task manager.

Capabilities:

  • Tasks: create, list, search, update, delete, move, and unassign tasks

  • Projects: create, list, and get project details

  • Workspaces: list and manage workspace context

  • Users: list team members and get current user info

  • Search: full-text search across tasks and projects, smart context retrieval

  • Comments: read and create comments on tasks and projects

  • Schedules: view available scheduling slots and calendars

  • Statuses: list workflow statuses for workspaces

  • Custom Fields: manage custom metadata on tasks and projects

  • Recurring Tasks: create and manage recurring task templates

Keywords: motion, task management, project management, calendar, scheduling, auto-schedule, productivity, to-do, assignee, deadline, priority, workspace, team

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}
prompts
{}
resources
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
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_workspacesA

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_tasksA

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 each day's working hours (start-end per day) and time zones. The Motion API returns all schedules with no filtering options. These are recurring working-hour templates only — they do NOT expose actual calendar events or meetings, so they cannot by themselves show a true free/busy picture; combine with tasks' scheduledStart/scheduledEnd to see what Motion has auto-booked.

motion_statusesA

Get available task/project statuses for a workspace

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 10 tools

Disambiguation4/5

Each tool maps to a clearly distinct resource (tasks, projects, workspaces, comments, users, schedules, statuses, recurring tasks, custom fields), so misselection is unlikely. The only mild overlap is motion_search, which can return tasks/projects that could also be fetched via the list operations on motion_tasks and motion_projects, but the query-based purpose keeps it distinguishable.

Naming Consistency5/5

All ten tools follow the exact same pattern: a motion_ prefix plus a lowercase snake_case resource noun (motion_tasks, motion_projects, motion_custom_fields, motion_recurring_tasks). No mixed conventions or verb/noun inconsistency anywhere in the set.

Tool Count5/5

Ten tools is squarely in the well-scoped range, and each tool corresponds to a genuine Motion domain entity rather than being a redundant wrapper. Nothing feels padded or missing at the resource level.

Completeness3/5

Task coverage is strong (create/list/get/update/delete/move/unassign/comment), but projects only support create/list/get with no update or delete, and workspaces are read-only. Users also lack invite/remove operations, leaving a few lifecycle gaps agents may hit when managing projects or membership.