# A context server that happens to be your ledger

URL: https://www.orla.finance/en/mcp-zed
Markdown twin of that page. Append `.md` to any Orla page URL to get one.

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

#### A context server with nothing but its address

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

- Open settings: The command palette, then zed: open settings.
- Add the server: Under 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 in: Zed opens Orla's consent page on the first call.

```
{
  "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.

#### Ask from the assistant panel

- What is in each account right now?
- What did I pay for tooling last month?
- List the reports you can run on this space.
- Book the 29 USD font licence to Software.

#### It reads and records. It does not pay

- 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. 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.