revenuecat-cli: driving RevenueCat from the terminal

rc is the official RevenueCat command line interface. It covers most of the same project, app, product, entitlement, offering, paywall, chart, and store-state operations as the RevenueCat MCP server (the CLI adds paywall generate/edit and paywall image/font upload; the MCP server has some SDK feature-gate and experiment tools the CLI does not). Use whichever surface is available; this skill is the reference for the CLI path.

Before the first command

The CLI needs a shell. Without one (for example in a chat app with only the MCP server), use MCP, or tell the user which rc command to run or which dashboard page to use.

Check it is installed: rc --version. If that fails, pick one:
- Run without installing: npx @revenuecat/cli <command> everywhere rc appears below. Needs Node. Best for CI and agent sandboxes.
- Install on macOS/Linux: brew install RevenueCat/tap/rc.
- Install with npm: npm install -g @revenuecat/cli.
Installing changes the user's machine, so ask before running brew or npm install -g. npx needs no permission beyond running the command.
Check it is logged in: rc auth status --json. The CLI does not share the MCP server's login. If no credential is active, ask the user to run rc auth login themselves: it opens a browser for OAuth. In CI, set RC_API_KEY or pass --api-key.
Check the project: pass --project-id <id>, or have the user set a default with rc projects use.

The CLI authenticates with a RevenueCat secret key (sk_...); that is correct because the CLI is a server-side tool. This is not the same as the public SDK keys (appl_/goog_/amzn_) you fetch for client app code. Never put a secret key in an app, and never ask the user to paste one into the chat.