Summary
Motion's whole API, with the rate limit already handled.
Motion's API is rate-limited tightly enough that a batch of task edits turns into a run of failures. Keeping that budget in a database that survives restarts is what makes a long agent session against Motion practical.
What it is
A server over Motion's API covering tasks, recurring tasks, projects, workspaces, users, comments and schedules. It manages Motion's request budget for you — rate-limit state is kept in a SQLite database that survives restarts, so Motion's request ceiling is respected rather than discovered.
What you get
- Tasks listed with filters, read, created, updated, deleted, moved between workspaces and unassigned
- Recurring tasks listed, created and deleted
- Projects listed, read, created, updated and archived
- Workspaces listed and read, users listed, and the current user identified
- Comments listed on a task and added to it
- Schedules listed
- Rate limiting handled automatically against Motion's rate limit, with the state persisted in SQLite
Requirements
A Motion API key, created at Settings > API & Integrations, set as MOTION_API_KEY. Installed globally from npm as @h3ro-dev/motion-mcp-server, or run on demand with npx -y.