# Command line

Every command of strazad, strazactl and straza with its flags and operands.


Straza ships three binaries, and each has its own command tree here. `strazad` is the server: it serves the API, the console, the MCP gateway and the SCIM endpoint, and an operator runs one per deployment. The operator's command line is `strazactl`. It runs on an admin API token, which a person mints in the console and sets in `STRAZA_API_TOKEN`, and it does the admin API's work, from applying a PolicySet to verifying the audit chain, in a form a script can call. An admin API token is not a person, so a person signs in, decides requests and publishes drafts in the console, and decides on the self-service page or on the phone as well. On the agent's machine runs `straza`, the client: it enrolls the device, installs the hooks into a harness, answers each hook call with a decision, fronts MCP for the harness and uploads the audit spool.

The pages under each tree are generated from the binary's own command tree by `make docs-gen`, one page per command with its synopsis, flags and operands, and the commit gate refuses a tree that differs from a fresh run, so a page here is the help text of the release it documents.

- [strazad](https://docs.straza.ai/reference/cli/strazad/index.md), the server
- [strazactl](https://docs.straza.ai/reference/cli/strazactl/index.md), the operator's command line
- [straza](https://docs.straza.ai/reference/cli/straza/index.md), the agent-side client


- [strazad](https://docs.straza.ai/reference/cli/strazad/index.md): Straza platform server
- [strazactl](https://docs.straza.ai/reference/cli/strazactl/index.md): Straza admin CLI
- [straza](https://docs.straza.ai/reference/cli/straza/index.md): Straza client: enroll this machine, wire the hooks and decide each tool call
