Todox MCP server

todox

Working memory for developers and their agents. Not a checklist — a log your next session can actually resume from.

An issue tracker is written human-to-human. todox is written agent-to-agent, with a human reading over its shoulder. Every task carries the decisions behind it, the approaches that failed, the questions still open, and the note the last session left behind.

A fresh agent calls getcontext, reads that, and starts where the last one stopped — without walking into a wall somebody already hit. The briefing is capped rather than unbounded, in rows and* in bytes, and it reports what the caps left out instead of trimming in silence. Nothing is ever cut mid-sentence: every record comes back named and dated with its first line, and a body of null means the budget was spent, not that the record is empty.

What goes in a log

Two things fall out of treating the log as the product:

side that can see them — the agent — and the server stores the hashes and compares. If the code moves on, get_context says the note may be lying. Until an agent has actually looked, the note is marked as never checked rather than claimed to be fresh: context that lies is worse than none, and that includes lying about how sure we are.

• Stale context is flagged, and never faked. Linked files are hashed by the

event, so what did I finish today, how long did it take, which model did it is a query rather than archaeology. A task set doing and walked away from counts as the morning it was set, not the weeks since -- and the report says how much it left out, rather than folding it into the headline.

• Reports come from the log, not from commits. Every status change is an

hashes are readable from the other end: getfilecontext takes a path and answers with the tasks that touched it, their dead ends, and any standing note attached to it. Paths are folded to their repo-relative form, so a link made on one machine is found from another.

• A file can be asked what is known about it. The same links that carry the

Why not the memory your agent already has?

Claude Code writes its own notes now (auto memory, on by default since February 2026), and Cursor and Codex have theirs. Use them: they are good at remembering that you prefer pnpm. What their documentation says, in its own words, is that they are per repository, per machine ("machine-local … not shared across machines") and per tool, and shared with nobody ("just you"). todox is for what falls outside that line:

note left on the laptop is read on the desktop.

• Two machines, one log. A repository is identified by its remote, so the

MCP; the handoff one leaves is what the next one reads, whichever it is.

• Every agent, one log. Claude Code, Codex, Cursor and VS Code all speak

what and which model did it.

• The people, too. A project can be shared, and the log carries who wrote

ends as their own kind, a report read from the log, a stale note that says so — and a briefing that reports what its caps left out.

• A shape a note in a file does not have. Tasks that open and close, dead

Try it

Shortened. The full README is on GitHub.