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; 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.

Install and authenticate

• Run without installing: npx @revenuecat/cli <command> (good for CI and agent sandboxes).
• Or install: brew install RevenueCat/tap/rc, or npm install -g @revenuecat/cli.
• Authenticate once with rc auth login (browser OAuth), or set RC_API_KEY. Non-interactively, pass --api-key or set RC_API_KEY.
• 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.

Discover the surface

The CLI is self-describing. Don't guess a command or flag, ask the binary:

• rc commands --json lists the full command tree. Capability IDs appear in colon form (apps:create, products:store:plan).
• rc commands --schemas --json returns every command's flags, args, and examples in one call. This is the most reliable way for an agent to discover per-command detail.
• rc schema <command> --json returns detail for a single command, but the command must be space-separated tokens (rc schema apps create), not the colon form from rc commands. rc schema apps:create silently returns the root schema, so when in doubt use rc commands --schemas.
• rc --help and rc <noun> --help give human-readable help.