Any agent
One file that teaches the agent the door, and where it ends.
Clients differ; the agent behind them does not. The skill names the commands, the JSON envelope, the exit codes and the one rule that paying waits for a person. An agent reads it once instead of guessing.
Server URL: https://app.orla.finance/api/mcp
Setup
Add the server, sign in once.
The URL is all it needs; the sign-in happens in your browser, on Orla's consent page.
The steps
- Install the skill
- npx skills add cheetah-trade/orla-cli puts it where your agent looks. Claude Code takes it as a plugin, with four bookkeeping skills beside it and the personal MCP connection they run on.
- Or just read it
- orla.finance/skill.md is the same file the package ships, served from the published version.
- Then sign in once
- The first orla command opens the browser on Orla's consent page. The skill tells the agent to stop and wait for you there.
terminal
# the skills CLI, into any agent it knows
npx skills add cheetah-trade/orla-cli
# Claude Code: the skill and the MCP server as one plugin
claude plugin marketplace add cheetah-trade/orla-cli
claude plugin install orla@orla
# Claude Desktop: the bundle attached to each release
# https://github.com/cheetah-trade/orla-cli/releases
# or read it
curl -fsSL https://orla.finance/skill.mdThe skill covers both doors: what a personal connection reads and records, and what an agent with a key of its own may do inside its ceilings. It says in plain words that only an executed payment with a reference means the money left.
If the menus have moved, the orla-cli repository is current for the client itself.
What to ask
Questions your ledger can answer for real.
Every figure comes from your own books, and is recomputed each time you ask.
- Record yesterday's 40 EUR taxi to Transport, and tell me the id.
- Which of my spaces does this connection reach?
- Export August as CSV for the accountant.
The client never sees this page: you tick which spaces it may reach, and one row in the app revokes it later. Card numbers and IBANs stay masked unless you switch that on.
The boundary
It reads and records. It does not pay.
An agent that pays is a different connection, with its own wallet and its own limits.
The boundary
- What it reads
- Everything you can read in the spaces you ticked, and nothing outside them.
- What it writes
- Transactions, categories, payees and notes, written straight away.
- What it cannot do
- Pay anyone. The payment tools are not in the list it is given, and are refused by name if asked.
- What it costs
- Nothing, and it takes none of the agent seats in your plan.
Other clients
The same connection, seen from another chair.
- 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.
This page as Markdown, for an agent: https://orla.finance/en/mcp-skill.md
See it on your own books.
Thirty minutes: we connect an account, drop a real bill in, and close a month together.