Sandbox / simulated — not a real bank. Balances, accounts and transactions on this site are synthetic demo data. This is not a real bank or a real customer.
Sign in

Install guide

Connect your AI tool to Banker MCP in about two minutes. You need an API key from your dashboard.

Client configuration formats change between releases. These snippets follow each tool's documented remote-MCP format and have not yet been tested against every client version. If a tool rejects one, check its current MCP documentation and use the same URL and Authorization header.

1. Get a key

  1. Sign in with Google or a passkey.
  2. In the dashboard, create a key and name it after the tool that will use it.
  3. Copy it now. It is shown once.

The examples below read the key from an environment variable so it never lands in a file you might commit:

export BANKERMCP_API_KEY="bmcp_..."

2. Add the server

claude mcp add --transport http bankermcp https://bankermcp.io/mcp \
  --header "Authorization: Bearer $BANKERMCP_API_KEY"

Run claude mcp list to confirm it connects.

3. Check it works

Ask your assistant: "Use Banker MCP to list the banks you can reach." You should see the sandbox bank, flagged simulated: true. Your dashboard's recent calls list shows the request within a moment.

Using it in an LLM application you build

Any MCP client library can connect to https://bankermcp.io/mcp with the Authorization header. Keep the key on your server, never in browser or mobile code, and use one key per application so you can revoke it independently.

Troubleshooting

SymptomCause and fix
401 UnauthorizedThe key is missing, mistyped or revoked. Create a new one.
"allowance used up"You hit your plan's monthly calls. Upgrade, or wait for the 1st (UTC).
"requires a paid plan"You asked for a real bank on the Sandbox plan.
Client cannot connectCheck the URL ends in /mcp and the client supports remote HTTP servers.