1. Add BankBridge in Claude
Open BankBridge in the Claude Connectors Directory and click Connect. That works from claude.ai, Claude Desktop and Cowork, and the connector then follows your Claude account to the mobile apps too.
Prefer to paste a URL? In Claude open Customize, then Connectors, click + Add and choose Add custom connector. Name it BankBridge, paste https://bankbridge.money/api/mcp, click Continue, keep the sign-in settings Claude detects, and click Add. There is no API key or token to paste. Step-by-step pages: claude.ai, Claude Desktop, Cowork.
2. Sign in
Claude opens a BankBridge sign-in page. Enter your email and type the 6-digit code we send you, or use Continue with Google. New here? The same code creates your account. No password to set.
3. Pick a plan
BankBridge costs $5 a month or $50 a year per connected bank. One bank: $5. Two banks: $10. Checkout runs through Stripe, and you can cancel any time: billing stops at the end of the current period and you keep access until then. Want to look first? Try the demo with sample data.
4. Link your bank
A secure window opens, hosted by the upstream bank-aggregator. Search your bank (Chase, Bank of America, Wells Fargo, Capital One, your local credit union, Fidelity, Schwab, Robinhood, etc.), enter the credentials you use on the bank's website, and approve read-only access. Then click Allow, and you're back in Claude with BankBridge connected.
If you want investment data (holdings, buys, sells, dividends), connect a brokerage account in the same flow. They show up next to your checking and credit cards.
Not sure your bank connects? Check your bank before you sign up. There are step-by-step guides for Chase, Bank of America, Wells Fargo and Fidelity, including where to turn access off from inside the bank.
Claude Code
In Claude Code, install the plugin instead of a connector:
/plugin marketplace add bankbridge-money/bankbridge-plugin
/plugin install bankbridgeThen run /mcp, pick bankbridge and choose Authenticate. Your browser opens the same sign-in, plan and bank steps as above (no key to copy). After that, Claude Code can call all 12 tools. Details: Claude Code setup.
What to ask first
Open a fresh Claude conversation and try one of these. Each one hits a different tool, so they're a quick way to confirm the connector works end-to-end:
- “List my bank accounts and current balances.”
- “How much did I spend on food this month?”
- “What subscriptions am I paying for?”
- “Are there any unusual charges this week?”
- “Break down my spending by category since January 1.”
- “Show me every charge from Whole Foods this year.”
- “How are my investments doing this quarter?”
The first one calls list_accounts. It's the fastest sanity check. If your balances come back, the rest will work too.
Is this safe?
Short version: read-only, encrypted, revocable, and nothing financial is cached on our servers.
- Read-only by design. No tool can move money, send a payment, or change your account. The MCP surface is 12 read tools and nothing else.
- Your bank password never touches us. The link flow runs inside the upstream bank-aggregator's own UI; we receive an encrypted access token, not credentials.
- Nothing financial cached. Every Claude call live-fetches from your bank through the aggregator and returns. Our database stores your account, your API key hash, and the encrypted token. That's it.
- Revocation is one click. Disconnect the bank, or rotate your API key from settings. Old keys stop working immediately.
Questions? Email hello@greatwork.company. Built by Great Work.