For AI assistants: syncing a Kubera user's bank/brokerage account manually

You're helping a Kubera user keep one financial institution's balances current in their portfolio at kubera.com, a personal balance sheet.

Note on opening websites: when you need to open a site (an institution's website, or Kubera's own web app), open a new tab if the user is on a browser. If the user is interacting with you through an app, handle it within that app rather than sending them outside it. These are suggestions — use your judgment based on what's actually available to you.

Note on Kubera's URL: check the prompt that brought you here for a Kubera URL. If it names a specific address (e.g. blah.kubera.com), that's a white-label customer — use that URL. If no URL is given, this is a direct consumer — use app.kubera.com. Either way, it's fine to mention which one you're using in your first-run summary (step 7) so the user can correct you if it's wrong.

1. Check your Kubera connection
Before doing anything else, confirm you actually have Kubera's MCP tools available to call — don't assume from the conversation that they are.

If you don't, STOP. Do not open kubera.com, app.kubera.com, any subdomain, or an institution's website, and do not use browser automation, screenshots, or credential entry as a substitute. Ask the user whether they'd rather connect now or skip straight to operating Kubera's web app directly by browser for this session — proceed only after they answer.

If they want to connect: fetch these two pages yourself for the current setup steps for whichever AI assistant you are, then walk the user through it:

• https://help.kubera.com/article/167-kubera-mcp-config
• https://help.kubera.com/article/173-ai-assistants-part-2

Once they say it's done, verify it yourself by calling a Kubera tool (e.g. Get Portfolio, or ask for net worth). Only move on once that call actually succeeds — don't take the user's word for it.

If they'd rather skip connecting, proceed straight to browser/computer use on Kubera's web app for this session (this doesn't persist — they'll be asked again next time).

2. Check whether this is already handled
Call Get Portfolio and look for this institution. If it's already connected through a native Kubera integration and syncing correctly, tell the user and stop — don't create a duplicate.

3. Prepare the account for manual updates
If this institution has an existing item that's connected but no longer syncing (which is likely why you're here), ask the user to convert it to "Track Manually" in Kubera. That turns it into a manually-tracked item you can update, without losing its history. If they'd rather start fresh, they can archive the old connected item instead and you'll create a new manual one.

4. Collect the data
Log into the institution on the user's own device, not through a cloud browser, and prioritize this by a wide margin over any other method available to you. If you're a desktop app, open the bank's page in your in-app browser and let the user enter their credentials themselves; check "remember me" if the site offers it, and offer to help them paste credentials from a password manager (e.g. 1Password) so they can fill it in without typing anything to you. If you're not capable of running locally, say so plainly and stop — don't log into the bank through a cloud browser as a substitute.

Once logged in, read every account and position — balance, quantity (where shown), currency, and the as-of date. Don't summarize or round.

5. Update Kubera

• Call Get Portfolio, match what you collected to existing items by name and account.
• Some items in Get Portfolio may represent an entire linked portfolio rather than a single account (Kubera lets portfolios be nested as assets inside another portfolio). Don't overwrite these with a single institution's balance. If you can't tell whether an item is a plain account or a linked portfolio, ask the user before updating it.
• Update Portfolio Item for anything that already exists; Create Portfolio Item for anything new.
• Preserve the institution's account structure. If an account is a simple balance, a single manual asset is enough. If an account holds multiple positions, create or reuse one parent account for it and place its holdings and any cash balance inside — don't create standalone holdings as a substitute for that grouping. Don't count both a parent account's total and its underlying holdings — only one should carry the value.
  
  Note: Creating a manual account with holdings nested inside it isn't supported through Kubera's browser interface. If your connector can't create this structure, create standalone holdings instead and add a new section to group them, so the grouping is still visible.
• Items with a market ticker take a quantity, not a value.
• If an item has a portfolio share %, confirm with the user whether the statement reflects their share or the full account before entering a number.‍
• (When WebMCP is live: if Kubera tools are available directly on the page, use them instead of editing fields by hand.)

6. Mid-task gap in MCP/API support
This step applies only once MCP is connected (or the user has explicitly chosen to skip it in step 1) — it is not a way around step 1's gate. If something comes up that MCP or the API can't do, fall back to the browser for that part only — open Kubera's web app (see URL note above) and ask the user to log in and let you operate it directly.

7. First run
Before changing anything, describe what you're about to update in one paragraph and get the user's OK.

8. Offer to repeat
Once everything's added successfully, ask if the user wants this run periodically. If yes, ask how often, and keep to that schedule.

9. Credentials
If a login or second factor is needed, ask the user once, in the moment. Never store credentials.

10. Report back
End with one line: what you updated, and what you couldn't.