The short answer is yes. BankSync supports Australian bank connections in Claude through its Model Context Protocol (MCP) server.
The connection has two separate trust layers:
- Australian bank → BankSync: connect through the Consumer Data Right (CDR) using the bank-hosted consent flow.
- BankSync → Claude: let Claude call BankSync’s read-only MCP tools using an API key whose scopes and expiry you control.
Claude never needs your online-banking password. BankSync acts as a CDR representative of Fiskil Pty Ltd, an Accredited Data Recipient, while the MCP connection exposes only the BankSync data and tools permitted by your workspace key.
This guide reflects BankSync’s current Australian MCP availability as at 23 August 2026.
Ways to use Australian bank data with Claude
| Feature | Method | Recommendation | What happens |
|---|---|---|---|
| BankSync MCP | BankSync MCP | Claude queries authorised BankSync transactions, balances, accounts and supported finance data. | |
| Spreadsheet or file | Spreadsheet or file | Useful for a fixed snapshot | Claude analyses only the rows shared and the result is only as current as the file. |
| Paste bank credentials | Paste bank credentials | Never appropriate | Passwords and one-time codes belong only in the bank or regulated provider’s secure flow. |
Connect an Australian bank account to Claude
Connect your Australian bank in BankSync
Open the Banks page, search for the exact institution and complete the bank-hosted CDR consent. Review the requested data, select the accounts to share and approve read-only access.
Confirm the connection
Check that the selected accounts appear in BankSync and that recent balances or transactions are available before configuring Claude.
Create a scoped API key
Go to Settings → Developers, create a separately named key for Claude, choose an expiry and grant only the scopes required. Copy it when shown and treat it like a password.
Add BankSync MCP to Claude
Install the BankSync .mcpb bundle in Claude Desktop where available, or configure the remote MCP server at https://mcp.banksync.io with the API key in the X-API-Key header.
Test a narrow query
Ask Claude to list the available accounts or state the latest balance date. Compare the result with BankSync before requesting broader analysis.
Build repeatable workflows
Ask for spending summaries, merchant searches, balance comparisons or transaction reviews. Require the answer to state the accounts and date range used.
CDR bank consent
You choose the Australian institution, accounts, data types and consent period through the regulated flow.
Scoped MCP access
A BankSync API key controls which MCP tools Claude may call and can be expired or revoked.
Read-only data
The workflow queries supported financial information and does not give Claude authority to move money.
Current source
Claude queries BankSync rather than relying only on a manually exported file, subject to bank-data freshness.
What can Claude do with the connection?
Useful requests are precise questions over a known set of accounts and dates:
- “List the Australian accounts available to this connection and the latest balance date for each.”
- “Summarise non-transfer outflows from my everyday account for the last complete calendar month.”
- “Find transactions from a merchant name containing ‘Telstra’ and return the date, account and amount.”
- “Compare total inflows and outflows across the last three complete months.”
- “Show the largest transactions in this period and separate transfers from external spending.”
- “State any gaps or uncertainty in the available data before calculating the result.”
Exact fields, history and freshness depend on the connected institution, account type and CDR permissions. MCP improves access to source data, but it does not fix a missing account, an expired consent or an ambiguous transfer automatically.
CDR details Australian users should understand
Consent is account-specific and time-limited
Select only the accounts and data types needed. If the consent expires or is withdrawn, reconnect through the bank and re-select every account that should remain available.
Revoking one layer does not revoke the other
Withdrawing CDR consent stops future bank-data access. Revoking the BankSync API key stops Claude calling BankSync. For a complete shutdown, do both where appropriate.
Verification still matters
Ask Claude to state the accounts, earliest and latest dates, latest refresh timestamp and supporting transactions behind every important conclusion. Verify material financial decisions against the underlying records.
A simple verification routine
| Check | Ask Claude | Verify |
|---|---|---|
| Account scope | Which accounts did you use? | They match the connected BankSync accounts. |
| Date range | What are the earliest and latest dates? | The full requested period is present. |
| Freshness | What is the latest balance or transaction timestamp? | The bank connection has refreshed recently. |
| Transfers | Which rows were treated as internal transfers? | Account-to-account movements were not counted as spending. |
| Evidence | Return the supporting transactions. | Amounts and descriptions match the source. |
Run these checks before relying on an AI-generated financial summary.
Australian bank accounts and Claude: FAQs
Sources and current product guidance
- BankSync: Australian bank data in Claude via MCP
- BankSync: connect a bank
- BankSync: manage CDR consents
- Australian Government: Consumer Data Right
The bottom line
You can connect an Australian bank account to Claude through BankSync.
The correct path is Australian bank → CDR consent → BankSync → scoped MCP API key → Claude. Keep both the bank consent and MCP key narrowly scoped, begin with a simple verification query and make Claude state the accounts, dates and evidence behind important answers.