Myfinance MCP Server

Connect Myfinance to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Personal finance by conversation: expenses, receipts, statement import, budgets, net worth. The myfinance mcp server is what makes that connection.

What the server does

A remote MCP server for personal finance - log expenses by talking, snap receipt photos, import whole bank statements, and get budgets, trends and net worth computed for you, in any currency.

• No app, no forms, no spreadsheet. — "Spent 24.50 eur on groceries at Lidl" is the whole workflow
• Every number is computed in SQL. — The server owns the data and the math; the AI reads the results, it never guesses arithmetic
• Any currency. — Transactions keep their original currency; the FX rate to your base currency is frozen at transaction date, so history never rewrites itself
• Statements in one message. — Drop a CSV/PDF export; hundreds of rows import in one call with idempotent deduplication, hand-logged twins merged, totals reconciled
• Personal vs business. — Entity tag on accounts and transactions, filterable everywhere, included in CSV export for your accountant
• Dashboards in the chat. — Budgets, trends, summaries and accounts render as interactive panels (MCP Apps) right in the conversation

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• log_expense — Record one purchase, bill or receipt (negative amount = refund)
• log_income — Record income: salary, invoice, refund, interest
• log_transfer — Move money between accounts, cross-currency supported; never counts as spending
• log_balance — Anchor an account's balance at a date; later flows compute from the snapshot
• import_transactions — Bulk statement import (up to 500 rows/call): dedup by bank reference or derived key, twin merge, reconciliation check
• create_account — Create a bank / card / cash / investment account with currency and personal/business entity
• update_account — Rename an account or change its type, entity or main currency
• delete_account — Delete one money account (with its transactions after explicit confirmation)
• merge_accounts — Fold one account into another: move rows, de-duplicate both sides, rewrite transfers
• get_accounts — All accounts with balances and net worth, converted to base currency
• get_summary — Period totals by category, merchant or month; expense or income breakdown, category drill-down and exclusions
• get_transactions — List and filter raw transactions

Credentials and setup notes

Configuration is passed through the environment: BASE_URL, DATABASE_URL, GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, RESEND_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Myfinance.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Myfinance's toolset — log_expense, log_income, log_transfer and 11 more — is a fair guide to whether it matches your workflow. It is maintained by alex-odoo; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.