Motion MCP server

What the model can do

Motion auto-scheduling work manager: workspaces with their statuses and labels, tasks by workspace, project, assignee, status, label or name with due dates, priority, duration and when Motion has scheduled them, projects, people and recurring tasks; when you ask, can create, update, complete, move, unassign and delete tasks, comment on tasks, create projects, and create or delete recurring tasks.

Reads

• motion_list_workspacesMotion workspaces this key can see: id, name, team or individual, labels, and statuses (which is the default and which count as done).
• motion_list_tasksMotion tasks: name, status, priority, due date, duration, when Motion scheduled it, project, workspace, assignees, labels and who created it…
• motion_get_taskOne Motion task by id, with the same fields as motion_list_tasks.
• motion_list_projectsMotion projects: name, status (and whether it counts as done), workspace, created and updated times.
• motion_list_usersPeople in a Motion workspace or team: id and name (emails are not returned).
• motion_list_recurring_tasksRecurring tasks in a Motion workspace: name, assignee, project and who created it.

Acts, when you ask

These change something in Motion. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• motion_create_taskCreates a task in a Motion workspace, created by the key's owner and assigned to assignee_id if given (Motion may notify them).
• motion_update_taskChanges a Motion task: name, status (a done status completes it), due date, duration, priority, labels, project, assignee, description…
• motion_move_taskMoves a Motion task to another workspace, optionally assigning it to someone there.
• motion_unassign_taskRemoves the assignee from a Motion task, taking it off their schedule.
• motion_delete_taskPermanently deletes a Motion task and takes it off everyone's schedule.
• motion_comment_on_taskPosts a comment (GitHub Markdown) on a Motion task as the key's owner, visible to everyone on the task; the API cannot delete it.
• motion_create_projectCreates a project in a Motion workspace, visible to its members.
• motion_create_recurring_taskCreates a recurring task in a Motion workspace, assigned to assignee_id…
• motion_delete_recurring_taskPermanently deletes a Motion recurring task, so no further occurrences are scheduled.

Connect it

First connect Motion on Dashboard → Connections, then add Memtro to your client once. The Motion tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Motion connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › What is scheduled for me this week?
• › Which of my tasks are overdue?
• › What is left open in the website relaunch project?
• › Which recurring tasks are set up in the operations workspace?
• › Create a task to review the Q3 budget, due Friday.

Questions

Is this an official Motion MCP server?

No. It is Memtro's MCP server with Memtro's Motion connector behind it: the connector reads Motion through its API with the credentials you connect on Dashboard → Connections, and Motion publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Motion?

Only when you ask, and only what it has been granted: create a task; update a task (name, status, due date, priority, assignee, scheduling); move a task to another workspace; unassign a task; delete a task; comment on a task; create a project; create a recurring task; delete a recurring task. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Work management

• Clio Manage MCP server
• Linear MCP server
• Jira MCP server
• Asana MCP server
• monday.com MCP server
• Airtable MCP server