CLI Reference

Install CLI

bash -i <(curl -fsSL https://fiveonefour.com/install.sh) aurora

Commands

init

Creates a data engineering project with Moose, with Aurora MCP preconfigured.

aurora init <project-name> <template-name> <--mcp <host>> <--location <location>> 

• <name>: name of your application

• --mcp <host>: Choice of which MCP host to [default: cursor-project] [possible values: claude-desktop, cursor-global, cursor-project, windsurf-global]

• --location <location>: Location of your app or service. The default is the name of the project.

• --no-fail-already-exists: By default, the init command fails if location exists, to prevent accidental reruns. This flag disables the check.

• If creating a new project:

  • <template-name>: the template you are basing your application on. Choose from an empty project (e.g. typescript-empty, a default project typescript or a pre-built project ads-b).
  • --from-remote <connection-string>: If you are creating a project from a pre-existing Clickhouse database, use this flag. Do not use a template.

• If creating a project from a pre-existing Clickhouse database:

  • --from-remote <connection-string>: The connection string to your Clickhouse database.
  • --language <language>: The language of your application. [possible values] typescript or python].

connect

Connects to an existing data source. Currently only clickhouse is supported.

aurora connect clickhouse <--connection-string <connection-string>> <--mcp <claude-desktop>>

• --connection-string <connection-string>: The connection string to your Clickhouse database.
• --mcp <host>: Choice of which MCP host to [default: cursor-project] [possible values: claude-desktop, cursor-global, cursor-project, windsurf-global]

setup

Takes an existing data engineering project build with Moose and configures Aurora MCP for it.

aurora setup [path] <--mcp <host>>

• Path to the Moose project (defaults to current directory)
• -mcp <host>: Choice of which MCP host to [default: cursor-project] [possible values: claude-desktop, cursor-global, cursor-project, windsurf-global]

config

Configure Aurora settings

config focus

List Aurora configured projects, allows selection of project globally configured hosts are “focused” on. No more than one Moose Project may be run at a time.

aurora config focus

config keys

Updates all MCP files for projects listed in ~/.aurora/aurora-config.toml to use updated API key.

aurora config keys <KEY>

• <KEY>: Your Anthropic API key. If you don’t have an Anthropic API key, see the Anthropic initial setup guide: https://docs.anthropic.com/en/docs/initial-setup

config models

[Coming Soon]. Allows you to configure which models Aurora agents use.

config tools

Toggles availability of experimental MCP tools. See Tools documentation for which tools are in standard and which are added in the experimental sets.

aurora config tools [EXPERIMENTAL_PREFERENCE]

• [EXPERIMENTAL_PREFERENCE]: Preference for experimental tools.

Note, if you select boreal-experimental, you will need to add your ClickHouse Cloud / Boreal credentials to mcp.json.

login

[Coming soon]. Allows you to log in to Aurora with your Boreal account. Will provide secure authentication and LLM provision.

aurora login