Open Banking MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRUELAYER_CLIENT_ID | Yes | Your TrueLayer client ID | |
| TRUELAYER_CLIENT_SECRET | Yes | Your TrueLayer client secret |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_data_auth_linkB | Create a TrueLayer OAuth authorization URL for data access. |
| exchange_codeA | Exchange OAuth authorization code for access and refresh tokens (legacy alias). |
| complete_code_exchangeB | Complete PKCE OAuth authorization code exchange with state validation. |
| get_accountsB | List all user bank accounts. |
| list_accountsA | Return 1-2 dummy accounts with proper schema validation. |
| get_transactionsB | Get transactions for a specific account within a date range. |
| list_transactionsD | Read sample CSV, normalize rows → Transaction[] with schema validation. |
| export_hmrc_csvA | Export transactions as HMRC-ready CSV with categorization and summary. |
| list_consentsA | List all active user consents with their purposes and expiration dates. |
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 9 tools
exchange_code and complete_code_exchange overlap almost entirely (one is a legacy alias), and get_accounts/list_accounts plus get_transactions/list_transactions have similar names but differ in real vs. dummy behavior, creating confusion. An agent could easily select the wrong tool without careful description inspection.
The pattern is mostly verb_noun, but the use of both get_ and list_ prefixes for closely related actions, along with exchange_code versus complete_code_exchange, shows inconsistent verb choice. The 'legacy alias' note further muddies the name convention.
With 9 tools, the server is well-scoped for Open Banking operations covering auth, accounts, transactions, consents, and export. Each tool has a place, and the count is neither too small nor excessive.
The surface covers the core lifecycle: OAuth authorization, code exchange, account listing, transaction retrieval, CSV export, and consent listing. Notable gaps include consent revocation and token refresh, which are minor but would round out the workflow.