b3n-knowhere 0.1.1

B3n Knowhere CLI and MCP server for the UI deployment platform

B3n Knowhere CLI

Terminal and MCP access for B3n Knowhere.

Default API: https://knowhere.b3n.in

Login

b3n-knowhere login --url https://knowhere.b3n.in

The default login starts GateKeeper device authorization for the knowhere-cli client, opens the verification URL when possible, and stores refreshable local credentials in ~/.b3n-knowhere/credentials.json.

For rollback or automation fallback, create an admin API token in the Knowhere web UI at System -> Admin API Tokens -> Create token, then run:

b3n-knowhere login --admin-token --url https://knowhere.b3n.in

Paste the token when prompted. The CLI stores it locally and sends it as Authorization: Bearer.

The old username/password OTP flow has been removed. Revoke CLI tokens from the web UI when they are no longer needed.

Common Commands

b3n-knowhere projects
b3n-knowhere project create b3n-inc-landing \
  --runtime ssr_container \
  --domain b3n.in \
  --repo benaiah-ke/b3n-inc-landing \
  --production-branch main
b3n-knowhere deployments --project b3n-inc-landing
b3n-knowhere workflow b3n-inc-landing
b3n-knowhere domains
b3n-knowhere readiness --project b3n-inc-landing

Set B3N_KNOWHERE_URL or pass --url for non-production instances. For automation, use B3N_KNOWHERE_TOKEN; generic KNOWHERE_* names are left to Payd-era tooling and are intentionally not read by this package.