The Homebrew tap for dednetsctl, the DedNets CLI and MCP server: enroll
hosts, publish services at public HTTPS URLs, set up watchdogs, and let an AI
agent drive all of it.
brew install dednets/tap/dednetsctl
dednetsctl version
dednetsctl mcp -h # the MCP server for AI agents; nothing is startedThe formula downloads a plain tarball from
https://releases.dednets.com/cli/ and installs a single static binary. It
covers macOS (Apple Silicon and Intel) and Linux (arm64 and amd64). Windows
gets no formula: Homebrew does not run there. Download the CLI from your
Console's /dist instead.
Point it at your Console and give it a token before first use:
export DEDNETS_CONSOLE=https://console.dednets.com # omit for the hosted Console
export DEDNETS_TOKEN=... # Console > Settings > API tokensDocs: https://docs.dednets.com/automation/ai-agent/
A Homebrew install pins one CLI version. If the MCP server warns on stderr
that the CLI and the Console disagree, run brew upgrade dednetsctl, or use
npx -y @dednets/mcp, which follows whichever Console you point it at.
Generated mirror, do not send pull requests here. The source of truth is
apps/homebrew-tap/ in the DedNets monorepo; this repository is regenerated by
scripts/sync-homebrew-tap.sh and hand edits are overwritten on the next sync.