Homebrew

The formula is Formula/arcane-mcp.rb in the jmrplens/homebrew-tap tap, rewritten by the release workflow for every new release from the release’s signed checksums.txt. It is a binary formula: it picks the release binary for your system and CPU, checks it against the SHA-256 pinned in the formula and installs it as arcane-mcp, with LICENSE and THIRD_PARTY_NOTICES in its prefix. Nothing compiles and nothing else is pulled in. Nothing is published until the first release; see Installation.

Requirements

Homebrew on macOS 13 or later (Apple Silicon or Intel) or Linux (x86-64 or arm64). Windows has no Homebrew; use winget.

Install

brew install jmrplens/tap/arcane-mcp
arcane-mcp --version

The fully qualified name taps jmrplens/tap on the way, so there is no separate brew tap step. The formula’s own test runs arcane-mcp --version, and brew info arcane-mcp shows the installed version and the formula’s caveats.

Configure your client

Homebrew installs into its prefix: /opt/homebrew on Apple Silicon, /usr/local on Intel macOS, /home/linuxbrew/.linuxbrew on Linux (brew --prefix prints yours). Clients started from the desktop do not always see Homebrew’s bin directory, so give them the absolute path:

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

Every client’s entry is on Client setup.

Pin a version

The tap serves one version, the newest release (a backport is never written to it, so brew upgrade never goes back). Homebrew cannot install an older version from it. To stay on the version you have, brew pin arcane-mcp; brew unpin arcane-mcp lets upgrades through again. For an exact older version, use the release binary.

Verify it

Homebrew checks the download against the SHA-256 in the formula, which the release workflow copied from checksums.txt after verifying its cosign signature and that it is the file the release serves. The installed $(brew --prefix)/bin/arcane-mcp is the release binary byte for byte, so the checks under Verifying a release (gh attestation verify on that path) apply to it as well.

Upgrade and uninstall

The binary never updates itself; Homebrew does.

brew update
brew upgrade arcane-mcp
brew uninstall arcane-mcp
brew untap jmrplens/tap   # optional: forget the tap (it also serves other formulae)

The formula has a livecheck block on GitHub’s latest release, so brew livecheck arcane-mcp tells you when the tap is behind.