Integration

Up Banking integration

Up is an Australian digital bank, and its API gives a customer access to their own banking data. List accounts (spending, Saver, home loan, individual or 2Up joint) with their balances; list transactions across every account or for one account, filtered by date range, status (HELD or SETTLED), category or tag; and read a transaction's detail, such as foreign currency amount, Round Up, cashback, card used and note. Browse the spending category tree and the receipt attachments. Writes are limited to organising: categorize a transaction, add or remove tags on it (at most 6 per transaction), and manage webhooks that push transaction events (created, settled, deleted) to a URL, with their delivery logs and a test ping. The API cannot move money, and removing a transaction's category (the vendor's null body) is not exposed. Authentication is a Personal Access Token the customer generates in the Up app (Data sharing), sent as a Bearer token.

Connect Up Banking How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Up Banking.Built from the 20 Up Banking tools below, on the connection you add once.

What you can do with Up Banking

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Webhook, 5 operations

create_webhookCreate webhookPOSTCreates a webhook that receives transaction events (created, settled, deleted) as JSON POST requests at the given URL, which must answer HTTP 200. At most 10 webhooks can exist at a time.
delete_webhookDelete webhookDELETEDeletes a webhook; events are no longer sent to its URL. Returns no content on success (HTTP 204).
get_webhookGet webhookGETRetrieve a specific webhook by providing its unique identifier.
list_webhooksList webhooksGETLists the configured webhooks, oldest first. The signing secretKey is never included. Paginated: when links.next is set, call again with its page[after] cursor to get the next page.
ping_webhookPing webhookPOSTSends a PING event to a webhook, to test that its URL receives events. The event is delivered asynchronously; the response returns the event that was sent. Check the outcome with list_webhook_logs.

Transaction, 4 operations

categorize_transactionCategorize transactionPATCHSets the category of a transaction. Only transactions whose isCategorizable attribute is true can be categorized, and the category must be a sub-category from list_categories, never a top-level (parent) one.
get_transactionGet transactionGETRetrieve a specific transaction by providing its unique identifier.
list_account_transactionsList account transactionsGETLists the transactions of one account, newest first. Narrow them by date range (filter[since], filter[until]), status, category or tag; the date filters are not a way to page.
list_transactionsList transactionsGETLists transactions across all of the customer's accounts, newest first. Narrow them by date range (filter[since], filter[until]), status, category or tag; the date filters are not a way to page.

Tag, 3 operations

add_transaction_tagsAdd transaction tagsPOSTAdds one or more tags to a transaction. A transaction carries at most 6 tags; tags already on it are silently ignored.
list_tagsList tagsGETLists every tag currently in use, in lexicographic order. A tag's id is its label. Paginated: when links.next is set, call again with its page[after] cursor to get the next page.
remove_transaction_tagsRemove transaction tagsDELETERemoves one or more tags from a transaction. Tags that are not on the transaction are silently ignored. Returns no content on success (HTTP 204).

Account, 2 operations

get_accountGet accountGETRetrieve a specific account by providing its unique identifier.
list_accountsList accountsGETLists the customer's accounts (spending, Saver or home loan, individual or 2Up joint) with their available balance. Filter by account type or ownership. Paginated: when links.next is set, call again with its page[after] cursor to get the next page.

Attachment, 2 operations

get_attachmentGet attachmentGETReturns one attachment: a temporary download link (fileURL) valid until fileURLExpiresAt, the file type, and the transaction it belongs to.
list_attachmentsList attachmentsGETLists the files (usually receipts) attached to transactions, each with a temporary download link and its expiry time. Paginated: when links.next is set, call again with its page[after] cursor to get the next page.

Category, 2 operations

get_categoryGet categoryGETRetrieve a specific category by providing its unique identifier.
list_categoriesList categoriesGETLists Up's predefined spending categories with their parent and sub-categories. Only a sub-category can be assigned to a transaction. Use filter[parent] to list the children of one parent. Not paginated.

Access token, 1 operation

pingPingGETChecks that the access token works. Returns the id of the authenticated customer and a status emoji; an invalid token is refused with HTTP 401.

Log, 1 operation

list_webhook_logsList webhook logsGETLists the delivery attempts of one webhook, newest first: the request body sent, the response received and the delivery status. Logs may be purged after a period of time.

Use Up Banking from Claude Code, Cursor or Codex

Connect Up Banking in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Up Banking operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Up Banking

Create your workspace
Sign up free. Nothing to install.
Connect Up Banking once
Add your Up Banking connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.