mcp-upbank

This MCP server exposes the Up Bank API through the Model Context Protocol, allowing you to query banking data without mutating it. After starting the server, you can use your MCP client to request read-only resources such as daily transactions, account balances, and other transaction history provided by the Up Bank API. The implementation leverages the Up Bank OpenAPI spec and a pagination handler to deal with opaque cursors, so you can fetch larger result sets in chunks and navigate through pages as needed. To begin, supply your Personal Access Token (PAT) as an environment variable when running the server; the token authenticates requests to Up Bank on your behalf. The server is designed to be read-only to minimize risk, aligning with Up Bank's API limitations that do not support mutating operations via this interface.

Typical use cases include pulling a day’s transactions for journaling, comparing spending across different months, and analyzing spending patterns. Since the API does not allow mutations, you can rely on the MCP client to aggregate and analyze data locally or feed it into prompts and workflows without altering your Up Bank data.

Prerequisites:

• Node.js (recommended: LTS version, e.g., 18.x or newer)
• npm (comes with Node.js) or pnpm/yarn if preferred
• An Up Bank Personal Access Token (PAT) with read access to transactions

Installation steps:

1. Clone the repository git clone https://github.com/your-org/mcp-upbank.git cd mcp-upbank

2. Install dependencies npm install

3)Configure environment

• Create a shell environment variable for your Up Bank PAT
• Example (bash): export UP_API_TOKEN="your-personal-access-token-here"
• Alternatively, create a .env file if the server supports loading it and populate UP_API_TOKEN accordingly

4. Run the server

   • If the server is started via a single entry script (as suggested by the MCP config): node path/to/server.js
   • If a start script is defined in package.json, you can use: npm run start

5. Verify locally

   • Ensure the server boots without error and is reachable by your MCP client at the configured endpoint.

Note: The exact server entry path (path/to/server.js) may differ in your setup; adjust accordingly based on your repository layout.

Security and usage tips:

• Never share your Up Bank Personal Access Token. Treat it as a password and store it securely (e.g., environment variables, secret managers).
• The server is intended for read-only use; mutations are not supported by the Up Bank API and are not exposed via this MCP implementation.
• If you encounter pagination issues, the server uses opaque cursors; ensure your MCP client handles paging correctly and stores/propagates cursors between requests.
• If using Smithery.ai or similar tooling to generate a config, you can replace the example config with the one produced by your client, but keep the PAT handling secure.
• Check rate limits from the Up Bank API to avoid throttling; consider implementing retry logic in your client.
• Update guidance: periodically review the OpenAPI spec and adjust pagination or field mappings if Up Bank updates their API.