akahu-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | Node environment, typically set to 'app'. | app |
| AKAHU_APP_TOKEN | Yes | Your Akahu app token, get it from developers.akahu.nz. | |
| AKAHU_USER_TOKEN | Yes | Your Akahu user token, get it from developers.akahu.nz. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_accountsA | List every bank account this server has access to via Akahu, with their current and available balance. Unrestricted - not limited to a specific allowlist. Takes no arguments. |
| bank_get_balanceA | Get the current and available balance for one bank account by its Akahu account ID. Use list_accounts to find the ID. |
| bank_get_transactionsA | Get settled (posted) transactions for one bank account by its Akahu account ID, optionally within a date range. Dates are ISO 8601 (e.g. "2026-06-01"). start is exclusive, end is inclusive, matching Akahu semantics. Omit both to get all transactions the app can access (up to its historical access window). |
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 3 tools
Each tool serves a distinct purpose: listing accounts, fetching a single account's balance, and fetching a single account's transactions. No overlap or ambiguity between them.
Tool names follow a mostly consistent snake_case pattern with verb-noun structure, but two use the 'bank_get_' prefix while 'list_accounts' deviates slightly. The inconsistency is minor and does not hinder understanding.
Three tools is an appropriate size for a banking read-only integration, covering the essential operations without unnecessary bulk. Each tool earns its place.
The tool set covers the core read-only banking needs: account listing with balances and transaction retrieval. Minor gaps exist (e.g., no direct account details endpoint, no cross-account transaction aggregation), but these are not critical for the apparent purpose.