home / mcp / up banking mcp server
an mcp server to run locally for your up bank in Australia, used with claude
Configuration
View docs{
"mcpServers": {
"alex1092-up-bank-mcp-server": {
"command": "node",
"args": [
"/absolute/path/to/up-mcp-server/build/index.js"
],
"env": {
"UP_API_TOKEN": "your_up_api_token_here"
}
}
}
}You provide a dedicated MCP server that lets Claude access your Up Banking data. This server exposes read-only operations for accounts, transactions, and categories, enabling practical, secure querying and integration without exposing your credentials directly to clients.
You connect an MCP client to the Up Banking MCP Server to read accounts, balances, transactions, and category information. Use the configured server to ask questions like your current balance, recent transactions, or spending by category. Your client will relay requests to the MCP server, which returns structured results suitable for natural language queries and data-driven insights.
Prerequisites: you need Node.js 18 or higher, an Up bank account, and an Up personal access token.
Step 1. Prepare your environment - Ensure Node.js 18+ is installed on your system - Have your Up personal access token ready and securely stored - Create a project directory for the MCP server files if you haven’t already
Step 2. Install dependencies and build - Open a terminal - Navigate to the MCP server directory - Install dependencies - Build the server
Step 3. Run the server using one of the provided configurations
- You can run the server locally via Node or via NPX with the token configured as shown below.{
"mcpServers": {
"up-banking": {
"type": "stdio",
"command": "node",
"args": ["/absolute/path/to/up-mcp-server/build/index.js"],
"env": {
"UP_API_TOKEN": "your_up_api_token_here"
}
}
}
}
```
```json
{
"mcpServers": {
"up-banking": {
"type": "stdio",
"command": "npx",
"args": ["-y", "/absolute/path/to/up-mcp-server"],
"env": {
"UP_API_TOKEN": "your_up_api_token_here"
}
}
}
}Two common startup configurations are provided. Choose the one that fits your workflow and environment. Ensure the UP_API_TOKEN is set in the environment for both options.
Claude Desktop configuration is used to connect the MCP server with your Claude client. You reference the absolute path to your server or run it via NPX, and you supply your Up API token in the environment.
Your Up API token provides read access to your banking data. Treat it as a secret: do not commit it to version control, and prefer environment variables or secure configuration management. Tokens can be revoked at any time.
If you encounter issues, verify that the path to your build/index.js is correct, ensure the configuration JSON is valid, restart the client, and check logs for error messages.
The server exposes read operations to list and query accounts, transactions, and categories. Key capabilities include: pinging to verify connectivity, listing accounts with optional filters, retrieving account and transaction details, listing categories, and filtering transactions by date, status, category, and tags.
Use natural language queries to ask Claude for your current balance, recent transactions, or category spending insights once the server is configured and connected.
For development with automatic recompilation, you can run the project in watch mode if you have the appropriate setup. Restart Claude Desktop after configuration to ensure the MCP server loads correctly.
Test the API connection and verify authentication is working.
List all accounts with optional filtering by account type or ownership.
Get detailed information about a specific account.
List transactions with comprehensive filtering options including account, status, date range, category, and tags.
Get detailed information about a specific transaction.
List all spending categories in Up.
Get details about a specific category.