Skip to main content
Coral ships as a single local CLI. Once installed, the same binary is used for source management, SQL queries, and the MCP stdio server.
Coral publishes macOS, Linux, and x86_64 Windows artifacts. Windows support currently targets native Windows 10/11 on x86_64-pc-windows-msvc; ARM64 Windows is not released.

Install Coral

brew install withcoral/tap/coral
Once installed, run coral onboard to start the interactive wizard to complete the setup.

Upgrade

brew upgrade withcoral/tap/coral

Uninstall

brew uninstall withcoral/tap/coral

Skills

Coral publishes a set of agent skills that teach your coding agent how to use Coral effectively. Install them with:
npx skills add withcoral/skills
Available skills:
  • coral — teaches your agent the discovery-first MCP workflow for answering data questions through Coral, including how to use list_catalog, search_catalog, coral.tables, coral.table_functions, coral.columns, and coral.inputs.
  • coral-create-source-spec — guides your agent through authoring or repairing a custom source spec YAML for coral source add --file, or adapting it into a bundled source.
  • coral-review-source-spec — guides source manifest and source PR reviews for correctness, query ergonomics, documentation quality, and consistency with existing Coral sources.
Installable skill packages are published from github.com/withcoral/skills.

Local state

Coral stores local state in its platform-specific configuration directory. You can override that location with:
export CORAL_CONFIG_DIR=/path/to/coral-config
On Windows PowerShell:
$env:CORAL_CONFIG_DIR = "C:\path\to\coral-config"
On Windows, the default local state path is %APPDATA%\withcoral\coral\config. Important files include:
  • config.toml for installed-source metadata, non-secret variables, and runtime settings. See Configuration.
  • imported source specs under workspaces/<workspace>/sources/<source>/manifest.yaml
  • source secrets stored separately within the same local trust boundary
Bundled source specs are not copied into the config directory. Coral resolves them from the current binary when you validate or query a bundled source, so upgrades pick up newer bundled manifests without re-adding the source.