mcp-server-enablebanking
by borgels
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HTTP_TOKEN | No | Upstream token held by the gateway that authenticates users and forwards X-MCP-User for the HTTP transport. | |
| ENABLEBANKING_COMPANY | Yes | Pins the instance to one company. No tool takes a company argument. | |
| ENABLEBANKING_AUDIT_LOG | No | Path where each tool call is written with company, user, tool and account id; arguments are hashed, and balances, transactions and the consent code are never logged. | |
| ENABLEBANKING_REDIRECT_URL | No | A URL registered with the Enable Banking application where the consent redirect must land. Nothing has to listen there; the admin copies the address from the browser into enablebanking_complete_consent. | |
| ENABLEBANKING_ACCOUNTS_PATH | Yes | Path to the account registry file (e.g. deploy/accounts.example.json). One file for all companies: CVR, name, and the IBANs that belong to each. The account registry decides which account belongs to which company. | |
| ENABLEBANKING_CACHE_SECONDS | No | Answers are cached per account and query for this many seconds. | 300 |
| ENABLEBANKING_CONSENT_ADMINS | No | Optional list of consent admins that further gates the consent tools. | |
| ENABLEBANKING_ENABLE_CONSENT | No | Set to true to enable the consent tools (enablebanking_list_banks, enablebanking_start_consent, enablebanking_complete_consent, enablebanking_refresh_consent, enablebanking_revoke_consent). | false |
| ENABLEBANKING_TRUST_FORWARDED_USER | No | When true, every request must carry the verified user in X-MCP-User; requests without it are refused. Use behind an authenticating MCP gateway. | false |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues