Metadata-Version: 2.4
Name: b3n-knowhere
Version: 0.1.1
Summary: B3n Knowhere CLI and MCP server for the UI deployment platform
Author-email: B3n Inc <admin@b3n.in>
Requires-Python: >=3.12
Requires-Dist: httpx>=0.28.0
Requires-Dist: mcp>=1.0.0
Requires-Dist: rich>=13.0.0
Requires-Dist: typer>=0.15.0
Description-Content-Type: text/markdown

# B3n Knowhere CLI

Terminal and MCP access for B3n Knowhere.

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

## Login

```bash
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:

```bash
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

```bash
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.
