Add Revenuecat

Detect App Type

Read package.json to determine the app type:

• If expo or react-native is in dependencies → Mobile (Expo/React Native) - Proceed with setup
• If next or react-dom without expo → Web only - Inform user that RevenueCat is for mobile apps

API Key Handling

BYOK mode uses a RevenueCat API v2 secret key in REVENUECAT_API_KEY. This key must have Project configuration: read and write permissions.

Always validate MCP access early by calling mcp__revenuecat__mcp_RC_get_project.

EXPO_PUBLIC_REVENUECAT_API_KEY is still required by the mobile app runtime. If it is missing:

1. Use mcp__revenuecat__mcp_RC_get_project to get project info.
2. Use mcp__revenuecat__mcp_RC_list_apps to get the app ID.
3. Use mcp__revenuecat__mcp_RC_list_public_api_keys to retrieve the public SDK key.
4. Set it using the secrets API:

   window.conveyor.secrets.setSecret(projectId, 'EXPO_PUBLIC_REVENUECAT_API_KEY', sdkKey)
   

Do not claim account-connection auto-configuration. In this IDE, key propagation is BYOK-driven. Do not tell users to manually edit .env files.

Provisioning Policy (Required)

When MCP access is available, the integration is only considered complete after resources are verified end-to-end:

1. Resolve project via mcp__revenuecat__mcp_RC_get_project.
2. Ensure at least one app exists via mcp__revenuecat__mcp_RC_list_apps (create one if none exist).
3. Ensure entitlement premium exists (create if missing).
4. Ensure offering default exists (create if missing).
5. Ensure at least one subscription product exists for the target app via mcp__revenuecat__mcp_RC_list_products (create if missing).
6. Ensure EXPO_PUBLIC_REVENUECAT_API_KEY is set from mcp__revenuecat__mcp_RC_list_public_api_keys.

Never report "production-ready" if these checks were not completed. Never claim products or offerings are configured unless MCP list calls confirm they exist.

Mobile (Expo/React Native) Steps

When reasoning about Expo/React Native issues, treat expo-sqlite/localStorage/install as an Expo compatibility shim/package path only. Do not treat it as permission to use browser localStorage semantics in app code.

1. Check if RevenueCat is already installed by reading package.json. If react-native-purchases is in dependencies, skip to step 3.

2. Install dependencies (only if not already installed):

   npx expo install react-native-purchases expo-build-properties
   

   If this fails, report the error and stop. Do NOT retry.

3. Update app.json safely (no string replacements):

   • Read and parse app.json as JSON before making changes. If parse fails, stop and report the parse error.
   • Ensure expo.plugins exists as an array.
   • Upsert exactly one expo-build-properties entry using templates/app-json-plugin.json:
     • If an expo-build-properties plugin entry already exists (string or tuple form), replace it with: ["expo-build-properties", { "ios": { "deploymentTarget": "15.1" } }]
     • Otherwise append that tuple to expo.plugins.
   • Write valid JSON back to app.json.
   • Validate after write (mandatory): node -e "JSON.parse(require('fs').readFileSync('app.json','utf8'))".
   • If validation fails, stop immediately and report the exact app.json error. Do not continue setup steps.
   • IMPORTANT: Do NOT add react-native-purchases to the plugins array. It does not ship an Expo config plugin (app.plugin.js) and adding it causes PluginError: Unable to resolve a valid config plugin. It only needs to be a dependency (installed in step 2).

4. Create RevenueCatProvider - Copy templates/providers/RevenueCatProvider.tsx into the project's providers directory and wrap the app layout with it.

5. Create hooks - Copy the hooks from templates/hooks/ into the project:

   • useOfferings.ts - Fetches available subscription offerings
   • usePurchases.ts - Handles purchase flows and restores

6. Create a paywall component - Build a subscription paywall UI that:

   • Uses useOfferings to display available packages
   • Uses usePurchases to handle purchase button clicks
   • Shows loading states and error handling
   • Includes a "Restore Purchases" button
   • Handles missing currentOffering safely (no crash)
   • Handles availablePackages.length === 0 safely (no crash)

RevenueCat MCP Tools

When REVENUECAT_API_KEY is present and valid, you have access to RevenueCat's official MCP tools:

• mcp__revenuecat__mcp_RC_get_project - Get project info (returns array of projects)
• mcp__revenuecat__mcp_RC_list_apps - List apps for a project
  • Input: { project_id: string }
• mcp__revenuecat__mcp_RC_list_public_api_keys - List public API keys (SDK keys) for an app
  • Input: { project_id: string, app_id: string }
• mcp__revenuecat__mcp_RC_create_app - Create a new app
  • Input: { project_id: string, name: string, type: string, bundle_id?: string, package_name?: string }
• mcp__revenuecat__mcp_RC_list_entitlements - List entitlements for a project
  • Input: { project_id: string }
• mcp__revenuecat__mcp_RC_create_entitlement - Create new entitlement
  • Input: { project_id: string, lookup_key: string, display_name: string }
• mcp__revenuecat__mcp_RC_list_offerings - List offerings for a project
  • Input: { project_id: string }
• mcp__revenuecat__mcp_RC_create_offering - Create new offering
  • Input: { project_id: string, lookup_key: string, display_name: string }
• mcp__revenuecat__mcp_RC_list_products - List products for a project
  • Input: { project_id: string }
• mcp__revenuecat__mcp_RC_create_product - Create new product
  • Input: { project_id: string, app_id: string, store_identifier: string, type: string }

Using MCP Tools

When the user wants to set up entitlements or offerings:

1. Use mcp__revenuecat__mcp_RC_get_project to find their project ID
2. Use mcp__revenuecat__mcp_RC_list_apps to see existing apps
3. Use mcp__revenuecat__mcp_RC_list_entitlements and ensure premium exists
4. Use mcp__revenuecat__mcp_RC_list_offerings and ensure default exists
5. Use mcp__revenuecat__mcp_RC_list_products and ensure at least one product exists for the app
6. Retrieve and set EXPO_PUBLIC_REVENUECAT_API_KEY using mcp__revenuecat__mcp_RC_list_public_api_keys
7. Update generated code to use resilient checks and safe empty states

Required Secrets

• REVENUECAT_API_KEY — RevenueCat API v2 secret key for MCP (must include Project configuration read/write permissions)
• EXPO_PUBLIC_REVENUECAT_API_KEY — RevenueCat public SDK key for the mobile app runtime (populate via MCP if missing)

After Integration

Tell the user exactly what was configured, for example: "RevenueCat SDK is set up. I verified MCP access with your REVENUECAT_API_KEY and configured EXPO_PUBLIC_REVENUECAT_API_KEY for the app runtime."

Do not claim account-connection-based auto configuration.