Connect BankSync with the TypeScript SDK
Build your own MCP client using the official @modelcontextprotocol/sdk package.
Prerequisites
- A BankSync account with at least one connected bank
- An API key with all permission scopes (created from Workspace menu → Developers)
Install the SDK
Terminal
npm install @modelcontextprotocol/sdk
Connect to BankSync
Custom MCP Client
1import { StreamableHTTPClientTransport } from '@modelcontextprotocol/sdk/client/streamableHttp.js';2import { Client } from '@modelcontextprotocol/sdk/client/index.js';34const transport = new StreamableHTTPClientTransport(5 new URL('https://mcp.banksync.io'),6 { requestInit: { headers: { 'X-API-Key': 'bsk_your_api_key_here' } } }7);89const client = new Client({ name: 'my-agent', version: '1.0.0' });10await client.connect(transport);1112const { tools } = await client.listTools();13console.log(`Connected! ${tools.length} tools available`);1415// Call a tool16const result = await client.callTool({17 name: 'list-workspaces',18 arguments: {},19});20console.log(result);
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.
