Connect BankSync to Claude Code

Use BankSync MCP server with Claude Code to give Anthropic's terminal-based AI coding assistant access to real bank transactions, balances, and investments directly from your CLI.

See the Claude Code MCP docs for more detail.

Prerequisites

A BankSync account with at least one connected bank
An API key with all permission scopes (created from Workspace → Developers)

One-click install (Claude Desktop app)

Using the Claude Desktop app? Download the BankSync bundle and double-click to install — no manual config needed.

Download banksync-mcp.mcpb

Add the server

Run the following, replacing the placeholder with your BankSync API key:

Terminal

claude mcp add --transport http banksync https://mcp.banksync.io \
  --header "X-API-Key: bsk_your_api_key_here"

Where it goes: .mcp.json (project root)

Option 2: JSON Config (CLI)

claude mcp add-json banksync '{
  "type": "http",
  "url": "https://mcp.banksync.io",
  "headers": {
    "X-API-Key": "bsk_your_api_key_here"
  }
}'

Option 3: Project Config File (.mcp.json, supports env var expansion)

{
  "mcpServers": {
    "banksync": {
      "type": "http",
      "url": "https://mcp.banksync.io",
      "headers": {
        "X-API-Key": "${BANKSYNC_API_KEY}"
      }
    }
  }
}

Alternative: npm Package (@banksync/mcp, bridges stdio to remote)

claude mcp add banksync -e BANKSYNC_API_KEY=bsk_your_api_key_here -- npx -y @banksync/mcp

Tip. Run /mcp inside Claude Code to verify your MCP servers are connected and see the available tools.

Server URL. BankSync’s MCP server is at https://mcp.banksync.io over Streamable HTTP, authenticated with your X-API-Key. If Claude Code can’t reach a remote server, use the local bridge npx -y @banksync/mcp with BANKSYNC_API_KEY set.

Verify your connection

Restart your client and try these prompts to confirm the connection works:

“List my workspaces”

“What banks do I have connected?”

“What’s my checking account balance?”

Troubleshooting

“No tools available” or the MCP server is not listed

Make sure you restarted your AI client after editing the config file.
Verify the JSON/YAML is valid (no trailing commas, correct brackets).
Check the URL is exactly https://mcp.banksync.io.

“Authentication failed” or “Invalid API key”

Confirm the key starts with bsk_ and has not been revoked.
Ensure the key is passed in the X-API-Key header.
Check for stray whitespace or newlines around the key value.

Connection timeout or the client lacks remote HTTP support

The server uses Streamable HTTP. Allow outbound HTTPS to mcp.banksync.io.
If your client only supports local servers, use the npm bridge: npx -y @banksync/mcp.

Tools are listed but return errors

Verify your API key has the required scopes — for full access, select all scopes when creating the key.
Make sure you have at least one bank connected in the BankSync app.
Check that you are passing the correct workspace ID when prompted.

Debugging with MCP Inspector

Use the MCP Inspector to test the connection independently of your AI client.
Run: npx @modelcontextprotocol/inspector --url https://mcp.banksync.io--header "X-API-Key: bsk_your_key"
If the Inspector connects but your client does not, the issue is your client configuration.

Frequently asked questions

How do I add BankSync to Claude Code?

Run "claude mcp add --transport http banksync https://mcp.banksync.io --header X-API-Key: bsk_your_api_key" in your terminal. You can also use claude mcp add-json for JSON config or add a .mcp.json file to your project root.

How do I verify BankSync is connected in Claude Code?

Run the /mcp command inside Claude Code to see all connected MCP servers and their available tools. You can also try asking "List my workspaces" to test the connection.

Can I use environment variables for the API key in Claude Code?

Yes. Add a .mcp.json file to your project root and use ${BANKSYNC_API_KEY} syntax in the headers. Claude Code supports environment variable expansion in project config files.

← All clients