Initializing Operalta...

Operalta

CLI Quickstart

Install the Operalta CLI, log in, and choose terminal or MCP mode

Audience
Developer
Truth
Mixed sources
Surface
CLI
Status
Active

Related documentation: Developer documentation

Install Operalta, log in, and run it from the terminal or as an MCP server.

Operalta CLI in a developer workflow

How it fits

How the CLI reaches Operalta

The CLI is a local entry point: authenticate, choose a context, run a command, and inspect the result.

  1. Install

    CLI

    Put the command and its local MCP server on the machine where you work.

    • operalta
    • MCP
    • Terminal
    Open CLI
  2. authenticates
    Sign in

    Identity

    Use the browser OAuth flow or an explicitly configured key.

    • Login
    • OAuth
    • API key
    Open Identity
  3. selects
    Choose

    Context

    Pin a company, network, or local working directory when the command needs one.

    • Company
    • Network
    • Local files
    Open Context
  4. produces
    Run

    Result

    The command returns business data, a run, a file, or a diagnosis you can act on.

    • Report
    • Agent run
    • Dataroom
    Open Result

Install

  • Requires Node 18+. The installer drops operalta into ~/.local/bin.
  • This installs the operalta binary itself — a separate, later step registers it with an editor. See MCP setup for operalta install --target claudecode.
curl -fsSL https://www.operalta.ai/install.sh | sh
source ~/.zshrc
operalta --version

Authenticate

  • operalta login — browser OAuth flow.
  • operalta status — confirm the session.
  • OPERALTA_API_KEY=op_... — bypass the login flow entirely.
  • Company data commands (reports, rooms, lists/matrices) need a company-scoped key with the matching read scope (reports:read, rooms:read, lists:read). Activate them under Settings → Developer → API Keys (the "MCP Read" pack covers all three).
  • No-company users can create personal keys from Personal Settings → Developer and run network-scoped workflows with OPERALTA_NETWORK_ID.
  • operalta rooms currently works with company Rooms only. Setting OPERALTA_NETWORK_ID does not open Community Rooms or their artifacts.

Next

  • Commands — full reference.
  • Local models — run the CLI model loop without Anthropic.
  • MCP setup — Claude Code, Cursor, Windsurf.
  • REST API — company context, metrics, artifacts, rooms, and agent runs.
  • Config — env vars, files, modes.
  • Data room — local due diligence flow.
  • API keys — create one for the CLI.