kaiten-cli (ViktorOgnev)
kaiten-cli
A Python CLI for Kaiten with an agent command registry, shell completion and three bonus skills
High risk
We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.
Why this level
- The kaiten-cli-mutations skill performs write operations on Kaiten cards and data
- The CLI runs under the user credentials set in its configuration
Install
Manual install
uv tool install git+https://github.com/ViktorOgnev/kaiten-cli.gitThe recommended method. Alternative: pipx install git+https://github.com/ViktorOgnev/kaiten-cli.git
This is third-party code. Review the repository files before installing.
What it does
The CLI lets you work with Kaiten from the terminal using the same commands a person, a script or an LLM agent can run. The source of truth for commands is the local src/kaiten_cli/registry, and the CLI has built-in agent-help and search-tools commands specifically for agents to find the right command by meaning. It installs via uv tool or pipx straight from Git, and supports Bash and Zsh completion via kaiten completion install with a --dry-run mode to preview changes before touching files. It runs standalone and does not depend on the same author's MCP server of the same domain at runtime, though it shares its domain layer. It ships three bonus skills: kaiten-cli-heavy-data, kaiten-cli-metrics and kaiten-cli-mutations.
Who it is for. For Kaiten teams who want one command-line interface shared by people, scripts and an agent alike.
Good fit when
- You need a Kaiten CLI that an agent can learn through the built-in agent-help command
- You need to find the right command by task meaning rather than memorizing exact names
- You want ready skills for heavy data, metrics and mutations in Kaiten
Not a fit when
- You need an MCP server, not a CLI: see the same author's kaiten-mcp
- You do not want to install a Python tool via uv or pipx
- You need direct Claude Code integration through the MCP protocol
Example request
Find the kaiten-cli command for searching board cards and list the open onesLimitations
It installs only from Git; the README does not mention a separate PyPI package. Completion needs Bash 4.4 or newer, and macOS's system Bash can be older, requiring you to specify the startup file manually. The CLI does not proxy commands to MCP and runs independently of it.
How to disable. Remove the tool with uv tool uninstall kaiten-cli or pipx uninstall kaiten-cli, and delete the marked completion block from ~/.bashrc or ~/.zshrc.
Security check
- The kaiten-cli-mutations skill performs write operations on Kaiten cards and data
- The CLI runs under the user credentials set in its configuration
README in short
The Russian README details install via uv tool, pipx or a venv straight from Git, troubleshooting PATH issues on macOS, Linux and Windows, and setting up Bash and Zsh completion with --dry-run and completion status modes. It stresses that the command registry in src/kaiten_cli/registry is the source of truth and that the CLI does not proxy calls to MCP.
FAQ
How is this different from a plain CLI?
It has built-in agent-help and search-tools commands specifically so an LLM agent can find the right command by meaning, not exact name.
Do I need a separate MCP server?
No, the CLI runs fully standalone and does not depend on kaiten-mcp at runtime, though it shares its domain layer.
Related
A self-hosted knowledge base with block-level references and a built-in MCP server for connecting AI agents to your notes
A CLI for every Google Workspace API with JSON output and agent skills: Drive, Gmail, Calendar, Sheets and more
Local search over Markdown notes, docs and meeting transcripts: keywords, semantic search and reranking, with an MCP server
A task manager for AI-driven development: breaks a PRD into dependent tasks and guides the agent through them via MCP or CLI