BankMCP™

Your AI now reads your bank. Ask it anything about your accounts. Read-only, self-hosted, one user. Standard MCP; tested with Claude and Ollama.

BankMCP™ is not a bank. It is a small open-source server you host yourself (npm package bankmcp). It connects to your banks through Enable Banking, which wraps 2,700+ European banks in one PSD2 API, and exposes them to any MCP client as a connector. Read-only, no payments, no third party holding your data.

"Has the invoice from Acme been paid?" · "What did we spend on groceries in August?" · "Which subscriptions am I paying for, and what do they cost per year?" · "Tell me when my balance drops below 5,000."

How it works

Your assistant ──OAuth──▶ your BankMCP™ server ──JWT──▶ Enable Banking ──PSD2──▶ your bank

• Your assistant (Claude, ChatGPT, Cursor, or any MCP client) talks to your server as a connector. You sign in once with a password; tokens handle the rest.
• Your server holds the Enable Banking application key, the bank consents and your account ids. It does not store balances or transactions and sends no telemetry.
• Enable Banking is the licensed provider between your server and your bank. Every balance and transaction you ask for passes through their servers on the way to yours; they do not store it, and they do not see your bank credentials, since you log in at your bank's own site. This hop is how PSD2 works and is the one part of the chain that is not on your machine.

Setup

Two ways to run it. Both need a free Enable Banking account and about ten minutes.

• On your own machine for Claude Desktop, Claude Code, Cursor and other desktop MCP clients. Nothing to deploy, no password.
• On a small server when you want it in claude.ai or on your phone.

On your own machine

The server and its state live on your computer, and no AI vendor or app maker sees your data. The bank connection is not on your computer: it goes through Enable Banking, as described above.

Requires Node 24 or newer. Add BankMCP™ to your client:

Claude Code:

claude mcp add bankmcp -- npx -y bankmcp

Claude Desktop: download bankmcp.mcpb and open it; Claude Desktop installs it as an extension. Or add it by hand in claude_desktop_config.json:

{ "mcpServers": { "bankmcp": { "command": "npx", "args": ["-y", "bankmcp"] } } }

Cursor and others: the same command, npx -y bankmcp, as a stdio server.

Then ask your assistant anything about your bank. It will answer with a localhost address. Open it: the setup page lists the values to register an application at Enable Banking, then takes the application id and the key file. Your browser will warn once about the certificate on localhost, which the server made for itself because Enable Banking requires https for the bank redirect. Continue past it. Say "connect my bank" and log in at your bank.

To avoid the warning altogether, use a certificate your browser already trusts: mkcert makes one with mkcert localhost 127.0.0.1; point TLS_CERT_PATH and TLS_KEY_PATH at the two files and the server uses them instead of generating its own. BankMCP™ itself does not touch your system's trust store.

State lives in ~/.bankmcp. Delete the folder to forget everything.

On a server

1. Deploy

Any container host works. The server needs a persistent volume at /data and a public https address; it asks you for everything else in the browser. A prebuilt image is published on every release: ghcr.io/noskillish/bankmcp (built by GitHub Actions from the tagged source, linux/amd64 and linux/arm64).

Railway: deploys the published image with a volume at /data and a domain, nothing to fill in. Or by hand: New Project, Deploy from GitHub repo, pick this repo, add a volume mounted at /data and generate a domain (Settings, Networking, port 8080). The server learns its own address from Railway.

Fly.io: three commands from a checkout, using fly.toml:

fly launch --copy-config --no-deploy   # pick an app name and region
fly volumes create data --size 1
fly deploy

Render: uses render.yaml. Render's persistent disks need a paid instance.

Docker on your own box:

docker run -d --name bankmcp --restart unless-stopped \
  -p 8080:8080 -v bankmcp-data:/data ghcr.io/noskillish/bankmcp:latest

or docker compose up -d with compose.yaml. Then put a TLS terminator in front (Caddy needs two lines: YOUR-HOST { reverse_proxy localhost:8080 }) and set BASE_URL to the public address. The server binds every interface by default. When the proxy runs on the same machine, set BIND_HOST=127.0.0.1 so nothing else on the local network reaches the login and setup pages.

Open the address. A fresh server shows a setup page.

2. Register an Enable Banking application

The setup page can do this for you. Enter the email of your Enable Banking account (or the one you want to create it with) and press Send me the sign-in link. Enable Banking emails you a one-time link; paste it on the next page. Your server signs in with it once, creates the application with the right redirect and policy addresses, generates the key pair and stores the id and the key. The sign-in is not kept. On a local server the click on the link does the same without pasting.

This is the beginning of the README. Read the rest at the original. Read the full README ↗