Up MCP Server

⚠️ SECURITY & PRIVACY DISCLAIMER ⚠️

This MCP server exposes your Up Bank financial data to Large Language Models (LLMs) like Claude. By using this server, you acknowledge and accept the following risks:

• Data Exposure: Your financial transactions, account balances, and banking information will be sent to and processed by LLM providers
• Training Data: LLM providers may use this data for model training, improvement, and other purposes
• Third-Party Processing: Your financial data will be processed by third-party AI services beyond your control
• No Data Protection: This project provides no encryption, anonymization, or data protection measures
• Use at Your Own Risk: You are solely responsible for the security and privacy of your financial data

This project is NOT responsible for:

• Keeping your financial data safe or private
• Preventing data breaches or unauthorized access
• Ensuring compliance with financial privacy regulations
• Any consequences of sharing financial data with AI services

Only use this server if you fully understand and accept these risks.

---

This is a Model Context Protocol (MCP) server that exposes tools for the Up Bank API.

Setup

1. Create a Personal Access Token from the Up developer portal.
2. Create a .env file next to package.json and add:

# Required: Your Up Bank Personal Access Token
UP_TOKEN=your_up_token_here

# Optional: Webhook local server configuration (defaults shown)
WEBHOOK_PORT=8787
WEBHOOK_PATH=/webhook

3. Install and build:

npm install
npm run build

Environment Variables

Variable	Required	Default	Description
UP_TOKEN	✅ Yes	-	Your Up Bank Personal Access Token
WEBHOOK_PORT	❌ No	8787	Port for local webhook receiver
WEBHOOK_PATH	❌ No	/webhook	Path for local webhook receiver

Run

Run under MCP via stdio (e.g., via a client that supports MCP). You can also run it directly for ad-hoc testing:

npm start

Tools

• up_ping
• up_accounts_list, up_accounts_get
• up_transactions_list, up_transactions_get, up_transactions_categorize
• up_tags_list, up_tags_add_to_transaction, up_tags_remove_from_transaction
• up_categories_list
• up_attachments_list, up_attachments_get
• up_webhooks_list, up_webhooks_create, up_webhooks_get, up_webhooks_delete, up_webhooks_ping, up_webhooks_logs
• up_webhooks_start_local_receiver

Webhooks

When creating a webhook via the Up API, capture the secretKey from the response. Use the up_webhooks_start_local_receiver tool with that key to start a local Express server that verifies X-Up-Authenticity-Signature per Up docs and logs events.

The local webhook server will use the WEBHOOK_PORT and WEBHOOK_PATH environment variables if set, otherwise defaults to port 8787 and path /webhook.

Refer to the official docs for event types and signature verification: https://developer.up.com.au/.