create-revenuecat-project

To set up a RevenueCat project from scratch, you create projects, apps, products, entitlements, and a default offering in a dependency-safe order. This ensures all resources are correctly attached for your subscription or one-time purchase rollout.

The correct order for creating entitlements and offerings in RevenueCat is dependency-safe: create products and entitlements first, attach them together, then build a default offering with packages to ensure valid relationships.

Yes, you can configure RevenueCat for both iOS and Android subscriptions simultaneously. The setup supports multi-platform app creation across App Store, Play, and web billing scenarios for mixed monetization models.

Yes, you need the RevenueCat MCP server to bootstrap your project. The setup requires using the MCP server for all tool calls, starting with listing existing projects before creating required resources.

You get public API keys for your RevenueCat app after setup through API key discovery. Once the project resources exist, the system retrieves public app API keys for embedding directly into your client apps.

If store-connected apps already exist when creating your RevenueCat project, the setup process provides specific guidance to handle them. It integrates existing apps rather than duplicating them during multi-platform app creation.