Bank data in your workflow

Run the BankSync MCP server next to Pieces and use your bank data across your development workflow.

PiecesBankSync MCP
Pieces memory and BankSync data side by side in one MCP client.

Connect Pieces in three steps.

  1. 01

    Create a scoped key

    Connect your banks in BankSync, then create an API key with read scopes under Developers.

    New API key

    NameMCP client
    Scopesbanks:readfeeds:read
    Keybsk_••••••••3f9a
  2. 02

    Add both servers

    Add BankSync beside the Pieces server (PiecesOS on localhost:39300) in your MCP client.

    .cursor/mcp.json

    {
      "mcpServers": {
        "pieces": {
          "url": "http://localhost:39300/model_context_protocol/2025-03-26/mcp"
        },
        "banksync": {
          "url": "https://mcp.banksync.io",
          "headers": {
            "X-API-Key": "bsk_your_key_here"
          }
        }
      }
    }
  3. 03

    Ask across both

    Ask a question that needs your notes and your numbers.

    What did I decide about the AWS bill last week, and what was it?

    get_transactions · AWS · Business Checking ••4021

    Your note from Tuesday says to move logs to cold storage. The October AWS bill was $1,212.40, down $96 on September.

What you can ask.

Financial code snippets
Save, organize, and reuse bank data query snippets, financial schemas, and API integration code.
Cross-IDE financial context
Access bank data context from any IDE or browser through Pieces' cross-platform workflow.
Financial schema references
Keep real bank data schemas as reference snippets while building finance features.
Code generation
Generate API clients and data models with Pieces AI using real bank data structures from BankSync.
Team knowledge sharing
Share financial integration patterns and bank data code snippets across your development team.
Debug with real data
Reference actual bank transaction formats and account structures while debugging finance code.

What Pieces gets.

Server
Remote and hosted at https://mcp.banksync.io over Streamable HTTP. Nothing to install.
Tools
227 documented tools: bank data, feeds and jobs, tables, dashboards, automations and enrichments. Tools reference
Sign-in
A scoped API key, sent in the X-API-Key header.
Config
Beside Pieces in any MCP client: Cursor, Claude Desktop, VS Code or Zed.
Access
Set by the scopes you grant. Read scopes keep the connection read-only; no tool can move money.
Rate limits
20 tool calls a minute on Standard, 40 on Professional, 60 on Business, shared across a workspace.
Banks
12,000+ institutions in the US, Canada, the UK, Europe and Australia, including Consumer Data Right connections.

Questions, answered.

How do I connect Pieces to BankSync?

Generate a BankSync API key, then add the BankSync MCP server configuration in your Pieces settings. Pieces will discover 227 financial data tools for use across your development workflow.

Can Pieces save bank data snippets?

Yes. Pieces can save and organize code snippets related to bank data queries, financial schemas, and API integrations. Combined with BankSync MCP, you can reference real bank data while managing your snippet library.

Does Pieces work across multiple IDEs with BankSync?

Yes. Pieces works across VS Code, JetBrains, and other IDEs. Once BankSync MCP is configured, financial data tools are available everywhere Pieces runs.

Bank data across your workflow