Zed

A context server that happens to be your ledger.

Zed calls them context servers and keeps them in settings.json. One with no header of its own gets the consent flow.

Zed prompts for the sign in itself; nothing is pasted into the settings file.

Connecting Zed

One. Open settingsThe command palette, then zed: open settingsone file

Two. Add the serverUnder context_servers, with the address and nothing elseone entry

Three. Sign inZed opens Orla's consent page on the first callonce

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

The configuration

// settings.json { "context_servers": { "orla": { "url": "https://app.orla.finance/api/mcp" } } }

A local bridge is the same key with "command": "npx", "args": ["-y", "orla-cli", "mcp"], after npx orla-cli login.

If the menus have moved, Zed's 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.

A custom connector in Settings, nothing to install.

One command in the terminal, then /mcp to sign in.

One entry in mcp.json, globally or in the repository.

One entry under servers, or one code --add-mcp line.

One entry with serverUrl in the Codeium config.

The CLI itself, and a stdio bridge for clients without HTTP.

Start

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