Nexra CLI

Install

The CLI needs Node.js 22 or later and has no other dependencies.

npm install -g https://usenexra.ai/downloads/nexra-cli-0.3.0.tgz
nexra --version

To verify the download first, compare it with the published checksum:

curl -fsSLO https://usenexra.ai/downloads/nexra-cli-0.3.0.tgz
curl -fsSL https://usenexra.ai/downloads/nexra-cli-0.3.0.tgz.sha256 | shasum -a 256 -c
npm install -g ./nexra-cli-0.3.0.tgz

Sign in

nexra auth login

Your session acts with your current role in each workspace. The CLI holds a one-hour access token and a refresh token, and renews the access token automatically while you use it:

The session (access and refresh tokens) is stored in credentials.json in the CLI's configuration directory, readable only by you (mode 0600). The directory is ~/.config/nexra on macOS and Linux, %APPDATA%\nexra on Windows, or NEXRA_CONFIG_DIR if you set it. Tokens are never printed, and secrets are never accepted as command-line flags.

In CI

Automation without a browser can set NEXRA_ACCESS_TOKEN from the CI secret store; it takes precedence over a stored session. To call MCP tools from CI, use nexra mcp token (below).

Choose a workspace and defaults

nexra context use --workspace <workspace-id> --environment sandbox
nexra context show
nexra context reset

--workspace on any command overrides the default for that command and is sent as X-Workspace-Id. Use --profile <name> (or NEXRA_PROFILE) to keep separate sign-ins and defaults, for example for two organisations.

Commands

API catalogue

These commands need no sign-in.

Connectors

These commands need no sign-in.

Nexra Connect

flows run generates an idempotency key unless you pass --idempotency-key. Re-running with the same key returns the original run instead of starting a new one. Production runs need an approved deployment.

SDKs

MCP

export NEXRA_MCP_CLIENT_ID=mcp_xxxxxxxxxxxx      # credential prefix
export NEXRA_MCP_CLIENT_SECRET=...               # from your secret store
export NEXRA_MCP_TOKEN=$(nexra mcp token)

nexra mcp token exchanges an MCP credential for a one-hour access token (see MCP authentication) and prints only the token.

Output

Every command accepts --output table (the default), json, yaml or ndjson. Tables are bold when your terminal supports it; use --no-color or NO_COLOR=1 for plain text. Fields named like tokens, secrets or passwords are always shown as [REDACTED].

nexra connect runs list --status failed --output json | jq '.[].id'

Diagnose problems

nexra doctor

doctor reports the CLI version, profile, API and console addresses, whether the API is reachable, where your session comes from, when it expires and who you are signed in as.

Environment variables

Everything the CLI does is also available in the console and through the platform API.

Connect a provider account across interfaces

See Connect through MCP, APIs, CLI and SDKs for account setup, exact operation selection, authentication, copyable examples, sandbox boundaries and approval troubleshooting.