log_entry

MCP tool from Todox by beydemirfurkan

Append one of the five kinds. answersentryid closes a question — the only thing that does.

How to use it

Project documentation lists log_entry for the Todox MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), then check which tools your installed version makes available. Tool availability can depend on configuration and credentials. A server handshake does not verify this tool’s behavior. See the full listing for setup details.

Install Todox

$npx -y https://github.com/beydemirfurkan/todox/releases/latest/download/todox-mcp.tgz
FULL TODOX LISTING

Other tools in Todox (14)

activity_report

Today / this week / any window: durations, models, importance, decisions, dead ends, open questions. format:"markdown" is written to be pasted into a status update.

add_context

Knowledge that outlives a task; omit the project to make it account-wide.

create_task

Capture work. Pass cwd or an explicit project; the tool schema requires one before the call runs. Registering a new one also needs reporoot or repourl. The receipt returns the task path and body length without echoing the body.

delete_entry

For an entry that was wrong when it was written. One overtaken by later work is history, not an error — append instead.

delete_project

The way back from a mistyped cwd. Takes the project and everything under it; confirm must be the slug.

get_context

Call this first. Standing rules, project decisions and gotchas, every open task with its decisions, dead ends, questions, files and last handoff — plus stale-file warnings. Resolves a project from a slug, a name, or any path inside it. Capped in rows and in bytes, never truncated: every record keeps

get_context_note

One note in full, for the ones whose body the briefing capped and for reading past a search snippet. An entry the budget did not reach is read with gettask.

get_file_context

What is known about one file: the tasks that touched it with their dead ends, and the notes attached to it. Absolute or repo-relative; both find a link made on another machine.

get_task

One task with its log and linked files.

link_files

Attach paths with their hashes to a task or a context note. Safe to call again for the same file.

merge_projects

The way back from one repo registered twice. Moves tasks, notes and paths into the surviving project; confirm must be the slug of the one being merged away.

report_file_hashes

Hosted only: what the linked files look like on disk now. The local process does this for itself.

search

Across all your projects, ranked by relevance. Ask the question in words; quote a phrase to require it. Stems English and Turkish, and still matches the middle of an identifier. Words that only one of the two languages treats as noise are dropped, so a question does not match every record containing

update_task

Status, title, body, priority. Moving to doing/done is where durations come from.