Ekso.Cli 2.2.0

Ekso.Cli — ekso

Official command-line interface for the Ekso API. Wraps Ekso.Sdk so every command is a thin shell over the same SDK call you'd write yourself.

The CLI has two surfaces:

• Curated commands under top-level branches (ekso auth, ekso item, ekso board, ekso mcp) — friendly flags, opinionated UX
• Raw API under ekso api … — auto-generated wrapper for every endpoint in the SDK surface (200+ commands across 30 sub-branches). --data @body.json for the body, exit codes mapped from HTTP status.

Install

dotnet tool install -g Ekso.Cli

Quick start

# Sign in once
ekso auth login --tenant acme
# → Open https://acme.ekso.app/auth/device and enter code: ABCD-1234
# → Waiting for approval...
# → ✓ Authenticated to tenant acme

# Use it
ekso item list --tenant acme
ekso board list --tenant acme --format table

# The magic moment: connect Ekso as an MCP server in Claude Code
ekso mcp connect --for claude-code --tenant acme
# →   claude mcp add ekso --transport http https://acme.ekso.app/mcp/ \
# →     --header "Authorization: Bearer ekso_at_..."

Auth

Two modes:

Device flow (interactive — recommended for local use):

ekso auth login --tenant acme
ekso auth whoami --tenant acme
ekso auth logout --tenant acme

Tokens persist to ~/.config/ekso/credentials.json (Linux/macOS) or %APPDATA%\Ekso\credentials.json (Windows). Refresh tokens rotate transparently on expiry — no need to re-login until the refresh token itself expires (~30 days).

API key (non-interactive — for CI, agents, scripts):

EKSO_API_KEY=ek_live_... EKSO_TENANT=acme ekso item list

API keys are issued from the admin surface. Pass via --api-key or EKSO_API_KEY.

Output formats

Default is JSON (agent-friendly). Override with --format:

ekso board list --format json     # default — pretty JSON
ekso board list --format jsonl    # one JSON object per line, pipe-friendly
ekso board list --format yaml     # YAML
ekso board list --format table    # human-readable table

--quiet suppresses non-essential output. On create commands it prints just the new id:

NEW_ID=$(ekso item create --container-id container_x --quiet)
echo "Created $NEW_ID"

Global options

Available on every command:

Curated commands

Hand-polished for the most common flows. Friendly flags, opinionated defaults.

Raw API surface — ekso api …

The full Ekso REST surface is reachable via auto-generated commands under ekso api. Each [EksoSdk]-tagged operation in the openapi spec gets one command:

ekso api --help                   # ~30 sub-branches
ekso api annotation --help        # operations on /api/annotation/*
ekso api annotation list-supported --tenant acme
ekso api clock list --tenant acme
ekso api rule create --tenant acme --data @rule.json

Path parameters become positional args; query parameters become flags. Request bodies pass via --data <json> or --data @file.json. Response is rendered through the same --format flag the curated commands use.

Generated commands run on every dotnet build Ekso.Cli from tools/Ekso.CliGenerator — they stay in sync with the backend openapi spec automatically.

Exit codes

Per the standard CLI convention:

License

MIT.