Smplify CLI Distribution

Understand how the CLI ships and how to roll it out.

The public install path is the branded CLI endpoint today, with GitHub Releases as the canonical artifact source and official Homebrew support planned once packaging review is complete.

Release channel

Published binaries and checksums ship through GitHub Releases, while the branded endpoint provides the first-party installation front door.

Canonical public endpoint

curl -fsSL https://cli.smplify.com/install.sh | sh

Artifact source of truth

https://github.com/smplify-mdm/smplify-cli/releases

Rollout guidance

Package the CLI the same way you would any other infrastructure surface: pin the version you deploy, verify the installer path, and prefer JSON output anywhere automation or AI-assisted tooling needs deterministic behavior.

Recommended for teams

Pin a specific release in CI and internal runbooks
Use --output json for shell and agent workflows
Prefer the branded installer endpoint for end-user docs

Operational note

Official Homebrew support is intentionally sequenced after stable release packaging review, so the branded installer remains the canonical public path today.

Review Releases Verify Installer Endpoint

Homebrew

Official Homebrew formula submission is planned after stable release and packaging review.

Planned install command

brew install smplify

Part of the same docs family

The CLI, MCP gateway, and main docs are intentionally presented as one connected platform surface for operators, developers, and AI-native workflows.

Main Docs

Platform, API, and integration guidance for the broader Smplify surface.

Open Main Docs

MCP Docs

Hosted MCP connection, security, supported tools, and reference guidance for agentic usage.

Open MCP Docs