interbanking-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IB_CLIENT_ID | Yes | Interbanking client ID from the developer portal | |
| IB_CUSTOMER_ID | Yes | Interbanking customer ID | |
| IB_REDIRECT_URL | Yes | OAuth redirect URL, for example https://localhost | |
| IB_CLIENT_SECRET | Yes | Interbanking client secret from the developer portal |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| listar_cuentasA | Lista las cuentas bancarias disponibles con su banco, tipo, moneda y numero. Util como primer paso para saber que cuentas existen antes de pedir movimientos. |
| saldosA | Saldos actuales de todas las cuentas: contable, operativo y proyectado. Acepta un rango de fechas opcional de hasta 64 dias; para rangos mas largos usar saldos_historicos. |
| saldos_historicosA | Saldos diarios en un rango de fechas largo. Parte el rango automaticamente en tramos de 60 dias porque la API no acepta mas de 64 por consulta, y devuelve la serie unificada. Devuelve un resumen por cuenta; usar detalle para la serie dia por dia. |
| movimientosA | Movimientos de todas las cuentas en un rango de fechas. Descubre las cuentas solo. Por defecto devuelve un resumen (totales por cuenta y los 25 mas recientes); pedir detalle solo para rangos cortos, porque un rango largo son miles de registros. |
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 4 tools
Each tool targets a distinct facet: listing accounts, current balances, historical daily balances, and movements. The descriptions explicitly clarify the boundary between saldos and saldos_historicos by date-range length, so an agent can select correctly.
listar_cuentas follows a verb_noun pattern, while saldos, saldos_historicos, and movimientos are noun phrases. The names are all snake_case and readable, but they do not follow one predictable convention.
Four tools are well-scoped for a read-only banking information surface. Each tool earns its place by covering a separate capability: account discovery, current balances, historical balances, and movements.
The surface covers the core read-only workflows: accounts, balances, historical balances, and movements. Minor gaps exist, such as no explicit account-filtered movement or balance query, but agents can work around them using the all-accounts responses.