Users on macOS/Linux expect brew install mcpc — today the only options are npm install -g @apify/mcpc or bun install -g, which require them to set up a JavaScript runtime first.

Two steps:

1. Own tap — apify/homebrew-tap, so brew tap apify/tap && brew install mcpc works, with the formula updated automatically on every release.
2. homebrew-core (follow-up) — makes plain brew install mcpc work with no tap and adds prebuilt bottles. mcpc meets the acceptance policy, including the stricter notability bar for self-submissions, and the mcpc formula name is unused.

Notes for whoever picks this up:

• The published npm tarball already contains dist/, bin/ and skills/, so the formula only needs depends_on "node" and npm install *std_npm_args — nothing to build.
• bin/mcpc ships #!/usr/bin/env node, so the formula must rewrite the shebang to Homebrew's node; otherwise a stale nvm/asdf node earlier in PATH can run mcpc under a runtime older than the required >= 22.12.
• @napi-rs/keyring is a native addon tied to a Node.js ABI, and mcpc silently falls back to file-based credential storage when it fails to load — the formula test needs an explicit canary so a Homebrew node major bump doesn't quietly downgrade credential storage.