Documentation

Connect in about two minutes

Factotum is a remote MCP server that stores tasks and the full history of every change made to them. You connect it to an AI assistant once, and from then on the assistant reads and writes your records on your behalf — there is no separate app to open.

Connect

Paste this URL into your MCP client as a custom connector:

https://factotum.zyxt.com/mcp

In Claude Code:

claude mcp add --transport http factotum https://factotum.zyxt.com/mcp

In Claude Desktop, go to Settings → Connectors → Add custom connector and paste the same URL.

Tools

Eight tools. Four read, four write. Every write is recorded in an append-only history.

Tool	Kind	What it does
`task_list`	Read	List and filter tasks by lane, priority, tag, assignee, due or check date, or free text.
`task_get`	Read	Full detail for one task, including its recent change history.
`daily_digest`	Read	The standup view: what fires today, what is overdue, what is due soon, P0s, bugs, and recent completions.
`task_create`	Write	Create a task. Attribution is set server-side from your token, never from the request.
`task_update`	Write	Change fields. Only the fields you pass are touched; pass null to clear one.
`task_complete`	Write	Mark a task done.
`task_reopen`	Write	Reopen a task that was completed or expired.
`task_expire`	Write	Retire a task whose window has passed.

There is no delete tool, deliberately. task_expire retires a task without destroying it, so the record and its history survive. Nothing you file is ever silently lost.

A worked example

Once connected, you talk to your assistant normally. A typical exchange:

You: “Add a task to check the Klaviyo flow on Friday, high priority.”
Assistant: calls task_create and reports back what was actually stored — lane, priority, check date, tags — so a dropped field is visible immediately rather than weeks later.
You: “What’s due today?”
Assistant: calls daily_digest and summarizes what fires today, what has slipped, and what is coming.

Two clocks

Tasks carry two independent dates, and keeping them separate is what stops a standup from lying to you:

Check date — resurface this for attention on that day. It is not late; it is ripe.
Due date — this is genuinely late after that day.

Recurrence

Recurring work is first class: daily (optionally until a date), weekly on named days, monthly on a day of the month, or a one-time date. The server decides what fires today, so every client agrees. Recurring tasks are not completed away — they fire again next cycle.

Limits

The free tier includes full read and write access up to 1,000 tasks. Past that, reading, editing, completing and undo all keep working; only creating new tasks needs a paid plan. There is also a technical rate ceiling to protect the service from runaway agents, separate from your plan.

Support

Email matthew@zyxt.com, or see the support page.