bank-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRUELAYER_ENV | No | The TrueLayer environment to use: 'live' or 'sandbox'. | live |
| BANK_TOKEN_PATH | No | The path to the token JSON file. Defaults to ~/.bank-mcp/tokens.json. | |
| BANK_MAX_RANGE_DAYS | No | The longest date range a single transaction query may span. | |
| TRUELAYER_CLIENT_ID | Yes | Your TrueLayer Console client ID. | |
| TRUELAYER_PROVIDER_ID | No | The TrueLayer provider ID. Normally set automatically per bank when the bank is linked. | |
| TRUELAYER_CLIENT_SECRET | Yes | Your TrueLayer Console client secret. | |
| BANK_TRUELAYER_REFRESH_TOKEN | No | An optional refresh-token seed. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_connectionsA | List linked banks with consent expiry. Banks needing re-linking say 'reconnect_required'. |
| list_accountsA | List accounts and cards. |
| get_balanceC | Balances. |
| list_transactionsA | Transactions with since <= date < before (ISO dates; default the last 30 days), oldest first.
Page with |
| list_pendingC | Pending (not yet settled) transactions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Most tools target clearly distinct data: connections, accounts, balances, transactions, pending items. list_transactions and list_pending overlap in domain (both return transactions), but descriptions make the settled vs. unsettled distinction clear, so confusion is limited.
All five tools follow a consistent verb_noun pattern: list_connections, list_accounts, list_transactions, list_pending, and get_balance. Predictable and easy to scan.
Five tools is well-scoped for a read-only banking data surface; each tool covers a distinct query need without bloat.
The read surface is solid: consent status, accounts, balances, settled and pending transactions, with pagination on the one listing that needs it. Minor gaps exist—no account detail/routing info, no transaction lookup by merchant or ID, and no write operations like transfers, though those may be intentionally out of scope.