Installation
Download
Download the latest release from the GitHub releases page.
Each archive contains:
| File | Purpose |
|---|---|
luminarys | Host runtime — loads and executes skills |
lmsk | Skill toolchain — code generation, signing, inspection (lmsk info) |
config/ | Ready-to-use configuration with a demo echo skill |
skills/ | Pre-built echo skill package |
Supported platforms
| OS | Architecture | Archive |
|---|---|---|
| Linux | x86_64 | luminarys-*-linux-amd64.tar.gz |
| Linux | ARM64 | luminarys-*-linux-arm64.tar.gz |
| Linux | RISC-V 64 | luminarys-*-linux-riscv64.tar.gz |
| Linux | MIPS | luminarys-*-linux-mips.tar.gz |
| Linux | MIPS64 | luminarys-*-linux-mips64.tar.gz |
| macOS | x86_64 | luminarys-*-darwin-amd64.tar.gz |
| macOS | Apple Silicon | luminarys-*-darwin-arm64.tar.gz |
| Windows | x86_64 | luminarys-*-windows-amd64.zip |
Quick start
Linux / macOS:
tar xzf luminarys-*-linux-amd64.tar.gz
./luminarys
macOS (Apple Silicon):
tar xzf luminarys-*-darwin-arm64.tar.gz
./luminarys
Windows:
Expand-Archive luminarys-*-windows-amd64.zip -DestinationPath .
.\luminarys.exe
The server starts on http://localhost:8080 with a demo echo skill. Connect any MCP client to http://localhost:8080/mcp.
Add to PATH (optional)
# Linux / macOS
chmod +x luminarys lmsk
sudo mv luminarys lmsk /usr/local/bin/
# Verify
luminarys --help
lmsk --help
On Windows, place the .exe files in a directory on your PATH.
Validate configuration
After setting up your config file and skill manifests, validate before starting:
luminarys -validate -config config/host.yaml
This checks YAML syntax, manifest validity, skill binary paths, and cluster configuration. If everything is correct:
config OK
Running the host
HTTP mode (default — for MCP clients over network):
luminarys -config config/host.yaml
stdio mode (for Claude Desktop, Cursor, or MCP Inspector):
luminarys -config config/host.yaml -stdio
Docker
For containerized deployments, see the MCP Demo Cluster — a ready-to-run Docker Compose setup with a two-node cluster.
Skill development requirements
To build your own skills, you need lmsk and a signing key:
lmsk genkey
Then install the toolchain for your language:
AssemblyScript
- Node.js 22+
npm install --save-dev assemblyscript @luminarys/sdk-as- Build:
npx asc assembly/lib.ts --target release
Go
- Go 1.25+
- Build:
GOOS=wasip1 GOARCH=wasm go build -buildmode=c-shared -o skill.wasm .
Rust
- Rust with
wasm32-wasip1target:rustup target add wasm32-wasip1 - Build:
cargo build --target wasm32-wasip1 --release - Some skills with native C dependencies (e.g. tree-sitter) require WASI SDK
Inspect skill packages
Use lmsk info to inspect any .skill package — view skill ID, version, methods, and verify the signature:
lmsk info my-skill.skill
See Skill Examples for complete working examples in all three languages.