Up Banking MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UP_API_TOKEN | Yes | Your Up Banking personal access token for API authentication |
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 |
|---|---|
| up_pingA | Test the Up API connection and verify authentication is working |
| up_list_accountsB | List all accounts for the authenticated user. Returns account balances, types (SAVER, TRANSACTIONAL, HOME_LOAN), and ownership information. |
| up_get_accountB | Get details for a specific account by ID, including current balance and account information. |
| up_list_transactionsA | List transactions across all accounts or for a specific account. Supports filtering by status, date range, category, and tags. Returns paginated results ordered newest first. |
| up_get_transactionB | Get detailed information about a specific transaction by ID, including amount, description, category, and related account. |
| up_list_categoriesA | List all spending categories in Up. Categories have a parent-child relationship. Use this to understand category IDs for filtering transactions. |
| up_get_categoryB | Get details about a specific category by ID, including its name and parent/child relationships. |
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 7 tools
Every tool has a clearly distinct purpose with no ambiguity. The tools are organized around three main resources (accounts, categories, transactions) with specific get and list operations for each, plus a separate ping utility. The descriptions clearly differentiate between retrieving single items by ID versus listing multiple items with filtering options.
All tools follow a perfectly consistent 'up_verb_noun' pattern throughout. The verb-noun combinations are logical and predictable (get_account, list_accounts, get_category, list_categories, etc.), with consistent snake_case formatting. The ping tool also fits this pattern as a special case.
Seven tools is an ideal number for this banking API server. It provides complete coverage for the three core resource types (accounts, categories, transactions) with both get and list operations, plus a connection test utility. Each tool earns its place without being overwhelming or insufficient.
The toolset provides excellent read-only coverage for the banking domain with get and list operations for all major resources. The only minor gap is the absence of write operations (create/update/delete transactions or accounts), but this is likely intentional for a banking API focused on data retrieval rather than modification. The surface covers all essential querying workflows.