open-banking-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRUELAYER_ENV | Yes | Environment to use: 'sandbox' or 'production' | |
| TRUELAYER_PSU_IP | No | End user's IP; lifts rate limits for user-present calls | |
| TRUELAYER_SCOPES | No | Space-separated scope list | all Data API scopes |
| TRUELAYER_CLIENT_ID | Yes | Your TrueLayer client ID, e.g. sandbox-yourapp | |
| TRUELAYER_PROVIDERS | No | Which banks to offer at consent | uk-cs-mock |
| TRUELAYER_CACHE_FILE | No | Local SQLite cache file path | ~/.open-banking-mcp/cache.db |
| TRUELAYER_TOKEN_FILE | No | Path to token file. Implies file storage. | ~/.open-banking-mcp/tokens.json |
| TRUELAYER_USE_KEYRING | No | Set 0 to store tokens in a file | 1 |
| TRUELAYER_HISTORY_DAYS | No | How far back a full sync pulls | 365 |
| TRUELAYER_REDIRECT_URI | No | OAuth redirect URI. Must match byte for byte what the server sends. | http://localhost:8080/callback |
| TRUELAYER_CLIENT_SECRET | Yes | Your TrueLayer client secret | |
| TRUELAYER_MAX_AGE_HOURS | No | Age past which cached data is flagged stale | 25 |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_banksB | List connected banks and when each was last synced. |
| list_accountsA | List bank accounts, with sort code and account number where available. Set fresh=true to bypass the local cache and query the bank directly. |
| list_cardsC | List credit and debit cards. |
| get_balanceB | Get the current and available balance for one account. Use fresh=true when the answer must reflect a payment made moments ago. |
| get_card_balanceC | Get a card's balance, credit limit and payment due details. |
| get_balancesC | Get balances for every account and card at once -- the 'how am I doing' view. |
| get_transactionsA | Query transactions across accounts and cards. Dates are YYYY-MM-DD and the range is inclusive. |
| list_standing_ordersB | List standing orders on an account (Open Banking providers only). |
| list_direct_debitsC | List direct debits on an account (Open Banking providers only). |
| get_identityC | Get the account holder's identity as the bank holds it. |
| sync_nowA | Pull everything from the bank into the local cache. Normally a scheduled job does this daily; call it when you need the whole cache refreshed rather than one account. |
| cache_statusA | Show what the local cache holds and when it was last refreshed. |
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 12 tools
Each tool targets a distinct resource or aggregation level: banks, accounts, cards, individual balances, aggregate balances, transactions, standing orders, direct debits, identity, and cache operations. Although get_balance, get_card_balance, and get_balances all relate to balances, their scopes are clearly separated by description.
Most tools follow a predictable verb_noun pattern (list_banks, get_balance, list_standing_orders). Two outliers—sync_now and cache_status—break the pattern slightly, but the overall set remains readable and consistent.
12 tools is well within the typical 3-15 range for a focused domain server and each tool earns its place by covering a distinct part of the open banking read surface.
The server provides broad read-only coverage for open banking data: banks, accounts, cards, balances, transactions, standing orders, direct debits, identity, and cache management. Minor gaps exist—such as payment initiation, payee/beneficiary listing, or individual transaction lookup—but these are likely outside the intended read-only scope.