Automators CLI

Use one authenticated shell and MCP connection for Automators applications. Operator is the first application module; additional applications can join the same command boundary without introducing another global CLI.

Create a Quick Session in Operator, then run its one-time command:

npx -y @automators/[email protected] operator connect opx_...

The real four-hour credential is stored locally with owner-only permissions. The one-time code expires after two minutes and cannot be reused.

npx -y @automators/[email protected] operator status
npx -y @automators/[email protected] operator tools
npx -y @automators/[email protected] operator call list_engineering_outcomes --input '{"limit":10}'
npx -y @automators/[email protected] operator logout

The package can also be installed globally to provide the automators command. For MCP clients, automators operator mcp is a line-oriented stdio proxy to Operator's existing MCP endpoint. It reloads the stored credential for every request, so renewing a Quick Session does not require changing MCP configuration.

The CLI stores application credentials below the shared AUTOMATORS_CONFIG_DIR, with the Operator session isolated as sessions/operator.json. OPERATOR_TOKEN and OPERATOR_URL remain available for disposable environments, and OPERATOR_CONFIG_DIR remains supported for compatibility. An environment token takes precedence over the stored session.

The current Quick Session is resource-scoped to Operator. Future application modules should obtain audience-scoped credentials through Auth rather than make one unrestricted bearer token valid across every service. A top-level login and federated automators mcp command remain reserved until that Auth and gateway boundary exists.