finance-sync

finance-sync

Ingestion status and reindexing for the money-manager MCP server. The server picks up the newest .mmbak in the drop folder automatically — there is nothing to "import"; this skill checks freshness and refreshes the OCR index.

Status check

Call backup_status and report:

• backup filename, size, active transaction count, date range, main currency
• Freshness warning: if the newest data date (or the filename's embedded date, e.g. 20240115_093000.mmbak) is older than ~10 days, tell the user to export a fresh backup in Money Manager and upload it to the drop folder.

Receipt reindex

After the user drops new receipt photos (or asks to reindex):

1. Call reindex_receipts (add force=true only if the user explicitly asks for a full rebuild — a normal run hash-skips unchanged images and is cheap).
2. Report the counts: seen, skipped, ocr_ok, ocr_failed, indexed_total.
3. If ocr_failed > 0, say how many and suggest re-running; repeated failures on the same files are worth listing.

Incremental runs are near-instant; a large batch of new images takes roughly 1–3 s per image on CPU.

Full / first-time index build

A full build (thousands of images, an hour or more) is too long for one tool call, but you can still run it:

• If you have shell access: run the CLI as a background job and report the final stats when it finishes: money-manager ocr-index (env: MONEY_PHOTOS, MONEY_INDEX). Safe to interrupt — re-running resumes via hash-skip.
• MCP-only: loop reindex_receipts(limit=50) — each call OCRs at most 50 new images (~1–2 min) then returns stats. Keep looping while ocr_ok + ocr_failed > 0, reporting cumulative progress against seen; when a call comes back all-skipped, the build is complete.

Index ownership

Every machine owns and writes its OWN index; indexes are disposable replicas, never a shared writable file.

• Primary machine (authoritative): builds and reindexes locally (outside any sync folder), then copies a snapshot into the synced folder (Money Manager/receipt_index.db) for other machines to seed from.
• Other machines / agent hosts: seed a local writable index once from the synced snapshot, then run incremental reindex_receipts locally. The photo source is read-only; seeded indexes diverging from the primary's is fine — every index rebuilds from source at any time.
• Never point MONEY_INDEX at a live sync folder or network share during a build: sync clients upload half-written databases and can create conflict copies.