Custom Connector.
Open Settings → Connectors.
Claude Desktop → Settings → Connectors → Add custom connector.
Paste the server URL.
URL:
https://bankbridge.money/api/mcp
Leave the Advanced fields empty — OAuth is auto-discovered.
Connect + approve.
Click Connect, sign in with your BankBridge email, click Allow. Claude Desktop gets an access token scoped to your account — no API key to copy, no token to paste. If you rotate anything later, click Connect again.
Use the tools + the + button.
The 12 MCP tools are available to every chat automatically. Try:
how much did I spend this week?
The + button in the chat input surfaces BankBridge’s 19 slash-command prompts: /monthly-check, /subscriptions, /portfolio-health, and more. One click fills the full prompt template; Claude runs the multi-step flow. Works the same way in Claude iOS, Android, and Cowork.
Because custom connectors sync across every Claude surface, adding BankBridge on the web enables it in Desktop automatically. One-click via the button below:
Copies https://bankbridge.money/api/mcp, opens the connector dialog in a new tab.
Troubleshooting
.mcpb)Claude Desktop supports two install formats: Custom Connector (remote URL, OAuth) and the .mcpb bundle (local executable, bearer token). We recommend the Custom Connector because the .mcpbflow shows a generic “grant this extension access to everything on your computer” warning on install — accurate for the format in general, but misleading for BankBridge, which only makes HTTP calls to our server. Custom Connector skips all of that: no local process, no filesystem access, no scary dialog.
Prefer the .mcpb bundle?
Still supported — download bankbridge.mcpb, double-click it, paste your API token from your dashboard when prompted.
The bundle wraps mcp-remote, a stdio → HTTP proxy that forwards your requests to bankbridge.money/api/mcpwith your bearer token. It’s functionally equivalent to the Custom Connector — only the install path differs.