Todo
Keep a personal task list that survives chat resets and syncs across MCP-enabled coding agents.
Overview
io.github.mctx-ai/todo is an MCP server for the Build phase that gives coding agents a persistent personal todo list across sessions and clients.
What is this MCP server?
- Hosted SSE remote at todo.mctx.ai (v2.0.3)—no local server required for remote clients
- Create, update, complete, and reorder todos from any MCP client in the same session fabric
- Cross-session persistence so agents resume work against your real backlog, not improvised lists
- MCP server integration, not a one-off prompt skill—tasks live in a dedicated service
- Pairs with Claude Code, Cursor, and other MCP hosts that support remote SSE transports
- Server version 2.0.3 per server manifest
- Remote transport: SSE at https://todo.mctx.ai/v2.0.3
- Website: https://todo.mctx.ai
What problem does it solve?
Agent chats forget your task list every session, so you repeat priorities and lose track of what shipped versus what is still open.
Who is it for?
Solo builders running multiple MCP sessions who want a single hosted todo remote without self-hosting infrastructure.
Skip if: Teams that need GitHub Issues-style workflows, assignees, or deep integration with Jira or Linear.
What do I get? / Deliverables
Your backlog lives in a shared MCP-backed todo service so any connected agent can read, update, and complete the same items reliably.
- Live todo items agents can mutate via MCP tools
- Ordered backlog visible across sessions and clients
- Reduced re-explaining of priorities in new chats
Recommended MCP Servers
Journey fit
Solo builders most often wire a persistent todo MCP while assembling agent workflows and sprint boards during the build phase, before heavier ship or launch work. Project-management tooling in Skillselion maps to build → pm because task lists anchor what the agent should do next across coding sessions.
How it compares
Hosted MCP todo service with SSE remote, not an in-repo agent skill or markdown checklist prompt.
Common Questions / FAQ
Who is io.github.mctx-ai/todo for?
Indie and solo builders using Claude Code, Cursor, or other MCP clients who want tasks to persist outside individual chat threads.
When should I use io.github.mctx-ai/todo?
Use it when you start a multi-day build or operate loop and need agents to create, complete, and reorder todos across sessions without re-pasting your backlog.
How do I add io.github.mctx-ai/todo to my agent?
Register the MCP remote SSE URL https://todo.mctx.ai/v2.0.3 in your client’s MCP server list (per todo.mctx.ai docs), then reload tools so create/update/complete actions appear.