Myfinance MCP

Totals for a period, computed server-side in the user's base currency. Breaks down expenses (default) or income: 'how much did I spend on X in July', 'what does my June income consist of'. Supports category drill-down (category=subscriptions + group_by=merchant), exclusions (exclude_categories), week-by-week views (group_by=week), comparison with the period before (compare=previous: 'how does this week compare to last week') and totals in another currency (currency=USD).

Find records: 'what was that 40 eur charge', recent spending, by category or merchant. Newest first. total = all matches; when has_more is true, call again with offset=next_offset to page (never treat count as the total).

Month-over-month expense/income dynamics, optionally for one category or scope.

Import bank-statement / statement-screenshot rows in bulk. ALWAYS send the ENTIRE statement as ONE call with the full transactions array (up to 500 rows) - never split into chunks, never log rows one-by-one via log_expense. If one statement truly cannot fit in a single call, EVERY row of EVERY chunk must carry external_id (bank reference; or a statement-scoped row id such as '2026-09:r017' - bare row numbers repeat in every statement) - rows without external_id are keyed by amount+date+occurrence WITHIN one call, so identical rows arriving in different calls are indistinguishable from re-impor…

Anchor an account's REAL balance at end of a date (from the bank app). Balances are then snapshot + later flows.

Record ONE purchase, bill, or receipt. Negative amount = refund to the same category. NEVER use this for bank-statement rows or any batch of 3+ records: use import_transactions with the whole array instead (one-by-one logging hits the per-turn tool limit).

Record incoming money: salary, client payment, gift.

Move money between OWN accounts: card to brokerage, cash withdrawal, currency exchange. Never counted as spending or income.

Money accounts (bank, card, cash, investment), one action per call. create: name, type, currency (entity optional). update: account plus new_name, type, currency or entity (history stays; an entity change affects future rows). set_balance: account, amount, optional currency and date: the REAL balance from the bank app at the end of that date; balances are this snapshot plus later flows. merge: source into target, moving every row, dropping duplicates (same type, currency, amount, date within dedup_window_days; the row with a bank reference wins) and deleting source; typical for a statement-imp…

Merge one account into another: moves all transactions to the target, de-duplicates rows present on both sides (same type, currency, amount and date within dedup_window_days; the row with a bank reference wins and absorbs the other's category), rewrites transfer references, then deletes the source account. Typical use: a hand-made statement-import account and a live bank sync account tracking the same real bank. Run with dry_run=true first and show the counts to the user.

Health check for the MyFinance MCP connection. Returns the signed-in account email - call this when the user asks which account is connected.

Monthly spending cap, overall or per category, in the user's base currency.

Save, change or remove a payment the user expects again (a subscription, rent, a bill). Saved ones show in get_recurring and in the email summary's 'Coming up'. With auto_log=true the expense is written on each date automatically: only for a fixed amount charged in this currency, and only for users who log by hand (refused while a bank or ZenMoney sync is connected: the sync brings the charge). A statement import merges an auto-logged row with the bank's row of the same amount within two days. Saving again under the same name changes it; remove=true deletes it (expenses already logged stay).

Pull booked transactions and balances from the connected bank (via connect_bank; read-only, incremental, safe to re-run). First sync imports months_back of history (default 3; banks may return less). Equal-amount same-day debit/credit pairs across the user's own synced accounts are merged into transfers. Categories come from the user's remembered per-merchant fixes first, then MCC; the rest land in 'other'. The server also auto-syncs healthy connections roughly daily; run this only for immediate freshness or right after connecting. If the same real bank account is also connected via ZenMoney i…

Pull transactions, accounts and balances from the linked ZenMoney account (read-only, incremental after the first run, safe to re-run). First sync imports full history unless months_back is set. dry_run previews transaction changes (account mapping is still saved). Report includes unmapped ZenMoney tags: those rows land in category 'other' for the user to review. If the same real bank account is also connected via connect_bank its transactions WILL duplicate: relay any overlap_warnings from the response to the user and offer to disable one side (action=set_account_sync).

Rename an account or change its type, entity or main currency. Transactions keep their history; an entity change only affects future transactions.

Change base currency (recomputes all historical stats at each transaction's original date rate), timezone, or the email summary (email_digest).

Fix a logged record: wrong category, amount, merchant, date, account, personal/business scope, or type. type=transfer + counter_account converts a mislogged row into a transfer between own accounts (e.g. a cash withdrawal into a transfer to Cash). counter_transaction_id instead GLUES TWO EXISTING rows (one expense + one income on different own accounts) into ONE transfer - use it when a currency exchange, own-account top-up, or cash withdrawal produced two separate rows. Category fixes on rows with a merchant are remembered: future bank syncs of that merchant reuse your category.

Read-only sync with a ZenMoney account (zenmoney.app international and zenmoney.ru both work; the backend is detected). action=paste_token stores the user's personal ZenMoney API token: free at zerro.app (log in choosing YOUR ZenMoney version, then open zerro.app/token and copy it). action=sync pulls transactions, accounts and balances (incremental, safe to re-run; the first sync takes the full history unless months_back is set; dry_run previews; unmapped ZenMoney tags land in 'other' for the user to review). action=status: connection health and synced accounts. action=set_account_sync with ac…