
Motion Mcp Public
Connect Motion task and calendar scheduling to Claude through MCP so your agent can read and update your solo-builder work queue without context switching.
Overview
Motion MCP Public is a MCP server for the Build phase that bridges Motion tasks and scheduling to Claude over MCP.
What is this MCP server?
- Remote MCP server bridging Motion to Claude (`@dishui/motion-mcp` npm v1.0.1)
- stdio package entry for standard MCP client registration
- Keeps scheduling and task state accessible inside agent sessions
- Public dishui/motion-mcp-public distribution on npm
- Focused integration—Motion calendar/tasks, not a full PM methodology skill
- Package version 1.0.1, npm identifier `@dishui/motion-mcp`
- Described as remote MCP server bridging Motion to Claude
- stdio transport in published server metadata
What problem does it solve?
Your tasks live in Motion but your coding agent cannot see deadlines or update work items, forcing constant app switching.
Who is it for?
Solo builders who already organize shipping work in Motion and use Claude as their primary coding agent.
Skip if: Teams on Notion/Linear-only workflows without Motion, or builders who want offline task management with no SaaS bridge.
What do I get? / Deliverables
Claude can interact with Motion through MCP so implementation chats stay tied to your real schedule and task list.
- Motion task and schedule visibility inside agent chats
- Reduced context switching between Motion and the IDE
- Agent-driven updates aligned with your Motion work queue
Recommended MCP Servers
Journey fit
Build + PM is the canonical shelf because indie makers use Motion to sequence implementation work, specs, and deadlines while coding—not primarily for post-launch SEO. PM subphase matches bridging a task scheduler into the IDE agent during active product delivery and sprint-style personal planning.
How it compares
Motion-to-Claude MCP connector, not a universal project-management methodology skill.
Common Questions / FAQ
Who is Motion MCP Public for?
Indie developers and founders who run their calendar and tasks in Motion and want those items available inside Claude via MCP.
When should I use Motion MCP Public?
Use it while building and shipping when you want the agent to reference Motion deadlines, batch work, or update tasks during coding sessions.
How do I add Motion MCP Public to my agent?
Install npm `@dishui/motion-mcp` (1.0.1), add the stdio MCP server entry in Claude Code or Claude Desktop, and complete Motion authentication steps from the package README.