Orla MCP server

orla

Your Orla books from a terminal, and a stdio bridge for MCP clients that cannot speak HTTP.

npx orla-cli login
npx orla-cli tx list --from 2026-08-01
npx orla-cli export --from 2026-01-01 > books.csv

No dependencies, no build step, no native module to compile. Node 22 or newer.

The package is orla-cli and the command it installs is orla. They differ because npm refused the bare name as too close to packages that already exist (ora, ol, rlp, url), and renaming the command would have been the worse half of that trade: npm i -g orla-cli still gives you orla tx list.

What it is

A thin client over the same MCP endpoint Claude connects to. Every command is a tool call, so the CLI cannot do anything a personal connection cannot do, and nothing here has its own idea of authorization. orla login walks the ordinary OAuth code flow with S256 PKCE: the browser lands on Orla's own consent page, where you tick the spaces this machine may reach.

It does not move money. A personal connection reads and records. Payments, transfers and card details belong to an agent connected for that purpose, with its own limits, set in the app under Agents. The tools that move money are not in the list this connection is given, and are refused at the endpoint if asked for by name.

That is not a matter of trust in this client: orla login asks for the personal address, where those tools do not exist, so the promise survives whatever gets ticked on the consent page. orla login --agent asks for the other address, the one where a bot with its own budget can be minted. A session remembers which door issued its tokens and keeps using it, so an existing connection is not re-pointed by an update.

Commands

--space on anything space-scoped, --json for machine-readable output.

For a program, or an agent

With --json, every command answers with one envelope on stdout:

{ "ok": true, "data": ... }
{ "ok": false, "error": { "code": "cli.not_connected", "message": "not connected: run `orla login` first" } }

Read ok, then branch on error.code. Codes that begin cli. are the CLI's own; any other code is Orla's, passed through unchanged, the same name the REST API and the MCP endpoint use. The exit status says which kind of failure it was, so a shell script can branch without parsing anything:

The skill that teaches an agent all of this, including where paying stops, is skills/orla/SKILL.md. It ships in the package and at orla.finance/skill.md, and it is one of the five skills the Claude Code plugin below installs. Into any other agent:

Shortened. The full README is on GitHub.