Connect BankSync to n8n
n8n connects to external MCP servers using the MCP Client Tool sub-node within an AI Agent workflow. Setup is done in the n8n workflow editor — there is no JSON config file.
Prerequisites
- A BankSync account with at least one connected bank
- An API key with all permission scopes (created from Workspace menu → Developers)
Requirement: Set the environment variable N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE=true to use the MCP Client node as a tool inside AI Agents.
Setup Steps
- In your n8n workflow, add an AI Agent node.
- Connect an MCP Client Tool sub-node to the AI Agent's Tools input.
- In the MCP Client Tool node, set:
- SSE/HTTP Endpoint:
https://mcp.banksync.io - Authentication: Header Auth, name
X-API-Key, value your BankSync API key - Tools to include: All (or select specific BankSync tools)
- SSE/HTTP Endpoint:
- Execute the node to verify — it lists all available BankSync 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
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.