Authentication

One Personal Access Token (PAT) covers all your projects. Get one from /app/settings/cli-tokens in the web console.

Login

loguro login                  # paste a pat_… when prompted

The PAT is saved to ~/.config/loguro/auth.json. The MCP server reads the same file, so logging in once with the CLI works for every IDE you connect MCP to.

Whoami / logout

loguro whoami                 # show current user / token info
loguro logout                 # remove the saved PAT

Environment variables (CI / one-shot)

export LOGURO_TOKEN=pat_xxx
export LOGURO_PROJECT=my-app
export LOGURO_BASE_URL=https://logu.ro   # optional override
VariablePurpose
LOGURO_TOKENActive PAT. Overrides the saved auth.json.
LOGURO_PROJECTProject slug to use when no .loguro link is found.
LOGURO_BASE_URLOverride the API host (self-hosted / staging).

LOGURO_TOKEN is the recommended way to authenticate in CI — no need to run loguro login on your runners.

Resolution order

When a command needs to know which project to query, the CLI resolves in this order:

  1. --app <name> flag (explicit per-command)
  2. .loguro in current dir or any ancestor (slug or app)
  3. Default app from config store
  4. LOGURO_PROJECT env / --project (with the active PAT)

The active PAT is LOGURO_TOKEN (env) or the saved auth.json (from loguro login).

// related

See also