@allocator-one/infraone
The infraone CLI: what you can do in Infra One,
from a terminal or a script, with exactly your app rights. It starts with your
data rooms.
Install
With npm (Node 20 or later):
npm i -g @allocator-one/infraone
infraone --help
Or run it without installing:
npx -y @allocator-one/infraone --help
With Homebrew, on macOS or Linux:
brew install allocator-one/tap/infraone
As a single binary for macOS or Linux, with no Node needed. The script
downloads the binary for your machine, checks its SHA-256 checksum, and installs
it in ~/.local/bin (set INFRAONE_INSTALL_DIR to choose another folder):
curl -fsSL https://github.com/allocator-one/homebrew-tap/releases/latest/download/install.sh | sh
Sign in
infraone login
infraone whoami
infraone login opens Infra One in your browser. You choose the organization
there, and the CLI stores a credential for it that lasts 30 days. Every command
then acts as you, in that organization, with the rights you have in the app.
Signing in covers other organizations, scripts and signing out,
and personal tokens are the credential to give a script.
Use it
infraone datarooms spaces list
infraone datarooms spaces list --type personal --json
The commands come from the Infra One API, so infraone --help always lists
what the server offers, including commands added after this release. Every
command takes --json. Lists page with --limit and --cursor, and --all
follows every page. The command reference lists the commands
this release knows about, and the app pages show each app's
commands and MCP tools, the scopes they need, the ones that ask you to confirm,
and what stays in the app. Both are generated at release from the API's spec
and ship in the npm package.
Deleting, revoking access, sharing outside Infra One and emailing people ask you to confirm first; confirmations explains how.
AI clients
Connect Claude, or any MCP client, to the hosted Infra One MCP at
https://mcp.infra.one/mcp. Infra One MCP shows how.
Exit codes
| Code | Meaning |
|---|---|
| 0 | Done |
| 1 | The API refused or failed the request |
| 2 | The command line was wrong, or a confirmation was missing; nothing was sent |
| 3 | The API could not be reached |
stdout carries data only; messages go to stderr.