VS Code
Books that answer in the chat panel
VS Code takes MCP servers in .vscode/mcp.json under a servers key, or from the command line. A remote one names its type.
Server URL: https://app.orla.finance/api/mcp/personal
Setup
A servers entry that names its type
The same object works in the workspace file, in your user configuration or on the command line.
The steps
- Per workspace
- .vscode/mcp.json, committed with the project, so everyone who opens it is offered the same server and signs in as themselves.
- Or for you
- Command palette, MCP: Open User Configuration.
- Or from a shell
- code --add-mcp with the same object on one line.
- Sign in
- Orla's consent page opens in the browser on the first call.
.vscode/mcp.json
{
"servers": {
"orla": {
"type": "http",
"url": "https:/ / app. orla. finance/ api/ mcp/ personal"
}
}
}The key is "servers", not "mcpServers". For a local bridge, drop the type and give "command": "npx", "args": ["-y", "orla-cli", "mcp"].
If the menus have moved, the VS Code MCP documentation is current for the client itself.
What to ask
Ask in the chat panel, next to the diff
Every figure comes from your own books, and is recomputed each time you ask.
- What does this repository's hosting cost a month?
- Which subscriptions renewed this week?
- What does the VAT report say for this quarter?
- Book the domain renewal to Software.
You tick which spaces the client 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.
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.
- 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.
See it on your own books
Thirty minutes: we connect an account, drop a real bill in, and close a month together.