Blog7 min read

Finance MCP servers compared: which one should you connect?

Six MCP servers that put your own money in your AI, judged on the two things that actually differ - where the data comes from, and what happens when the model wants to change something.

A year ago "connect my budget to my AI" meant copying a CSV into a chat window. Now there are a dozen MCP servers for it, and picking between them is genuinely confusing, because they all describe themselves the same way.

We build one of these, so read this knowing that. What we have tried to do is describe the others accurately enough that you can tell when one of them is the better answer - and say plainly when it is.

Everything below is checked against each project's own documentation or repository, linked as we go. Where a claim is ours rather than theirs, it says so.

The two questions that actually separate themLink to this section

Almost every difference that matters comes down to two things.

Where does the data come from? Either the server reads a ledger that a bank feed fills in for you, or it reads one you fill in yourself. That single choice decides which countries a product can serve, what it costs to run, and what happens on the day an aggregator drops your bank.

What happens when the model wants to change something? There are three real answers, and the marketing language rarely distinguishes them:

  • Read-only. The model can look and never touch. Safe by construction, and it means "add that coffee" is not a thing you can do.
  • Direct write. The model calls a tool and your ledger changes. Fast, and it trusts the model to have understood you.
  • Confirm-first. The model drafts, you approve, and only then does anything change.

Almost every argument about "is it safe to give an AI my finances" is really an argument about which of those three you are running.

At a glanceLink to this section

ServerData sourceWritesHostingSource
HundoManual, receipts, imports, agent draftsConfirm-first, alwaysRemoteClosed
BonsaveLinked banks and brokeragesNone - read-onlyRemoteClosed
OpenBudgetPlaid, US institutionsDirectRemoteOpen
Actual Budget MCPYour Actual Budget fileDirect, except deletesLocalOpen
Expense Budget TrackerWhatever you or the agent insertsDirect, via SQLRemote or self-hostOpen
EnvelopeBudgetYour EnvelopeBudget accountNone - review onlyRemoteClosed

BonsaveLink to this section

Bonsave links your banks, brokerages, credit cards and loans, and exposes eight tools - accounts, net worth, net worth history, transactions, spending, budgets, holdings and charts. Its own page describes them as strictly read-only: it "cannot move money or make changes of any kind."

That is a coherent position, and for a lot of people it is the right one. If what you want is to ask questions about numbers a bank feed already keeps accurate, the safest possible answer is a server that cannot write, and Bonsave is that.

MCP access sits in its Pro and Ultra plans, with a 14-day trial.

OpenBudgetLink to this section

OpenBudget syncs from US institutions through Plaid - transactions, balances, net worth, credit cards, loans, mortgages, investment holdings - and lets you add cash, real estate and private holdings by hand on top.

It writes, and the writes apply directly: create_transaction, update_investment_holding, delete_transaction and so on. Its README is careful about the boundary, and the boundary is a good one: Plaid connections are read-only, it never stores your bank credentials, and your assistant "cannot move money or place trades." Every write stays inside your OpenBudget account.

Pricing is public: $60 a year or $9.95 monthly, with an Investor tier at $99 a year, both after a 7-day trial.

Pick this one if you are in the US and want the feed to do the typing. Automatic bank sync is a real advantage and Hundo does not have it. The catch is the one every aggregator has: it is Plaid, so it is US institutions.

Actual Budget MCPLink to this section

This one connects to Actual Budget, the open-source envelope budgeting app, and it is the most thoughtful of the write-capable servers.

It runs locally, from npm or a container, against your own Actual file. It has real analysis tools - projections, category trends, budget vs actual - not just lookups. And it takes safety seriously in two ways worth copying:

  • Every delete previews before it deletes. The tool refuses to destroy anything on the first call, reports what would be lost, and stops.
  • ACTUAL_READ_ONLY=1 hides the write tools from the model entirely, so they are not registered at all.

That second one is a good idea and we did not have it when this page was first written. We do now - Settings has a read-only toggle that stops the change tools being registered at all, so a connected model never sees that writing is possible. Credit where it is due: we copied it from here.

The distinction against Hundo is narrower than it first looks, and worth stating precisely: Actual's confirmation covers deletes. Creating a transaction, or editing one, applies straight away. Hundo's covers every write, edits and creates included. Whether that difference matters depends entirely on whether you think a wrong number is worse than a missing one.

Pick this one if you already use Actual Budget, or want everything on your own machine. It is free, open source, and nothing leaves your computer.

Expense Budget TrackerLink to this section

This is the most different design in the list, and the most interesting one. It is a self-hosted, open-source tracker on Postgres, with multi-currency reporting - and its MCP surface is essentially the database: get_schema, list_workspaces, sql_query, sql_execute.

You are handing the agent SQL. That is enormously flexible - any question you can express, it can answer, and its own documentation suggests sending the agent bank statement PDFs and CSVs and letting it insert the parsed rows through the SQL execute endpoint. Write access is controlled by scope.

It is also the opposite end of the safety axis from confirm-first, and honestly so: an agent with sql_execute can do anything a SQL statement can do.

Pick this one if you want maximum flexibility and are comfortable owning the consequences. Open source, self-hostable, no per-seat pricing.

EnvelopeBudgetLink to this section

EnvelopeBudget's server is remote and, by its own description, for securely reviewing authorised account data from a compatible assistant. Review, not change.

We have less to say about this one than the others because there is less published about it - which is itself worth knowing before you build a workflow on it.

HundoLink to this section

Ours, so treat the framing with suspicion and check the tool list yourself.

No bank connection at all. Hundo does not ask for banking credentials and does not use an aggregator. Entries are typed, photographed, forwarded to a personal receipts address, imported, or drafted by the agent and confirmed by you.

That is a genuine cost. Nothing arrives on its own, and if you want a feed to do the typing, one of the servers above is a better fit. What it buys is that Hundo works in any country - including every one Plaid does not cover - and that there is no bank credential anywhere in the system to worry about.

Every write is confirm-first, not just deletes. Nine tools draft and return a proposal; one tool, confirm_proposal, commits it after you approve in the conversation. An unconfirmed proposal expires. Eleven read tools cannot change anything, and the SQL query tool runs as an unprivileged database role scoped to your own rows.

Multi-currency is the part we would defend hardest. Over 160 currencies, converted at the rate for the day a transaction happened rather than today's, with accounts, assets and individual budgets each able to hold their own currency while net worth still reports in the one you think in.

Pricing is pay-what-you-want above a floor, and the tracker itself is free and uncapped whether or not you ever connect an AI.

So which oneLink to this section

Roughly:

  • US, and you want the bank feed to do the work: OpenBudget, or Bonsave if you would rather the model could not write at all.
  • You already use Actual Budget, or want it all local: Actual Budget MCP.
  • You want to hand the agent SQL and own the consequences: Expense Budget Tracker.
  • You are outside aggregator coverage, juggling currencies, or you want every change to stop and ask: that is the gap Hundo was built for.

The honest summary of the category is that it is early and the products are less alike than their descriptions suggest. Read the tool list before you connect anything - it tells you more about what a server will do to your money than any landing page, including ours.

Checked 2026-09-10 against each project's own documentation, linked throughout. This category moves quickly, and a comparison that goes stale is worse than none - if something here no longer matches what a project actually does, the Contact link in the footer reaches us and we will correct it.