Update and delete both take flags for whether the change reaches future occurrences or all of them, which is exactly the distinction that goes wrong when a subscription changes price mid-year. Category deletion can hand its movements to a replacement category, so tidying the chart of accounts does not cost historical classification. One boundary is stated outright: a transaction listing returns at most 300 rows, so a long history is read in shorter date ranges rather than in one call.
A client for the Organizze personal finance service, covering accounts, categories, credit cards, transactions, transfers, budgets and balances.
- Bank accounts listed, created, inspected, updated and deleted, with one of them marked as the default.
- Categories with a colour and a parent, and deletion that can name a replacement so existing movements keep a classification.
- Credit cards with card network, limit in cents, closing day and due day; their invoices for a date range, or only the open and future ones; and the payment entry behind an invoice.
- Transactions listed by account and date range, created as one-off, recurring or instalment entries with tags, notes and a paid flag, and updated or deleted for one occurrence, all future ones, or the whole series.
- Transfers between two accounts — credit cards are not accepted — listed, created, updated and deleted.
- Budgets for the current month, a named month or a whole year, and a balance report across a period at a periodicity you choose.
An Organizze account, with the login email in ORGANIZZE_EMAIL and its key in ORGANIZZE_API_KEY.
One command plus a key — ORGANIZZE_EMAIL=seu@email.com ORGANIZZE_API_KEY=sua_chave uvx mcp-organizze, then supply credentials