Skip to main content
The stoffel command line tool can currently be run on Linux and macOS, and on Windows through WSL2. Use this page to install the stoffel CLI, verify that the command is on your path, and create a first project. The CLI is the entry point for creating projects, checking source, building bytecode, and running local MPC development workflows.
Using an AI coding agent? Start with the agent install prompt. It installs the stoffel CLI, adds Stoffel skills, connects docs access, and verifies the setup before the agent changes a Stoffel project.

Requirements

Required for the CLI:
  • A Unix-like shell: Linux, macOS, or Windows with WSL2
  • curl or wget
  • 4 GB RAM minimum; 8 GB recommended
Required only for source builds or repository examples: Required only for AI-agent setup:
  • Node.js for npx-based skill and MCP setup commands
Install the stoffel CLI with the official installer:
The installer places stoffel in ~/.local/bin by default. If your shell cannot find it, add that directory to your PATH:
Verify the installation:
You should see commands for the normal project loop:
You can also check the installed version:

Verify with a new project

Create and build a project:
Expected output includes:
This verifies that the stoffel command line tool can create, check, and build a Stoffel app. The Quick Start continues from here into local MPC execution and the Rust SDK wrapper.

Install Stoffel with an AI coding agent

Paste this prompt into your AI coding agent if you want it to install Stoffel, connect the docs context, and prove the setup works:

Manual agent-context setup

If you do not want your agent to install the CLI and skills, run the core setup yourself:
List the available skills without installing:
Connect the live Stoffel docs through Mintlify’s hosted MCP server when your agent supports MCP:
After setup, continue to Quick Start or choose a playbook from Developer Skills.

Pin a CLI version

Pin a version when you want every developer or CI job to use the same CLI:
For example, use --version 0.1.0 when a project or CI job intentionally standardizes on that CLI version. Install into a different directory when your environment manages tool paths explicitly:

Build the CLI from source

Build from source when you need repository examples, workspace development, or local CLI changes.
The debug CLI path is:
For a faster CLI binary, build in release mode:
The release CLI path is:
Use the prebuilt CLI for the normal app development loop. Build the CLI from source only when you need local CLI changes or repository examples.

Troubleshooting

stoffel is not found

Add the CLI install directory to your path:
If you installed into another directory, add that directory instead.

cargo is not found

Install Rust and load Cargo’s shell environment:

Source builds take a while

The CLI source build compiles several workspace crates. The first Cargo build may take several minutes while dependencies are fetched and compiled.

Native Windows issues

Use WSL2 unless you are specifically testing native Windows support.

Next steps