go install

go install downloads the module and builds the server on your machine. The result is the same program as the release binary, but built by your toolchain rather than the release workflow, so it carries no signature or attestation and reports no version of its own. From the first release, @latest resolves to the newest release tag. Until then: while the repository is private, go install cannot fetch the module at all; once it is public without a tag, @latest builds the newest commit of main as a pseudo-version, which is not a release (see Installation).

Requirements

Go 1.27.2 or later. With Go 1.21 or later already installed, the default GOTOOLCHAIN=auto downloads 1.27.2 when the module asks for it; with an older Go, install a current one first.

Install

The module is github.com/jmrplens/arcane-mcp, and the command lives in cmd/arcane-mcp:

CGO_ENABLED=0 go install github.com/jmrplens/arcane-mcp/cmd/arcane-mcp@latest
arcane-mcp --version

The binary lands in $(go env GOBIN), or $(go env GOPATH)/bin (usually ~/go/bin) when GOBIN is unset. CGO_ENABLED=0 gives the static binary the release ships; the server uses no C code, so it changes nothing else.

arcane-mcp --version prints arcane-mcp dev (none, unknown): the version, commit and date are stamped in by the release build’s linker flags, which go install does not set. Note the version you installed if you need to know it later (go version -m $(go env GOPATH)/bin/arcane-mcp shows the module version it was built from).

Configure your client

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

{
  "mcpServers": {
    "arcane": {
      "command": "/home/you/go/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

Name a release tag instead of latest: go install github.com/jmrplens/arcane-mcp/cmd/arcane-mcp@vX.Y.Z. @main builds the current development state, which is not a release.

Verify it

The Go toolchain checks the module’s source against the Go checksum database (sum.golang.org), so you build what every other user of that version builds. The binary itself is yours: the release signatures and attestations under Verifying a release cover the release workflow’s binaries, not a local build. For the signed binary, use the release binary or a package manager.

Update and uninstall

Run the same go install …@latest again to update; delete $(go env GOPATH)/bin/arcane-mcp (or the one in GOBIN) to uninstall. To build from a clone instead, see Getting started.