Your assistant. Your server. Your bank.
Your assistant talks to your server. Your server talks to your bank through Enable Banking, a licensed open-banking provider. Your data passes through Enable Banking on every call and is not stored there. It does not go to the makers of BankMCP™.
Run your own copy
On your machine with npx bankmcp, or as one container on Railway or Fly. A new server shows a setup page in the browser.
Register at Enable Banking
Free. You get an application and a private key. The setup page shows the values their form asks for.
Connect your assistant and your bank
Add your server as a connector, sign in with your password, then say connect my bank and log in at your bank.
Local
With Node 24 or later installed, run npx -y bankmcp from your MCP client's configuration, or install the Claude Desktop bundle from the GitHub releases. The server listens on https://localhost:8080 and shows the setup page there. There is no password in local mode, so anyone with access to your machine has access to the server.
Hosted by you
One click on Railway: Deploy on Railway creates the container, the volume and the domain. Or deploy the container to Fly, Render or any host with a persistent volume. Then open the URL, and the setup page asks for your Enable Banking application id, the private key file and a password. Then add the server's /mcp URL as a connector in your assistant and sign in with that password.