Installation
sqry ships pre-built binaries for all major platforms and is also available via crates.io and from source. This page covers all installation paths, shell completions, and how to build the MCP and LSP servers.
macOS and Linux (recommended)
The install script downloads sqry, sqry-mcp, sqry-lsp, and sqryd into ~/.local/bin (override with --install-dir):
curl -fsSL https://raw.githubusercontent.com/verivus-oss/sqry/main/scripts/install.sh | bash -s -- --component all
Add --verify-signatures to enforce Cosign bundle verification (requires cosign). Published binaries are available for Linux x86_64/arm64, Windows x86_64, and macOS Apple Silicon/Intel.
Windows (recommended)
The PowerShell installer places sqry.exe, sqry-mcp.exe, sqry-lsp.exe, sqryd.exe, and the bundled MinGW runtime DLLs (libstdc++-6.dll, libgcc_s_seh-1.dll, libwinpthread-1.dll) into %LOCALAPPDATA%\Programs\sqry\bin, then adds that directory to the user PATH:
irm https://raw.githubusercontent.com/verivus-oss/sqry/main/scripts/install.ps1 | iex
Review-first variant with signature verification:
Invoke-WebRequest https://raw.githubusercontent.com/verivus-oss/sqry/main/scripts/install.ps1 -OutFile install.ps1
Get-Content .\install.ps1
.\install.ps1 -VerifySignatures
Pin a specific release:
.\install.ps1 -Version v16.0.6 -VerifySignatures
Windows runtime dependencies
The Windows builds target x86_64-pc-windows-gnu and dynamically link against three MinGW-w64 runtime libraries: libstdc++-6.dll, libgcc_s_seh-1.dll, and libwinpthread-1.dll. The release ZIP bundles these alongside the executables, the installer copies them into the install directory, and each release is smoke-tested end-to-end under Wine so the ZIP is verified to launch before publishing. You do not need to install MSYS2 or MinGW separately.
Manual fallback
Download sqry-windows-x86_64.zip from the releases page and extract the entire archive (not just the .exe files) into a single directory on PATH. The executables and bundled .dll files must sit side by side; Windows resolves them from the executable directory first, and removing the DLLs will cause sqry.exe to fail with libstdc++-6.dll was not found on launch.
If you are working around an older, DLL-less Windows release and cannot upgrade, place matching libstdc++-6.dll, libgcc_s_seh-1.dll, and libwinpthread-1.dll from a trusted MinGW-w64 toolchain (for example C:\msys64\mingw64\bin after pacman -S mingw-w64-x86_64-gcc) next to the executables. Do not source these DLLs from unvetted download sites — pull them only from an upstream toolchain you control. Upgrading to the current release is the supported path.
Package Managers
Release packaging configs are generated from signed release checksums and included in release assets:
| Manager | Asset |
|---|---|
| Homebrew | homebrew-sqry.rb |
| Scoop | scoop-sqry.json |
| Winget | winget-*.yaml |
| AUR | aur-PKGBUILD |
| Nix | nix-*.nix |
| Snap | snap-snapcraft.yaml |
Primary install methods provide sqry, sqry-mcp, sqry-lsp, and sqryd. Raw binaries and .bundle files are advanced/manual verification assets.
From crates.io
Install the CLI from source via cargo:
cargo install sqry-cli
The sqry binary is placed in ~/.cargo/bin/. Make sure this directory is in your PATH (rustup adds it automatically on most systems). This cargo command installs the CLI only; use the platform installers above or the source build below when you also need sqry-mcp, sqry-lsp, and sqryd.
The standard language set is compiled in by default, including IaC languages (Terraform, Puppet, Pulumi). High-cost plugins such as JSON and ServiceNow XML can be enabled explicitly when needed.
Requirements: Rust 1.94+ (Edition 2024). About 20 GB disk for a full build (37 tree-sitter grammars are compiled from source).
From Source
Clone the repository and install all four binaries:
git clone https://github.com/verivus-oss/sqry.git
cd sqry
cargo install --path sqry-cli
cargo install --path sqry-mcp
cargo install --path sqry-lsp
cargo install --path sqry-daemon
To build release binaries without installing system-wide:
cargo build --release --package sqry-cli
cargo build --release --package sqry-mcp
cargo build --release --package sqry-lsp
cargo build --release --package sqry-daemon
The compiled binaries are placed at target/release/sqry, target/release/sqry-mcp, target/release/sqry-lsp, and target/release/sqryd. Copy them to any directory in your PATH:
cp target/release/sqry target/release/sqry-mcp target/release/sqry-lsp target/release/sqryd ~/.local/bin/
Verify
Confirm the installation succeeded:
sqry --version
You should see output like sqry 16.0.6 (version numbers vary). To list supported languages and their file extensions:
sqry --list-languages
Shell Completions
sqry can generate completion scripts for Bash, Zsh, Fish, and PowerShell.
Bash:
sqry completions bash >> ~/.bashrc
# Or for system-wide completions:
sqry completions bash > /etc/bash_completion.d/sqry
Zsh:
sqry completions zsh > ~/.zfunc/_sqry
# Ensure ~/.zfunc is in your fpath in ~/.zshrc:
# fpath=(~/.zfunc $fpath)
# autoload -Uz compinit && compinit
Fish:
sqry completions fish > ~/.config/fish/completions/sqry.fish
PowerShell:
sqry completions powershell > sqry.ps1
# Source the file from your PowerShell profile
After adding completions, start a new shell session (or source the relevant file) for them to take effect.
Completions cover all subcommands (query, search, graph, index, unused, cycles, diff, explain, similar, impact, batch, shell, workspace, cache, config, mcp, lsp, etc.), their flags, and valid values for enum flags like --kind, --lang, --format, and --scope. In shells that support it (Zsh, Fish), descriptions are shown alongside each completion candidate.
MCP Binary
sqry includes a native MCP (Model Context Protocol) server that exposes 36 JSON-RPC tools for AI assistants such as Claude, Codex, Gemini, Cursor, and Windsurf.
If you used the platform install scripts above, sqry-mcp is already installed. To build it separately from source:
git clone https://github.com/verivus-oss/sqry.git
cd sqry
cargo build --release --package sqry-mcp
The binary is placed at target/release/sqry-mcp. See the MCP Integration page for assistant-specific configuration.
LSP Binary
sqry ships an LSP server supporting hover, definition, references, call hierarchy, document/workspace symbols, code actions, and custom sqry/* methods. It works with VS Code, Neovim, Helix, and any LSP 3.17 client. Socket mode is available for shared instances.
If you used the platform install scripts above, sqry-lsp is already installed. To build it separately from source:
git clone https://github.com/verivus-oss/sqry.git
cd sqry
cargo build --release --package sqry-lsp
The binary is placed at target/release/sqry-lsp. See the LSP Integration page for editor configuration.
Daemon Binary
sqryd is sqry’s background process. It keeps one or more workspace graphs loaded in memory so that CLI, LSP, and MCP queries are served from a warm index. Use it for long sessions, large repositories, or when sharing one graph across an editor (LSP), an AI assistant (MCP), and ad-hoc CLI queries.
If you used the platform install scripts above, sqryd is already installed alongside the other binaries. To build it separately from source:
git clone https://github.com/verivus-oss/sqry.git
cd sqry
cargo build --release --package sqry-daemon
The binary is placed at target/release/sqryd. Start it with sqry daemon start (or sqryd start --detach) and connect MCP/LSP shims via sqry-mcp --daemon and sqry lsp --daemon. See the Daemon (sqryd) page for the CLI surface, daemon.toml schema, environment variables, IPC transport details, and service-installation snippets for systemd, launchd, and Windows.