How to give Raw HTTP access to your bank account

4 min read
Direct answer: To give Raw HTTP access to your bank account, sign up at bankbridge.money ($5/mo per bank), link your bank in about 30 seconds through the bank-connection flow, then POST JSON-RPC to https://bankbridge.money/api/mcp with a Bearer header. BankBridge ships 11 read-only MCP tools (list_accounts, list_transactions, get_recurring_charges, get_monthly_cashflow, list_holdings, and 6 more) plus connect_bank, and Raw HTTP calls them live, with zero financial data cached.

1. Sign up at bankbridge.money

Go to bankbridge.money/login. Enter your email, click the magic link we send, and you're in. No password to remember. Takes about 20 seconds.

2. Subscribe and link your bank

Pricing is $5/month per connected bank. The dashboard prompts you for a card before letting you link a bank. Checkout is Stripe; cancel anytime from the dashboard.

Then click Connect a bank. A secure window opens, hosted by our upstream bank-aggregator, where you search for your bank (Chase, Bank of America, Wells Fargo, Capital One, Fidelity, Schwab, your local credit union, and thousands more), enter the credentials you use on the bank's website, and approve read-only access. Most banks take about 30 seconds; banks with MFA take a minute.

3. Install BankBridge in Raw HTTP

From your dashboard, copy your bbk_ API key. Then POST JSON-RPC to https://bankbridge.money/api/mcp with a Bearer header.

The full Raw HTTP setup doc auto-fills your real key when you're signed in, so you can copy the snippet with the key already baked in.

4. Try it

Open a fresh Raw HTTPsession and ask one of these. Each one hits a different tool, so it's a quick way to sanity-check the install:

  • “List my bank accounts and current balances.”
  • “How much did I spend on food this month?”
  • “What subscriptions am I paying for?”
  • “Any unusual charges this week?”

The first one calls list_accounts and is the fastest end-to-end check. If your balances come back, the other 12 tools will work too.

Is this safe?

  • Read-only by design. No tool can move money, send a payment, or change an account. The MCP surface is 11 read tools plus connect_bank, which only returns a link.
  • Your bank password never touches us.The link flow runs inside the bank-aggregator's UI; we receive an encrypted access token, not credentials.
  • Zero financial data cached. Every Raw HTTP query live-fetches from your bank and returns. We store your account, your API key hash, and the encrypted token. That's it.
  • Revoke in one click. Disconnect the bank from the dashboard, or rotate your API key from settings. Old keys stop working immediately.

Questions? Email hello@greatwork.company. Built by Great Work.

FAQ

Is it safe to give Raw HTTP access to my bank account?

BankBridge is read-only by design: its 11 data tools only read, and the 12th, connect_bank, returns a link you open yourself. No tool can move money or change an account, so Raw HTTP has nothing to call even if a prompt tells it to. Your bank password never touches BankBridge; you sign in inside the bank-connection provider's window, and BankBridge stores only an encrypted access token (AES-256-GCM). No balances or transactions are cached on our servers.

Where does my bank data go when Raw HTTP reads it?

Each question makes Raw HTTP call a BankBridge tool, BankBridge fetches live from your bank, and the result is returned to Raw HTTP. From there, tool results are sent to your own code, and to any model you pass it to. Ask narrow questions ("restaurant spending in May") rather than "show me every transaction" to keep less financial detail in the conversation.

What can Raw HTTP do once it is connected?

Your code can call any of the 11 read tools: balances, filtered transaction lists, search, spending summaries by category, merchant, month, or week, recurring charges, monthly cashflow, merchant history, categories, holdings, and investment transactions. Results come back as JSON, so Raw HTTP workflows can aggregate them however you need.

Where do I get the API key Raw HTTP needs?

From your BankBridge dashboard. Keys start with bbk_ and are sent as an Authorization: Bearer header. The Raw HTTP doc page on bankbridge.money fills your real key into the snippet when you are signed in. If a key leaks, rotate it in settings and the old one stops working immediately.

What does it cost to use BankBridge with Raw HTTP?

$5 per month per connected bank, or $50 per year per bank on the annual plan, and the same subscription works in Raw HTTP and every other MCP host. One bank is $5 a month, three banks is $15. Cancel any time from the dashboard; you keep access through the end of the billing period.