Skip to main content

Download

4 mins

The Ogham CLI is the Go companion for Ogham MCP. Single self-contained binary, no runtime dependencies, cross-platform. Use it for the local dashboard, cross-client memory ops, native store without a Python sidecar, and enterprise-friendly stdout logging.

Pick the build for your platform and architecture. All binaries are reproducible, -trimpath built, and include SHA256 checksums.

Windows

Windows 10+ · PowerShell
Version: latest stable SHA256: checksums.txt Source: github.com/ogham-mcp/ogham-cli License: MIT

One-line install

macOS / Linux – picks the right arch automatically, unpacks into ~/.local/bin/, and verifies the SHA256:

curl -sSL https://github.com/ogham-mcp/ogham-cli/releases/latest/download/install.sh | bash

Windows (PowerShell):

iwr -useb https://github.com/ogham-mcp/ogham-cli/releases/latest/download/install.ps1 | iex

Homebrew (tap opening soon):

# brew install ogham-mcp/tap/ogham-cli   # coming after homebrew-tap flip

Manual install

# 1. Download the tarball for your platform (pill buttons above)
tar -xzf ogham-cli-darwin-arm64.tar.gz

# 2. Move the binary onto your PATH
mv ogham-cli /usr/local/bin/
chmod +x /usr/local/bin/ogham-cli

# 3. Verify it runs
ogham-cli --version

Verify the checksum before running unknown binaries:

curl -sSL https://github.com/ogham-mcp/ogham-cli/releases/latest/download/checksums.txt \
  | shasum -a 256 -c --ignore-missing

macOS: first-run unblock (unsigned binary)

Pre-release binaries are unsigned. Paid Apple Developer signing + notarization is on the roadmap for a future point release. Until then, macOS Gatekeeper will block the binary on first run with:

ogham-cli” cannot be opened because the developer cannot be verified.

Pick one of these one-time fixes -- they all do the same job (remove the com.apple.quarantine extended attribute that Safari / curl / Finder tag downloads with):

Option 1 – remove the quarantine flag (recommended for terminal users):

xattr -d com.apple.quarantine /usr/local/bin/ogham-cli

One line, permanent for that file. No admin rights needed if the binary lives under your user directory. Re-apply after every upgrade, or use Option 3 to wrap into a one-time install.

Option 2 – right-click Open from Finder (for users who prefer the GUI):

  1. Open Finder, navigate to the binary
  2. Ctrl + click (or right-click) the binary
  3. Choose Open, then Open again in the confirmation dialog
  4. macOS records your approval; future runs launch without prompt

Option 3 – ad-hoc code-sign the binary locally (most robust):

codesign -s - --force --deep /usr/local/bin/ogham-cli

The -s - flag means “ad-hoc sign with no identity.” The binary is now locally-signed and Gatekeeper stops complaining. Free, requires Xcode command-line tools (which you already have if you use git on macOS).

Option 4 – allow via System Settings after a failed first run:

  1. Try to run the binary; macOS blocks it and shows a dialog
  2. Open System Settings → Privacy & Security
  3. Scroll to “Security” — an “Open Anyway” button appears for the blocked binary
  4. Click it, then Open in the confirmation

Why this is needed: Apple Gatekeeper quarantines any executable downloaded from the internet that lacks a notarized Developer ID signature. We'll ship notarized builds once the project has a paid Apple Developer account — tracked as v0.4.1 distribution polish in the ogham-cli repo roadmap. Until then, a one-time xattr or ad-hoc sign is the tax.

Verify first. Before running any of the above, compare the file's SHA256 against checksums.txt. If the hash matches, the binary is the one GoReleaser built from the tagged commit. The checksum file itself is listed alongside every release on GitHub and fetched over TLS.

Windows: first-run SmartScreen

On Windows, SmartScreen may show a blue “Windows protected your PC” panel. Click More infoRun anyway. Authenticode signing is on the same roadmap as macOS notarization.

Linux: no Gatekeeper equivalent

Linux distributions don't enforce a Gatekeeper-style quarantine. After chmod +x, the binary runs. You may still want to verify against checksums.txt.

Next steps

Once the binary is on your PATH:

  • Quickstart → – connect Ogham CLI to a running MCP server
  • Dashboard → – local web UI for memory ops, audit log, and health
  • Skills → – Ogham skills for Claude Code, Cursor, OpenCode, Codex