ABANCA MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Optional local port for the OAuth login session (defaults to 3000). | 3000 |
| CLIENT_ID | Yes | ABANCA OpenBanking CLIENT_ID | |
| CLIENT_SECRET | Yes | ABANCA OpenBanking CLIENT_SECRET | |
| ENCRYPTION_KEY | Yes | A 32-character secret encryption key for secure local storage of OAuth tokens. |
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": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_bank_accountsB | Retrieves a list of bank accounts and their balances. |
| get_account_transactionsC | Retrieves the transactions for a specific bank account IBAN. |
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 2 tools
The two tools have clearly distinct purposes: one retrieves a list of bank accounts with balances, while the other retrieves transactions for a specific account. There is no overlap or ambiguity in their functions, making it easy for an agent to select the correct tool based on the need.
Both tools follow a consistent verb_noun pattern with 'get_' prefix, using snake_case throughout. The naming is predictable and readable, with no deviations or mixed conventions, ensuring clarity and ease of use.
With only two tools, the server feels under-scoped for a banking domain that typically involves operations like creating accounts, updating details, or initiating transfers. This limited set may hinder agents from performing comprehensive banking tasks, indicating a mismatch with the apparent scope.
The tool surface is severely incomplete for a banking server, covering only retrieval of accounts and transactions. Missing are essential CRUD operations such as creating or updating accounts, initiating transfers, or managing payments, which are critical for typical banking workflows and will likely cause agent failures.