BankSync

Connect BankSync to Kilo Code

Connect BankSync MCP server to Kilo Code for AI-powered fintech development with live bank data.

Prerequisites

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

Configuration

Add the BankSync server to your Kilo Code MCP configuration, replacing the placeholder with your API key:

MCP config (JSON)
{
  "mcp": {
    "banksync": {
      "type": "remote",
      "url": "https://mcp.banksync.io",
      "headers": {
        "X-API-Key": "bsk_your_api_key_here"
      },
      "enabled": true
    }
  }
}

Where it goes: ~/.config/kilo/kilo.jsonc (global) · kilo.jsonc or .kilo/kilo.jsonc in project root (project)

Alternative: npm package (@banksync/mcp local stdio bridge)

Alternative: npm package (@banksync/mcp local stdio bridge)
{
  "mcp": {
    "banksync": {
      "type": "local",
      "command": ["npx", "-y", "@banksync/mcp"],
      "environment": {
        "BANKSYNC_API_KEY": "bsk_your_api_key_here"
      },
      "enabled": true
    }
  }
}
Tip. Kilo Code differs from Cline/Roo Code: the root key is "mcp" (not "mcpServers"); remote servers use "type": "remote"; the toggle is "enabled": true (not "disabled": false); and the file format is JSONC (comments allowed).
Server URL. BankSync’s MCP server is at https://mcp.banksync.io over Streamable HTTP, authenticated with your X-API-Key. If Kilo 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.
← All clients