BankMCP™ for Claude Code: /bank:setup walks you through installing it locally, /bank:deploy through hosting it; plus a skill with account mapping, categorisation rules and a monthly review format.

version
0.1.1
GitHub stars
326

Install

/plugin install bank@bank

Run it inside Claude Code after adding the marketplace with /plugin marketplace add noskillish/bankmcp.

Contents

Discovered from source

Skills 3

bank

You have read-only access to the user's own bank accounts through the bank MCP server. There are no payment tools.

Ground rules

  • Amounts are signed: negative is money out. Use the booked balance for totals and net worth. available can include an overdraft or a credit line, so a mortgage can show a positive available while booked is deeply negative.
  • Refer to accounts by their label. Run list_accounts once per conversation to see labels and uids. If an account has no label, suggest one and set it with set_account_label.
  • Banks return limited history, often 90 days and rarely more than two years. If a range comes back empty, say the bank returned nothing rather than assuming there was no activity.
  • Do not invent or "adjust" a balance or transaction. If the user asks for a number to look different than it is, decline and offer to explain the real one.
  • Keep answers short. Numbers in the account's currency, rounded to whole units unless cents matter.

Account map

Fill this in for the user (or ask them to). Copy it into the user's own copy of this skill.

LabelPurposeTreat as
EverydaySalary in, cards and bills outPersonal spending
SavingsBufferPersonal, exclude from spending
Joint expensesShared household costs, funded by fixed monthly transfers from each partnerShared spending
HousingMortgage payments and housing billsShared spending
MortgageLoanLiability, not spending

Transfers between the user's own accounts are not income or spending. Detect them as pairs: same amount, opposite sign, within two days, on two different accounts. When the user has a partner with unlinked accounts, the partner's transfers into shared accounts show up as income on the shared side; label them "partner contribution", not income.

Categorisation

Use the counterparty first, then the description. Categories:

income, transfer, housing, utilities, groceries, eating out, transport, subscriptions, shopping, health, kids, travel, insurance, fees, cash, other.

Rules of thumb:

  • Recurring same-amount debits from a company: subscriptions (streaming, phone, gym, software) or utilities (power, water, heating, internet) or insurance.
  • Supermarket chains and grocers: groceries. Restaurants, cafés, takeaway apps: eating out.
  • Public transport, fuel, parking, ride hailing, tolls, bridge fees: transport.
  • Mortgage and rent: housing. Property tax and housing association fees: housing.
  • Pharmacies, doctors, dentists: health. Daycare, school, kids' clubs: kids.
  • Airlines, hotels, foreign card payments in a cluster: travel.
  • Card fee, interest, currency surcharge: fees.

Add the user's own rules below as pattern → category lines and apply them before the rules of thumb:

# STRIPE PAYOUT → income (client invoices)
# ACME INSURANCE → insurance

Monthly review format

  1. Headline: income, spending, net, savings rate. One line.
  2. Spending by category, largest first, with share of total. Compare to the previous month if you fetched it.
  3. Ten largest single expenses with date, counterparty, account.
  4. Recurring items seen this month and their yearly cost.
  5. Two or three observations worth acting on. Concrete: "Eating out was 40% above the three-month average; three of the ten largest expenses were restaurants."

Watches

Use create_watch when the user says "tell me when", "let me know if", "has X paid yet, keep an eye on it":

  • Waiting for a payment: credit_missing_by with match = payer name and by_date = due date. It notifies when the money arrives or when the date passes.
  • Cash floor: balance_below on the everyday account.
  • Fraud and surprises: large_debit with an amount around three times the usual biggest card payment.

Notifications go to the server's webhook. If create_watch says no webhook is configured, tell the user to set NOTIFY_WEBHOOK_URL on the server; check_watches still works on demand.

Deploy BankMCP™ to a server

Guide one person through a hosted deployment. Prefer Railway unless the user names another host. Run what you can with the CLI; the user does the dashboard clicks, their bank login and their claude.ai settings.

1. Choose the host

Ask which they have: Railway, Fly.io, Render, or their own box with Docker. If none, recommend Railway (https://railway.com) and wait until they have an account.

2. Railway

If the railway CLI is installed and logged in (railway whoami), do it from the terminal:

railway init
railway add --service bankmcp --repo noskillish/bankmcp --branch main
railway volume add -m /data
railway domain --port 8080

Otherwise, in the Railway dashboard: New Project, Deploy from GitHub repo noskillish/bankmcp; add a Volume mounted at /data; Settings, Networking, Generate Domain on port 8080.

Report the public address. No variables are needed; the server detects its own address on Railway.

3. Fly.io or Docker

Fly: from a clone of the repo, fly launch --copy-config --no-deploy (the repo's fly.toml already mounts /data and checks /healthz), fly volumes create data --size 1, fly deploy. Render: the Deploy to Render button in the README uses render.yaml; a persistent disk needs a paid instance. Docker: 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 from a clone), then a TLS proxy in front and BASE_URL set to the public https address.

4. Setup page

Tell the user to open the public address. It shows a setup page with the values for Enable Banking's form. Walk them through registering the application as in the setup skill (environment, redirect URL, description, privacy and terms URLs, key download), then entering the application id, the .pem file and a password of twelve characters or more. The status page then shows the connector URL.

5. Connector

claude.ai (personal Pro or Max account): Settings, Connectors, Add custom connector, name BankMCP™, URL https://<address>/mcp, leave OAuth fields empty, Add, Connect, enter the password.

Team or Enterprise workspaces only allow Owners to add custom connectors; say so if the button is missing.

Claude Code: claude mcp add --transport http bankmcp https://<address>/mcp, then /mcp to sign in.

6. Bank

In the connected client: "connect my bank". Same flow as locally; the redirect returns to the server's /callback.

Notes

  • Changing the password later logs every client out; that is the kill switch.
  • Set NOTIFY_WEBHOOK_URL to a Slack incoming webhook for sign-in alerts and watch notifications.

Set up BankMCP™ locally

You are guiding one person through running BankMCP™ on their own machine. Do the steps in order, one at a time, and confirm each before the next. Run commands yourself where you can; ask the user to do the parts that need their browser or their bank login. Do not guess values; read them from command output.

1. Node

Run node --version. BankMCP needs 24 or newer. If it is older or missing, tell the user to install the current LTS from https://nodejs.org and stop until it is done.

2. Register the server with Claude Code

Run:

claude mcp add --scope user bankmcp -- npx -y bankmcp

Then tell the user to restart Claude Code (or run /mcp) so the bankmcp tools appear. Wait for them to confirm the tools are listed.

3. Find the setup page

Call any BankMCP tool, for example list_accounts. On a fresh install it answers with a localhost address such as https://localhost:8080. Give the user that exact address and tell them:

  • their browser will warn about a self-signed certificate on localhost; they should continue past it, it is the server they just started;
  • the page lists four values for Enable Banking's form, each with a Copy button.

4. Enable Banking application

Tell the user to open https://enablebanking.com/cp/applications in another tab, create an account if needed, and add an application:

  • Environment: Production for real accounts, Sandbox to try with test data.
  • Paste the redirect URL, description, privacy URL and terms URL from the setup page.
  • Keep "generate private key" selected. On Save a .pem file downloads once; the application id (a UUID) is shown after saving.

For Production, mention that the application starts Inactive and that clicking Activate by linking accounts and logging in at their bank is what activates it for their own accounts.

5. Finish the setup page

Back on the localhost page: paste the application id, choose the downloaded .pem, set the country, click Finish setup. The page turns into a status page. Confirm with the user.

6. Connect the first bank

Call list_banks with the user's country and let them pick. Call start_consent with the exact bank name and give them the URL. They log in at the bank and land on a "Bank connected" page. Then call list_accounts and show what got linked. Offer labels with set_account_label.

If something fails

  • Tool says "not set up yet" after setup: the server may need a restart; run /mcp and reconnect bankmcp.
  • "redirect_uri" errors from Enable Banking: the redirect URL on the application must be exactly the one the setup page showed, including https:// and the port.
  • Port in use: set PORT for the server (for example claude mcp add --scope user -e PORT=8085 bankmcp -- npx -y bankmcp) and register the matching redirect URL.

MCP servers 1

Sponsors

Details

Marketplace
noskillish/bankmcp
Source
plugin
Author
Nils Smed
Category
Productivity
License
MIT
Keywords
banking, personal-finance, psd2, enable-banking