factotumThe system of record for agent-run operations.
Your agents forget. This doesn’t.
Tasks, deadlines, recurring checks — and every change an agent makes, written down with who, what, and when.
Connect
https://factotum.zyxt.com/mcp
Paste into Claude. No account, no card.
Claude · ChatGPT (Enterprise) · any MCP client
Then just ask
- What’s due today?
- Mark the AP run done.
- Show me what I skipped.
- What changed while I was out?
- Undo the last change.
What it records
recordtask #112
Mark the AP run done.
Task #112 is now ✓ done: Weekly AP run — pay open vendor invoices
2026-08-28 09:14 | complete | claude | {"status":["open","done"]}
2026-08-21 09:07 | complete | claude | {"status":["open","done"]}
2026-06-05 08:41 | create | matthew | {"recur_spec":"FRI","priority":1}
A spreadsheet doesn’t know who changed what, and it can’t undo. Every write here is a record — attributed, historied, reversible in one call.
Built to be trusted with writes
Refuses corrupt writes
Bad input is rejected at the door, not written and cleaned up later.
Full change history
Every write is recorded with what changed, when, and which agent did it.
One-call undo
Reverse any change in a single call. No manual repair.
Private by construction
Encrypted per workspace
Task text is encrypted at rest with a key unique to your workspace. A database dump reads as ciphertext — even to another tenant’s key.
Isolation the server enforces
Every query must carry your workspace’s identity. One that doesn’t is refused by the server itself — not just avoided by convention.
Numbers that say nothing
Task numbers are private to your workspace. Yours start at #1 and reveal nothing about anyone else’s usage.
Never trained on
Your records are never used to train models — ours or anyone else’s. Privacy policy
Free to 1,000 tasks.
Full read and write until then. After 1,000 tasks, everything keeps working — reading, editing, undo — except creating new ones.