Connect BankSync to Claude Desktop
Claude Desktop supports remote MCP servers natively via Streamable HTTP. You can also install via the one-click Desktop Extension. See the Claude Desktop 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: One-Click Install (Desktop Extension)
Download the BankSync Desktop Extension and open it with Claude Desktop. You'll be prompted to enter your API key during installation.
Download banksync-mcp.mcpb
Open the downloaded file with Claude Desktop to install.
Option 2: Remote Server Config
Config File Location
| Platform | Path |
|---|---|
| macOS | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Windows | %APPDATA%\\Claude\\claude_desktop_config.json |
Add the MCP Server
Add the following to your configuration file:
claude_desktop_config.json
{"mcpServers": {"banksync": {"type": "http","url": "https://mcp.banksync.io","headers": {"X-API-Key": "bsk_your_api_key_here"}}}}
Option 3: npm Package
If your version of Claude Desktop does not support remote HTTP servers, you can use the @banksync/mcp npm package as a local bridge:
claude_desktop_config.json
{"mcpServers": {"banksync": {"command": "npx","args": ["-y", "@banksync/mcp"],"env": {"BANKSYNC_API_KEY": "bsk_your_api_key_here"}}}}
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
headersobject underX-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.
- If your client does not support remote HTTP servers, use the npm package instead:
npx -y @banksync/mcp
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 successfully but your client does not, the issue is with your client configuration.