Raw HTTP

Standard MCP endpoint.

BankBridge is a plain-vanilla streamable-http MCP server. Point any MCP-speaking client at it with a bearer token and you’re in.

Step 01

The endpoint.

URL

https://bankbridge.money/api/mcp

Authorization header: Authorization: Bearer bbk_.... Grab a key from your dashboard.

Step 02

Test it with curl.

shell

curl -N https://bankbridge.money/api/mcp \
  -H "Authorization: Bearer bbk_your_api_key_here" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/list"
  }'

You should see all 12 tool definitions in the response.

Step 03

That's the API.

Speaks MCP 2025-06-18 (streamable-http). Supports initialize, tools/list, tools/call, prompts/list, prompts/get, and session re-initialization per spec. No custom extensions — your existing MCP client library will just work.

Two ways to authenticate

Static key (this page): a bbk_ key from your dashboard, sent as Authorization: Bearer. Simplest; one key per user/app.

OAuth 2.1: for consumer apps where each end-user should connect their own BankBridge account, we run a full OAuth provider with Dynamic Client Registration, PKCE, and token refresh. Discovery metadata at /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server.

Troubleshooting

401 Unauthorized.

The Bearer token is wrong, missing the `Bearer ` prefix (note the space), or the key was revoked/rotated.

Fix: Paste a fresh key from Settings. Double-check the header has Bearer plus a space plus the key.

403 Forbidden.

Your BankBridge subscription is inactive (canceled or past-due), or your account has no connected banks.

Fix: Visit Settings to confirm your subscription is active.

Tools return a NO_CONNECTIONS warning.

You haven't linked a bank yet.

Fix: Visit Connect a bank — the bank-connect flow opens automatically, ~30 seconds.

Tools return REAUTH_REQUIRED.

Your bank requires re-authorization (happens every 90 days at most institutions).

Fix: Visit the dashboard. The affected bank will have a Reconnect button.

Client reports 'protocol version mismatch'.

Older MCP clients may send 2024-11-05 or 2025-03-26. We support 2025-06-18, but backward-compat advertises older versions on initialize.

Fix: Update your MCP client library to the latest release.

Problems? Email hello@bankbridge.money.