CLI Reference

The Sloan CLI is a tool we created to facilitate the easy setup of Sloan 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 Sloan 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) sloan

Commands

init

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

Terminal

sloan 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

sloan 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 Sloan MCP for it.

Terminal

sloan setup [path] <tools> <--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

--<tools>

Setup Sloan MCP to already have access to Moose read tools – --moose-read-tools, --moose-write-tools, --remote-clickhouse-tools

config

Configure Sloan settings

config focus

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

Terminal

sloan config focus

config keys

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

Terminal

sloan 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

sloan 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