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.

The workspace file travels with the repository; the user file follows you between them.

Connecting VS Code

Per workspace.vscode/mcp.json, committed with the projectone file

Or for youCommand palette, MCP: Open User Configurationone file

Or from a shellcode --add-mcp with the same object on one lineone command

What you approve on Orla's pageWhich spaces this client reaches, and nothing else to fill in

The configuration

// .vscode/mcp.json: "servers", not "mcpServers" { "servers": { "orla": { "type": "http", "url": "https://app.orla.finance/api/mcp" } } }

For a local bridge instead, drop the type and give "command": "npx", "args": ["-y", "orla-cli", "mcp"].

If the menus have moved, the VS Code MCP documentation is the version that is current for the client itself.

The boundary

It reads and records. It does not pay.

An agent that pays is a different connection.

What it readsEverything you can read in the spaces you ticked, and nothing outside themyour rows

What it writesTransactions, categories, payees and notes, straight away rather than into a queueyour books

What it cannot doPay anyone. The payment tools are not in the list it is given, and are refused by namenever

What it costsNothing, and it takes none of the connected agent seats in your planfree plan too

How it endsAgents, then revoke. Every client connected this way stops at onceone click

Other clients

A second client joins the same connection, not another one.

The client is open source and reads what it is given: github.com/cheetah-trade/orla-cli.