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.

Server URL: https://app.orla.finance/api/mcp/personal

Setup

A context server with nothing but its address

A few lines of JSON, and Zed does the sign-in in your browser.

Consent page, in Claude

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.

Open settingsThe command palette, then zed: open settings.
Add the serverUnder context_servers, with the address and nothing else. An entry with a header of its own does not get the consent flow, so leave headers out.
Sign inZed opens Orla's consent page on the first call.

settings.json

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

After npx orla-cli login, a local bridge is the same key with "command": "npx", "args": ["-y", "orla-cli", "mcp"] and no url at all.

If the menus have moved, Zed's MCP documentation is current for the client itself.

What to ask

Every figure comes from your own books, and is recomputed each time you ask.

The boundary

An agent that pays is a different connection, with its own wallet and its own limits.

What it cannot doPay anyone. The payment tools are not in the list it is given, and are refused by name if asked.
What it costsNothing, and it takes none of the agent seats in your plan. Reading is unmetered; what it records comes out of your plan's monthly allowance of agent writes, and the free plan has a small one.

Other clients

On your own books: one position, one rule, and the first bill waiting for your button.