Motionmcp MCP Server

MCP server for Motion API integration - manage projects, tasks, and workspaces from LLMs

Local serverstdioGo

What is the Motionmcp MCP server?

Most planning and project tracking work still happens through a UI a human drives. Motionmcp MCP server moves it into the conversation instead. MCP server for Motion API integration - manage projects, tasks, and workspaces from LLMs.

The short version

For desktop MCP clients — Claude Desktop, Claude Code, Cursor, and similar.

Getting it running

Installation goes through your MCP client rather than a global install: point it at motionmcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

The tools it exposes

The server publishes 10 tools. What each one is for:

  • motion_tasks — The primary tool for task management. Supports all Motion API parameters including name, description, priority, dueDate, duration, labels
  • motion_projects — Manage Motion projects. Workspace and project names are fuzzy-matched, and the server auto-selects your "Personal" workspace if none is specified
  • motion_workspaces — The motion_workspaces tool exposed by this server
  • motion_users — List users in a workspace or get the current authenticated user
  • motion_search — The motion_search tool exposed by this server
  • motion_comments — The motion_comments tool exposed by this server
  • motion_schedules — Retrieve user schedules and time zones. Supports prioritized scheduling with conflict detection and workload breakdowns by status, priority, and
  • motion_custom_fields — Define and manage custom fields across workspaces, projects, and tasks
  • motion_recurring_tasks — The motion_recurring_tasks tool exposed by this server
  • motion_statuses — The motion_statuses tool exposed by this server

What it needs from you

Configuration is passed through the environment: MOTION_API_KEY, MOTION_MCP_TOOLS, MOTION_MCP_SECRET, YOUR_SECRET. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 10 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Motionmcp.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Among the planning and project tracking options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Motionmcp's toolset — motion_tasks, motion_projects, motion_workspaces and 7 more — is a fair guide to whether it matches your workflow. It is maintained by devondragon; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Motionmcp's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
motion_tasksThe primary tool for task management. Supports all Motion API parameters including name, description, priority, dueDate, duration, labels, assigneeId, and autoScheduled. You can reference workspaces and projects by name
motion_projectsManage Motion projects. Workspace and project names are fuzzy-matched, and the server auto-selects your "Personal" workspace if none is specified.
motion_workspacesThe motion_workspaces tool exposed by this server.
motion_usersList users in a workspace or get the current authenticated user.
motion_searchThe motion_search tool exposed by this server.
motion_commentsThe motion_comments tool exposed by this server.
motion_schedulesRetrieve user schedules and time zones. Supports prioritized scheduling with conflict detection and workload breakdowns by status, priority, and project.
motion_custom_fieldsDefine and manage custom fields across workspaces, projects, and tasks.
motion_recurring_tasksThe motion_recurring_tasks tool exposed by this server.
motion_statusesThe motion_statuses tool exposed by this server.

How to install the Motionmcp MCP server

{
  "mcpServers": {
    "motion": {
      "command": "npx",
      "args": ["motionmcp"],
      "env": {
        "MOTION_API_KEY": "your_api_key"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
MOTION_API_KEYCredential the server authenticates with.Yes
MOTION_MCP_TOOLSConfiguration value read at startup.Optional
MOTION_MCP_SECRETCredential the server authenticates with.Yes
YOUR_SECRETCredential the server authenticates with.Yes

Example prompts to try

  • Use Motionmcp to motion tasks.
  • Use Motionmcp to motion projects.
  • Use Motionmcp to motion workspaces.

Frequently asked questions

It connects Motionmcp to MCP-compatible AI assistants such as Claude and Cursor, exposing 10 tools (motion_tasks, motion_projects, motion_workspaces, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Motionmcp directly.