Installation
Quiver is a single binary, quiver.
Requirements: git on your PATH. Quiver keeps your skills in git repositories and clones sources with it.
Platforms: macOS, Linux and Windows, on x86-64 (amd64) and ARM64. See Supported platforms.
Install
Section titled “Install”curl -fsSL https://raw.githubusercontent.com/kheif/quiver/main/install.sh | shThe script downloads the latest release for your system, checks it against the release's checksums.txt, and installs quiver into ~/.local/bin. If that folder is not on your PATH, it prints the line to add to your shell profile.
| Variable | Effect |
|---|---|
QUIVER_VERSION=v1.2.0 | Install a given release instead of the latest. |
QUIVER_INSTALL_DIR=/path | Install into another folder. |
curl -fsSL https://raw.githubusercontent.com/kheif/quiver/main/install.sh | QUIVER_VERSION=v1.2.0 shIn PowerShell:
irm https://raw.githubusercontent.com/kheif/quiver/main/install.ps1 | iexThe script does the same steps: it installs quiver.exe into %LOCALAPPDATA%\Programs\quiver and adds that folder to your user PATH, without admin rights. Open a new terminal afterwards.
QUIVER_VERSION and QUIVER_INSTALL_DIR work the same way. Set them before the line:
$env:QUIVER_VERSION = 'v1.2.0'irm https://raw.githubusercontent.com/kheif/quiver/main/install.ps1 | iexnpm install -g @kheif/quivernpm installs the binary for your platform from a platform package. No install script runs. Node.js 18 or later is needed.
go install github.com/kheif/quiver/cmd/quiver@latestThis builds Quiver with your Go toolchain into $(go env GOPATH)/bin. It needs the Go version in go.mod or later.
Download the archive for your system from the releases page: quiver_<os>_<arch>.tar.gz, or .zip for Windows. Check it against checksums.txt, unpack it, and put quiver in a folder on your PATH.
To build from a clone instead:
git clone https://github.com/kheif/quivercd quivermake build # writes bin/quiverCheck the installation
Section titled “Check the installation”quiver --versionThen set Quiver up with quiver init, as the quickstart shows. It offers to run quiver install, which registers the MCP server and a session-start hook with the assistants it finds. See Connect an assistant.
Updates
Section titled “Updates”Once a day, a command run in a terminal asks GitHub for the latest release and remembers the answer in ~/.quiver/state/version-check.json. When a newer version is out, the command ends with one line on stderr with the update command that matches how you installed Quiver. Nothing is shown for quiver mcp, with --json, outside a terminal or for development builds, and a failed check is silent. quiver doctor shows the latest version too.
To turn the check off, set QUIVER_NO_UPDATE_CHECK=1.
To update, run the install command again: the install scripts, npm install -g @kheif/quiver or go install …@latest.
Uninstall
Section titled “Uninstall”quiver uninstall # remove the MCP server from every assistantrm "$(command -v quiver)" # remove the binary; with npm: npm uninstall -g @kheif/quiverrm -rf ~/.quiver # delete the libraryOn Windows, after quiver uninstall, delete %LOCALAPPDATA%\Programs\quiver and %USERPROFILE%\.quiver, and remove the folder from your user PATH in the environment variables settings.
Projects keep their .quiver.json. Delete it there if you no longer need it.