Skip to main content

​
Install

​
Mac, Linux

Use homebrew to install mocli:
On Linux with a headless machine, mocli login requires a browser for the initial login. After the first login, your session persists locally.

​
Windows

​
Login (optional)

Signing in to mogenius is optional — you only need it for the platform features (organizations, workspaces, operator-connected clusters, tunnels). Working against a local kubeconfig needs no login. To use platform features, authenticate once. Your browser opens automatically to complete the login:
Your session is stored locally, so you only need to log in once per machine.

​
Self-hosted instances

By default, mocli connects to the mogenius cloud at app.mogenius.com. If you run a self-hosted mogenius platform, point mocli at your own instance by editing its configuration file. The config file lives at: Replace the endpoints in the services block with the URLs of your self-hosted deployment:
All five endpoints refer to the same self-hosted instance. Ask your platform administrator for the exact hostnames if you are unsure — they follow the DNS scheme configured during installation.
mocli must be able to reach these endpoints over the network from the machine it runs on. In restricted environments where the platform is only reachable from inside a managed desktop or jump host (for example via a VDI or bastion), run mocli there rather than on your local machine.

​
API-key authentication

For automated pipelines — or locked-down environments where the browser callback used by mocli login is blocked — authenticate with an API key instead. It needs no local callback server:
Create the API key in your mogenius profile settings. The key is a single opaque token starting with mo_pat:. When MOGENIUS_API_KEY is set, mocli automatically uses API-key authentication.
CI/CD integration: set the MOGENIUS_API_KEY environment variable in your pipeline and mocli picks it up automatically — no interactive step required.