Release binary

Each GitHub release carries the static binary for every supported system, raw and in archives. It is the binary every other channel except Docker installs, so this page is also what Homebrew, winget, npm, PyPI and NuGet do for you. Nothing is published until the first release; see Installation.

Requirements

No runtime or library: the binary is statically linked (no libc), so the Linux builds run on glibc and musl (Alpine) systems alike. On macOS it needs macOS 13 (Ventura) or later, the minimum the Go toolchain writes into the darwin binaries.

Pick an asset

Asset	For
`arcane-mcp-linux-amd64`, `arcane-mcp-linux-arm64`	Linux on x86-64 or arm64
`arcane-mcp-darwin-arm64`, `arcane-mcp-darwin-amd64`	macOS on Apple Silicon or Intel
`arcane-mcp-darwin-universal`	macOS, one binary for both
`arcane-mcp-windows-amd64.exe`, `arcane-mcp-windows-arm64.exe`	Windows on x64 or arm64
`arcane-mcp_<version>_<os>_<arch>.tar.gz` (`.zip` on Windows)	The same binary with `LICENSE`, `README.md` and `THIRD_PARTY_NOTICES`

Every release also has checksums.txt (SHA-256 of every asset except the Claude Desktop bundles, which have their own attestation), its signature checksums.txt.sigstore.json, an SPDX SBOM per raw binary (<binary>.sbom.json) and THIRD_PARTY_NOTICES.

Install

On Linux or macOS, download the raw binary, check it and put it in a directory on your PATH:

ASSET=arcane-mcp-linux-amd64   # pick yours from the table
curl -fLO "https://github.com/jmrplens/arcane-mcp/releases/latest/download/$ASSET"
curl -fLO https://github.com/jmrplens/arcane-mcp/releases/latest/download/checksums.txt
grep " $ASSET$" checksums.txt | sha256sum --check   # macOS: … | shasum -a 256 --check
install -m 0755 "$ASSET" ~/.local/bin/arcane-mcp
arcane-mcp --version

On Windows, download arcane-mcp-windows-amd64.exe (or the arm64 one) from the release page, rename it arcane-mcp.exe, put it in a folder of its own (for example %LOCALAPPDATA%\Programs\arcane-mcp) and add that folder to your user PATH, or give clients its full path. Get-FileHash .\arcane-mcp.exe prints the SHA-256 to compare with checksums.txt.

macOS and downloads from a browser. A file a browser downloads is marked as quarantined, and macOS refuses to run a command-line binary that Apple has not notarized; the release binaries are signed with cosign, not with an Apple certificate. Download with curl as above, or clear the mark: xattr -d com.apple.quarantine arcane-mcp.
Windows SmartScreen may warn about an unrecognised download the first time; the file is the one listed in checksums.txt.

Pin a version

releases/latest/download/ follows the newest release. For a fixed version, use its tag:

curl -fLO "https://github.com/jmrplens/arcane-mcp/releases/download/vX.Y.Z/$ASSET"

Verify it

The checksum above proves the file matches checksums.txt; the signature of checksums.txt and the build provenance of each asset prove both came from this repository’s release workflow. The commands are under Verifying a release.

Configure your client

Use the binary’s absolute path: a client started from the desktop does not see your shell’s PATH.

{
  "mcpServers": {
    "arcane": {
      "command": "/home/you/.local/bin/arcane-mcp",
      "env": {
        "ARCANE_URL": "https://arcane.example.com",
        "ARCANE_API_KEY": "<your Arcane API key>"
      }
    }
  }
}

On Windows the command is the .exe path, with backslashes escaped in JSON ("C:\\Users\\you\\AppData\\Local\\Programs\\arcane-mcp\\arcane-mcp.exe"). Every client’s entry is on Client setup.

Update and uninstall

The binary never updates itself. To update, download the newer release and replace the file; clients pick it up the next time they start the server. To uninstall, delete the file.