neetokb setup commands add NeetoKB instructions for your assistant, while --toon keeps command output compact for it to read.
Set up your assistant
Run the subcommand for the tool you use:CLI or MCP?
Both surfaces let an assistant work with NeetoKB. The CLI runs on your machine and reuses your browser sign-in, so it suits coding assistants that already have a terminal. The MCP server is hosted by NeetoKB and suits assistants without shell access; it connects with an OAuth grant scoped to you, or an API key scoped to the whole workspace.Tips for agent workflows
- Authenticate once with
neetokb login; the assistant reuses the stored credentials. - When several workspaces are signed in, the assistant must pass
--subdomain <name>on each command. - Run
neetokb doctorfirst to confirm the assistant is authenticated and connected.