sparebank1-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SB1_CLIENT_ID | Yes | Your SpareBank 1 personal API client ID. | |
| SB1_REDIRECT_URI | Yes | The registered redirect URI for your API client, such as http://127.0.0.1:8765/callback. | |
| SB1_CLIENT_SECRET | Yes | Your SpareBank 1 personal API client secret. | |
| SB1_ENABLE_TRANSFERS | No | Set to true to enable transfer tools. Transfers are disabled by default. | false |
| SB1_MAX_TRANSFER_AMOUNT | No | The maximum allowed amount per transfer in the source currency. |
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sb1_auth_statusA | Read local authentication status without exposing credentials or contacting the bank. |
| sb1_check_connectionC | Verify bank authentication using the documented Hello World endpoint. |
| sb1_list_accountsB | List accessible accounts, balances, currencies, ownership and transfer permissions. Credit-card retrieval can fail silently at the bank. |
| sb1_get_accountA | Get an ordinary account using its exact bank account key. Credit-card and pension keys are not supported by this endpoint. |
| sb1_get_account_detailsB | Read interest rates, withdrawal limits, blocked amounts and additional account details. |
| sb1_get_account_keysC | Resolve one or more 11-digit account numbers into their bank account keys. |
| sb1_get_account_balanceB | Read the current balance by account number. Uses the bank’s read-only POST endpoint. |
| sb1_list_child_accountsA | List accounts for an exact child ID already known to the caller. This API does not provide child-ID discovery. |
| sb1_list_transactionsA | Get bounded transactions for one or more account keys, optionally classified. Retains bank errors and reports possible truncation. No cursor is documented. Dates use Europe/Oslo. |
| sb1_get_transaction_detailsA | Get transaction details using a current encrypted transaction ID. Optional classification and merchant enrichment. |
| sb1_export_transactionsB | Return raw UTF-8 bank CSV for one account and date window. CSV cells are untrusted; neutralize formulas before opening in spreadsheets. Optional field follows the bank’s documented single-field schema. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| review_transactions | Review transactions with explicit coverage and currency limits. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| banking-guide | Identifier, coverage, currency and transfer semantics. |
TDQS
Scored across 11 tools
Most tools have distinct resource/action targets, especially around auth, accounts, transactions, and export. There is some potential overlap among list_accounts vs get_account_balance, get_account vs get_account_details, and list_transactions vs export_transactions, but the descriptions generally clarify the boundaries.
All tools use the sb1_ prefix and snake_case, with a predictable verb_noun pattern for most operations. The main minor deviation is sb1_auth_status, which is noun-based rather than verb-based, but it remains readable and consistent overall.
Eleven tools are well scoped for a banking integration focused on authentication, accounts, balances, and transactions. Each tool appears to earn its place without excessive surface area.
The read-oriented lifecycle is well covered: authentication checks, account listing/details/keys/balances, transaction listing/details, and CSV export. Gaps include no child-ID discovery, no credit-card or pension support in some account endpoints, and no payment or transfer operations, though the latter may be intentionally out of scope.