n26-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EB_BANK | No | Bank name to use. Defaults to N26. | |
| EB_CACHE | No | Set to 0 to skip the local cache. | |
| EB_APP_ID | Yes | Your Enable Banking application ID. | |
| EB_PSU_IP | No | Your current IP, sent with EB_PSU_USER_AGENT to mark requests as online (both must be set together). | |
| EB_COUNTRY | No | Bank country code. Defaults to DE. | |
| EB_KEY_PATH | No | Absolute path to the Enable Banking private key (.pem) file. Defaults to the n26-mcp config directory if omitted. | |
| EB_PSU_PRESENT | No | Set to 0 for scheduled jobs so requests do not pretend you are online. | |
| EB_SESSION_PATH | No | Absolute path to the session.json file used to store the bank session. | |
| EB_PSU_USER_AGENT | No | The user agent of the browser you are using, sent with EB_PSU_IP to mark requests as online (both must be set together). |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_accountsA | Read-only list of accounts covered by the current bank consent. Returns each account uid, its currency, and the last four IBAN characters from the local session file. It does not call the bank and cannot move money. Show the result only to the account owner. |
| get_balancesA | Read-only balances for the consented accounts. Shows balance type, amount, currency and reference date. There is no payment action. Show the result only to the account owner. |
| get_transactionsA | Read-only transactions for a date range. Follows Enable Banking continuation pages, then returns the newest matching rows only (default 50, maximum 200) so a long history does not fill the context. Filter with search, or narrow date_from and date_to. For a summary, use recurring_charges or the monthly spending resource instead of raising the limit. Debits are negative amounts with direction DBIT. There is no payment action. Show the result only to the account owner. |
| recurring_chargesA | Read-only detection of subscriptions and other recurring charges. Same detector as |
| consent_statusA | Read-only consent expiry: valid until, days left, and a warning. N26 consents last at most 180 days. state is ok, renew_soon, expired or
unknown. This does not renew the consent and cannot move money. Renew with
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| monthly_spending_summary | Draft a monthly spending summary the agent may show only to the account owner. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool maps to a distinct read-only resource: accounts, balances, transactions, recurring-charge detection, and consent expiry. The only mild overlap is between get_transactions and recurring_charges, since the latter is derived from transaction data, but the descriptions explicitly steer agents (use recurring_charges for summaries rather than raising the transaction limit).
Three tools follow a clean verb_noun pattern (list_accounts, get_balances, get_transactions), while recurring_charges and consent_status are noun-phrase names describing derived resources. The deviation is small and every name is self-explanatory, so predictability remains high.
Five tools is well-scoped for a read-only open-banking surface, and each one covers a genuinely different question (which accounts, what balance, what moved, what recurs, is the consent still valid). There is no filler or redundant tool.
The read-only lifecycle is well covered: discovery, balances, paged/filterable transactions, recurring-charge analysis, and consent health including expiry warning. Minor gaps exist (no account-holder details, no dedicated spending-summary tool — it is only referenced as an external resource), but nothing blocks core agent workflows, and payment operations are intentionally out of scope.