toda
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@toda note that rate limiting is deferred until we add Redis"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
TODA — deferred-issues tracker
Tracks issues deliberately put aside during LLM-assisted work ("not a priority, later"),
so they stop getting lost between sessions. One plain-text ledger per project
(TODA.md) is the single source of truth; a stateless stdio MCP server provides five
tools over it. No network, no database, sub-millisecond operations.
Spec:
docs/superpowers/specs/2026-10-27-toda-design.mdFormat: one item per line —
D-017 o 2026-10-26 payments/stripe.ts:210 what / why-deferred / revive: trigger [/ ref: REFS] [/ done: NOTE]The file is the contract: humans and non-MCP LLMs can Read/Edit
TODA.mddirectly. Unknown lines are preserved verbatim by all tools.
Tools
Tool | Purpose |
| Create |
| Append an item ( |
| List items (default open + sleeping; |
| Change status ( |
| Move done items opened more than N days ago (default 30) to |
Related MCP server: horizon-ledger
Convention-file snippet (paste into AGENTS.md / CLAUDE.md / .cursorrules)
TODA rule: When we defer an issue or idea, call
toda_addin the same turn — never "at the end of the session". When starting a task, calltoda_listand mention open items whoserevive:trigger matches the task. When a fix lands, calltoda_setwith statusxin the same turn.
Build
npm install
npm test
npm run buildRegister the server (user/global scope, so every project gets it)
Absolute path to the built entry: <this repo>/dist/main.js.
JSON form (Claude Desktop claude_desktop_config.json, Cursor mcp.json, ZCode/Claude Code mcpServers config):
{
"mcpServers": {
"toda": {
"command": "node",
"args": ["C:\\path\\to\\TODA\\dist\\main.js"]
}
}
}CLI form (Claude Code / ZCode — confirm exact flags with --help first):
claude mcp add --scope user toda -- node "C:\path\to\TODA\dist\main.js"
zcode mcp add --scope user toda -- node "C:\path\to\TODA\dist\main.js"Notes
TODA.mdis resolved from the session's working directory; set theTODA_FILEenv var in the server config to pin an explicit path.Closed items stay in the hot file until
toda_prunearchives them; the archive is only read wheninclude_archiveis set, keeping the token bill bounded. Prune counts from the item's opened date (the spec's documented approximation).References are stored as plain text and never resolved (no git/GitHub calls).
Available Tools
5 toolstoda_addA
Append a deferred item to TODA.md (auto-creates the file)
Inputs: what (required), revive_when (required), why_deferred (required), ref, +2 more.
toda_initA
Create TODA.md for the current project (idempotent); returns the convention-file snippet
Inputs: no named parameters.
toda_listC
List deferred items (default: open + sleeping)
Inputs: ref, status, keyword, include_archive.
toda_pruneA
Move done items older than N days into TODA-archive.md
Inputs: older_than_days.
toda_setC
Update an item status (moves it between sections)
Inputs: id (required), status (required), ref, note.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool maps to a distinct action on the TODA.md lifecycle: init (create file), add (append item), list (read), set (change status), prune (archive). There is no overlap — 'add' creates items while 'set' only transitions status, and 'prune' is clearly scoped to done items.
All tools follow the exact pattern toda_<verb> in snake_case with short, predictable verbs. The shared prefix also makes the tool family easy to discover and group.
Five tools is a tight, well-scoped surface for a deferred-item tracker: one per lifecycle stage (init, add, list, update, archive). No tool feels redundant or filler.
The core lifecycle (create file, add, list, change status, archive) is covered, but there is no way to delete an item outright or edit an item's text without archiving. These are minor gaps an agent can work around by setting status or manual edits.
Maintenance
Related MCP Connectors
Issue tracker for coding agents: a real backlog, plus a risk-ranked review of every change.
Task and bug tracker for AI coding agents: 75 tools to file, triage and update work.
Track issues, projects and dependencies with your agent in a workspace you control.
Personal project management with AI agents: numbered tickets, statuses, files, a thread per ticket.
Related MCP Servers
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI-native task management using plain markdown files to create, update, query, and organize Epics, Stories, Tasks, and Milestones without requiring a database.-
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to read and manage a Git-native decision ledger, providing tools for querying decisions, evidence, cross-repository workspaces, validation, and commit tracing, all operating locally and without a cloud service.MIT
- AlicenseAqualityBmaintenanceEnables an AI coding agent and developer to keep a shared live markdown record of goals, tasks, detours, ideas, and standing instructions across long sessions and context compression. It provides MCP tools and a dashboard to track progress, branch and merge detours, and maintain focus.16847 npm1PolyForm Noncommercial 1.0.0
- AlicenseBqualityBmaintenanceEnables coding agents to persist and retrieve ADR-style decisions and machine-checkable constraints as git-friendly markdown in a repository, linked to requirement ids, tests and commits. Agents can pull relevant context before a task, check a proposed change against accepted constraints before committing, and record, supersede or search decisions over a local stdio connection.723 npmMIT