Give Amazon Q Developer access to your bank data
Add the BankSync MCP server to Amazon Q Developer and build with your real transactions, balances and holdings from the IDE or the CLI.
reports/runway.py
# Monthly burn from BankSync transactionsfrom collections import defaultdict def monthly_burn(txs): months = defaultdict(float) for tx in txs: if tx["amount"] < 0: key = tx["date"][:7] months[key] -= tx["amount"] return dict(sorted(months.items())) def runway(balance, burn): return round(balance / burn, 1)
Agent
Connect Amazon Q Developer 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
Put the BankSync entry in ~/.aws/amazonq/mcp.json, or .amazonq/mcp.json for one workspace. Amazon Q finds the tools when it loads.
~/.aws/amazonq/mcp.json
{ "mcpServers": { "banksync": { "url": "https://mcp.banksync.io", "headers": { "X-API-Key": "bsk_your_key_here" } } } } - 03
Ask from your IDE
Ask Amazon Q about your accounts, or have it build on the data it reads.
Write a runway report from our last six months of spending.
get_transactions · 1,284 rows · Business Checking ••4021
reports/runway.py is ready. Average burn is $21,480 a month, which gives 14.2 months of runway on today’s balances.
What you can build.
- Build your own finance tools on AWS with live bank data
- Amazon Q can scaffold Lambda functions, API Gateway routes, and DynamoDB schemas using real transaction structures from your connected banks.
- Automate infrastructure for financial data pipelines
- Ask Amazon Q to generate CloudFormation or CDK templates for ingesting bank transactions into S3, Redshift, or RDS with proper partitioning.
- Generate code with real transaction schemas
- Amazon Q writes TypeScript, Python, or Java code that matches your actual bank data shapes - no mocking or guessing field names.
- Query spending from the CLI
- Use Amazon Q in the terminal to check balances, search transactions, or analyze spending patterns without leaving your development workflow.
Change assistants. Keep your data.
What Amazon Q Developer 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
- ~/.aws/amazonq/mcp.json for every workspace, or .amazonq/mcp.json in one project.
- 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 Amazon Q Developer to my bank data?
Sign up for BankSync, connect your bank accounts, and generate an API key. Then add the BankSync MCP server configuration to your Amazon Q Developer settings. Amazon Q will automatically discover all 227 financial data tools.
Does Amazon Q Developer support MCP servers?
Yes. Amazon Q Developer added MCP support in April 2025. It works in the CLI, VS Code, and JetBrains IDEs. Amazon Q supports both local and remote MCP servers using HTTP transport, and tools become available progressively as servers load.
What can Amazon Q do with bank data through MCP?
Amazon Q can query transactions, check account balances, analyze spending patterns, generate code using real financial schemas, build AWS infrastructure for data pipelines, and execute multi-tool tasks - all through natural language conversation.
Do I need to write custom integration code?
No. The MCP protocol handles the connection between Amazon Q and BankSync. You just add a JSON configuration with your MCP server URL and API key. No SDKs, no adapters, no custom code required.
Is my financial data secure when using Amazon Q with BankSync?
Yes. BankSync uses encrypted transport, scoped API keys with granular permissions, and never stores banking credentials. You can revoke API key access at any time from the BankSync dashboard.