# Ask the assistant you already use what you spent

URL: https://www.orla.finance/en/mcp
Markdown twin of that page. Append `.md` to any Orla page URL to get one.

The assistant you already use reads your ledger live: balances, budgets, who owes whom. Nothing is copied out, and it cannot pay.

Server URL: https://app.orla.finance/api/mcp/personal. Sign-in happens in your browser, and the connection is one row you can revoke.

#### Eight ways in, one connection behind all of them

- Claude: A custom connector in Settings, nothing to install.
- Claude Code: One command in the terminal, then /mcp to sign in.
- Cursor: One entry in mcp.json, globally or in the repository.
- VS Code: One entry under servers, or one code --add-mcp line.
- Zed: One entry under context_servers in settings.json.
- Windsurf: One entry with serverUrl in the Codeium config.
- Terminal: The CLI itself, and a stdio bridge for clients without HTTP.
- Any agent: A skill file the agent reads itself: one install, every client.

#### Everything you could read on your own

Recomputed on every call against your own permissions, from the tool list the server hands a personal connection.

##### It reads

- Accounts and balances: Every account the spaces you ticked hold, narrowed to what you may see.
- Transactions: Newest first, with date, account, text and uncategorised filters.
- Budgets and net worth: Each budget with the spend against it, and the net worth of the space.
- Who owes whom: Every participant's balance in a shared space, and the shortest set of transfers that settles it.
- The assistant's reports: The assistant's reports: cash forecast, owed and owing, bills due, VAT, balances. It asks for the list, then runs one by name.
- With the same fences: Bank details and addresses come masked unless you approved otherwise, and a connection narrowed to some accounts sees only their figures.
- The approval queue: Payments waiting for a person to sign, read only.
- Fraud findings: Open findings over a business space's crypto payouts, the counterparties and what the detector saw.

##### It records

- Book a transaction: An income or an expense, with a category and a payee.
- Correct one: The category, payee or note; amount, date and account stay as they are.
- Set a budget: Change one budget's amount in the space's base currency.
- Add a shared expense: Who paid and how it divides, in a group or family space.

#### It reads and records. It does not move money

Payment tools are not in a personal connection's list and are refused by name. A prompt hidden in a payee name can reach a wrong entry, never a transfer.

##### Not on the list

- Payments, transfers and swaps: Not offered, and refused by name if asked for.
- Card details: The card and its reveal link are the payment instrument itself.
- The agent's wallet: A float this connection is never given, so the tool is not there to ask.
- A verdict on a fraud finding: Settling one mutes the detector for six months, so a person decides.

##### Yours to set

- Which spaces: Ticked on Orla's own consent page, and narrowed later in the app.
- Approved where it began: A request is approved only in the browser that started it, within about fifteen minutes. A forwarded link shows Started in another browser and no Allow, so a page that arrived from somebody else is one to close.
- No seat on your plan: A personal connection is not an agent and takes no agent seat.
- One row to revoke: Every client connected through it stops at once; the trail of what it did stays.
- An agent that pays: A different thing with its own wallet and its own limits, on the agents page.