Connect BankSync to Claude Code

Claude Code is Anthropic's CLI for Claude. Add BankSync as an MCP server with a single command. See the Claude Code docs for more details.

Prerequisites

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

Option 1: CLI Command

Run this command in your terminal to register BankSync as an MCP server:

Terminal

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

Option 2: JSON Config

Alternatively, use the JSON config command:

Terminal

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

For project-level configuration, add to .mcp.json in your project root. This approach supports environment variable expansion:

.mcp.json

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

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

Verify Your Connection

After configuring your client, restart it and try these prompts to verify the connection is working:

“List my workspaces”

“What banks do I have connected?”

“What’s my checking account balance?”

Troubleshooting

“No tools available” or MCP server not listed

Make sure you restarted your AI client after editing the configuration file.
Verify the JSON is valid (no trailing commas, correct brackets).
Check that 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 in the headers object under X-API-Key.
Check for accidental whitespace or newlines around the key value.

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.

Connection timeout or network errors

The MCP server uses Streamable HTTP transport. Ensure your network or proxy allows outbound HTTPS connections.
If using a VPN or firewall, allow connections to mcp.banksync.io.
Try the connection from a different network to rule out local issues.

Connect BankSync to Claude Code

Claude Code is Anthropic's CLI for Claude. Add BankSync as an MCP server with a single command. See the Claude Code docs for more details.

Prerequisites

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

Option 1: CLI Command

Run this command in your terminal to register BankSync as an MCP server:

Terminal

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

Option 2: JSON Config

Alternatively, use the JSON config command:

Terminal

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

For project-level configuration, add to .mcp.json in your project root. This approach supports environment variable expansion:

.mcp.json

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

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

Verify Your Connection

After configuring your client, restart it and try these prompts to verify the connection is working:

“List my workspaces”

“What banks do I have connected?”

“What’s my checking account balance?”

Troubleshooting

“No tools available” or MCP server not listed

Make sure you restarted your AI client after editing the configuration file.
Verify the JSON is valid (no trailing commas, correct brackets).
Check that 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 in the headers object under X-API-Key.
Check for accidental whitespace or newlines around the key value.

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.

Connection timeout or network errors

The MCP server uses Streamable HTTP transport. Ensure your network or proxy allows outbound HTTPS connections.
If using a VPN or firewall, allow connections to mcp.banksync.io.
Try the connection from a different network to rule out local issues.