Access bank data in your terminal with Copilot
Add the BankSync MCP server to GitHub Copilot CLI and let the terminal agent plan, build and iterate with your real transactions and balances.
$copilotWhich subscriptions did we pay for twice this quarter?banksync · get_transactions 642 rows · Venture Card ••8830Two: Figma was billed on both cards in August, and Zoom twice in September. $184 in duplicates.Write them to duplicates.csv.Saved duplicates.csv with 4 rows.
Connect Copilot CLI in three steps.
- 01
Create a scoped key
Connect your banks in BankSync, then create an API key with read scopes under Developers.
New API key
NameMCP clientScopesbanks:readfeeds:readKeybsk_••••••••3f9a - 02
Add the server
Run /mcp add in a Copilot CLI session and fill in the form, or edit ~/.copilot/mcp-config.json.
/mcp add
Server NamebanksyncServer TypeHTTPURLhttps://mcp.banksync.ioHeaders{"X-API-Key": "bsk_…"} - 03
Ask from your terminal
Ask Copilot about your transactions, or have it build on them.
Which subscriptions did we pay for twice this quarter?
get_transactions · 642 rows · Venture Card ••8830
Two: Figma was billed on both cards in August, and Zoom twice in September. $184 in duplicates.
What you can build.
- Terminal financial queries
- Ask Copilot CLI to fetch account balances, recent transactions, and investment holdings directly from your terminal.
- Automated scripts
- Let the autonomous agent plan and build shell scripts that pull bank data, generate reports, and automate financial workflows.
- Data pipelines
- Build ETL pipelines that extract, transform, and load bank data, Copilot CLI understands your actual data schemas via MCP.
- Code generation
- Generate API clients, type definitions, and data models based on real bank transaction structures and account types.
- Test fixtures
- Create realistic test data and mock fixtures derived from actual transaction patterns and account structures.
- Cloud agent delegation
- Use the & prefix to delegate complex financial data tasks to the cloud coding agent and /resume to switch between sessions.
Change assistants. Keep your data.
What Copilot CLI 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
- ~/.copilot/mcp-config.json, or /mcp add inside a session.
- 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 add BankSync MCP to GitHub Copilot CLI?
Generate a BankSync API key, then add the MCP server configuration to your Copilot CLI config. The BankSync tools will be available as MCP tools when you run copilot in your terminal.
Does Copilot CLI support custom MCP servers like BankSync?
Yes. GitHub Copilot CLI ships with the GitHub MCP server built-in and supports adding custom MCP servers like BankSync for domain-specific tools and data access.
What models does Copilot CLI support?
Copilot CLI supports Claude Opus 4.6, Sonnet 4.6, GPT-5.3-Codex, and Gemini 3 Pro. BankSync MCP tools work with all supported models.
Can I delegate BankSync tasks to the cloud coding agent?
Yes. Use the & prefix in Copilot CLI to delegate work to the cloud coding agent. You can use /resume to switch between local and remote sessions seamlessly.