Aurora

Reference

CLI reference

CLI Reference

The Aurora CLI is a tool we created to facilitate the easy setup of Aurora MCPs. It is not required, and we hope that LLM clients will eventually support all these features natively, so that we can remove the CLI.

It allows you to:

  • set up your Aurora MCP with a variety of clients
  • manage multiple projects
  • manage multiple toolsets
  • update multiple MCP configurations at once

Install CLI

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

Commands

init

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

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

Common Arguments & Flags

<name>
Required
Name of your application (this will be the <project-name>). – e.g. my-app
--mcp <host>
Choice of which MCP host to use. – default: cursor-project, other options: cursor-global, claude-desktop, windsurf-global
--location <location>
Location of your app or service. The default is the name of the project. – e.g. my-app
--no-fail-already-exists
By default, the init command fails if `location` exists, to prevent accidental reruns. This flag disables the check.

For New Projects

<template-name>
Required
The template you are basing your application on. – typescript-empty, typescript, ads-b

For Projects from a Pre-existing ClickHouse Database

--from-remote <connection-string>
Required
The connection string to your ClickHouse database. – e.g. clickhouse://user:pass@host:port/db
--language <language>
Required
The language of your application. – typescript, python

connect

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

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

Arguments / Flags

--connection-string <connection-string>
Required
The connection string to your ClickHouse database. – e.g. clickhouse://user:pass@host:port/db
--mcp <host>
Choice of which MCP host to use. – default: cursor-project, other options: cursor-global, claude-desktop, windsurf-global

setup

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

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

Arguments / Flags

[path]
Path to the Moose project. – defaults to current directory
--mcp <host>
Choice of which MCP host to use. If flag is not provided, the default is `cursor-project`. – default: cursor-project, other options: claude-desktop, cursor-global, cursor-project, windsurf-global

config

Configure Aurora settings

config focus

Aurora allows you to configure project level MCPs (e.g. for Cursor) and global MCPs (e.g. for Claude Desktop). To configure which Aurora project is being used with the Global MCPS, use aurora config focus.

Terminal
aurora config focus

config keys

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

Terminal
aurora config keys <KEY>

Arguments / Flags

<KEY>
Required
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 tools

Toggles availability of experimental MCP tools. See Tools Reference.

Terminal
aurora config tools

Note: if you select remote-clickhouse, you will need to add your ClickHouse Cloud / Boreal credentials to mcp.json.

AI powered OLAP templates

Tools reference