Finance Toolkit
500+ transparent financial methods calculated from raw statements, not third-party endpoints.
Description from the maker (original English)
Read-only MCP server for the Monzo banking API: OAuth, local transaction cache, spending analysis.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"monzo": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/partymola/monzo-mcp:v0.13.0"
]
}
}
}Run this in your terminal
claude mcp add monzo -- docker run -i --rm ghcr.io/partymola/monzo-mcp:v0.13.0Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"monzo": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/partymola/monzo-mcp:v0.13.0"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"monzo": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/partymola/monzo-mcp:v0.13.0"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account partymola, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.13.0) reached the registry 3 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.
In the same category: Finance Toolkit, SolidInvoice, Korea Tax Calculator
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
500+ transparent financial methods calculated from raw statements, not third-party endpoints.
Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.
Korean tax calculation and tax-audit judgment MCP: 96 tools with statutory citations.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
MCP server for the Monzo banking API. Read-only access to accounts, balances, pots, transactions, and spending analysis - all through Claude Code or any MCP client.
Unlike other Monzo MCP implementations that use raw bearer tokens (which expire in 6 hours), this server handles full OAuth with automatic token refresh.
monzo_sync by hand| Tool | Description | Data source |
|---|---|---|
monzo_list_accounts | List accounts with types and IDs | Live API |
monzo_get_balance | Current balance and spend today | Live API |
monzo_list_pots | Savings pots and balances | Live API |
monzo_sync | Sync transactions to local cache | Live API -> SQLite |
monzo_list_transactions | List/filter cached transactions | Local cache (auto-syncs if stale) |
monzo_search_transactions | Search by merchant/payee/description/notes | Local cache (auto-syncs if stale) |
monzo_spending | Spending analysis with category breakdown | Local cache (auto-syncs if stale) |
git clone https://github.com/partymola/monzo-mcp.git
cd monzo-mcp uv venv --python 3.13 .venv uv pip install -e .
This package is not on PyPI - the name belongs to an unrelated project. A container image is published instead; see Docker.
Go to developers.monzo.com and create an OAuth client:
http://localhost:6600/callbackmonzo-mcp auth
This opens your browser for Monzo OAuth. After authorizing, approve the login in your Monzo app within 5 minutes for full transaction history access (Monzo's SCA window).
claude mcp add -s user monzo -- /path/to/monzo-mcp/.venv/bin/monzo-mcp
On Windows the console script is at .venv\Scripts\monzo-mcp.exe.
In Claude Code, run monzo_sync to populate the local transaction cache. Do this immediately after auth to take advantage of the SCA window (up to 11 months of history).
Images are published to ghcr.io/partymola/monzo-mcp. Tags carry a v prefix (:vX.Y.Z), and :latest follows the most recent release.
The container needs a volume. Credentials and the transaction cache live under /data; with nothing mounted there, the container still starts and every tool reports that it is not configured, and anything you authorise is lost as soon as the container is replaced.
First register an OAuth client as described in Setup step 1 - auth prompts for the Client ID and secret, and there is no way to supply them later. The redirect URL is http://localhost:6600/callback, the same as a source install.
Authenticate once, into a named volume. Decide before you run this whether you want a bind mount instead - switching afterwards means authorising again:
docker volume create monzo-mcp-data
docker run --rm -it \ -v monzo-mcp-data:/data \ -p 127.0.0.1:6600:6600 \ ghcr.io/partymola/monzo-mcp:latest auth
The published port is needed only for this step, so the OAuth redirect can reach the container. Binding it to 127.0.0.1 keeps the callback listener off your network. No browser opens - the container has none - so copy the URL it prints. Then approve the login in your Monzo app within 5 minutes (see Monzo SCA window).
Then register the server, reusing the same volume:
claude mcp add -s user monzo -- \
docker run --rm -i -v monzo-mcp-data:/data ghcr.io/partymola/monzo-mcp:latest
-i is required - the server speaks JSON-RPC over stdin and stdout.
Sync straight away. The 11-month backfill closes 5 minutes after you approve in the Monzo app (see Monzo SCA window), and this route is longer than a source install - so call monzo_sync as soon as the server is registered. Miss it and you silently get 90 days instead, with no error.
To keep the files somewhere you can read them, use a bind mount instead of a named volume. The container runs as root and writes credentials owner-only, so without --user they end up root-owned:
mkdir -p ~/monzo-mcp-data/config
docker run --rm -it \ -v ~/monzo-mcp-data:/data \ --user $(id -u):$(id -g) \ -p 127.0.0.1:6600:6600 \ ghcr.io/partymola/monzo-mcp:latest auth
Pass the same -v and --user to the server command. Create the directory first - --user against a named volume fails, because the volume initialises root-owned from the image.
monzo-mcp Start the MCP server (stdio transport)
monzo-mcp auth Interactive OAuth setup (opens the browser) monzo-mcp --version Print the installed package version
All configuration is via environment variables (optional):
| Variable | Default | Description |
|---|---|---|
MONZO_MCP_CONFIG_DIR | /config/ | Directory for OAuth credentials and tokens |
MONZO_MCP_DB_PATH | /monzo.db | Path to SQLite transaction cache |
MONZO_MCP_CALLBACK_HOST | localhost | Interface the auth callback server binds to. The redirect URI is unaffected |
The container image sets the first two under /data, because the package-relative defaults resolve into the interpreter's lib directory there, which cannot be mounted. It sets the third to 0.0.0.0, because a published port arrives on the container's bridge interface and a localhost bind refuses it.
Credential files (created by monzo-mcp auth):
config/monzo_client.json - OAuth client ID and secretconfig/monzo_tokens.json - Access and refresh tokens (auto-refreshed)Monzo's Strong Customer Authentication (SCA) limits transaction history access:
The local SQLite cache preserves all synced transactions permanently, so run monzo_sync promptly after monzo-mcp auth.
To backfill a specific range, pass since to monzo_sync - an ISO date (2026-01-01) or datetime (2026-01-01T14:30:00Z). Within the last 90 days this works at any time. Reaching further back only works inside the SCA window; outside it the request is refused, and the sync quietly fetches only what is newer than the newest cached transaction.
Older cached transactions gain fields added in newer versions (e.g. counterparty/payee details on bank transfers) only when re-fetched, which a post-auth full sync does for the history it re-pulls.
config/ directory (gitignored)monzo-mcp auth and approve the login in the Monzo app within 5 minutes, then sync straight away (see the SCA window above).monzo-mcp auth to re-authorise.monzo_sync to see the error. Run monzo-mcp auth only if it says the stored credentials were refused or cannot be used, or that the login needs approving in the Monzo app, and then call monzo_sync once./data. See Docker; the same volume must be passed to the auth run and to the server.-p 127.0.0.1:6600:6600).See CONTRIBUTING.md for development setup, the test workflow, and the pre-commit hook. Changes are tracked in CHANGELOG.md.
GPL-3.0-or-later. See LICENSE.