Asc Revenuecat Catalog Sync

This reconciles your App Store Connect subscription catalog with RevenueCat's product configuration using both the asc CLI and RevenueCat MCP server. You run it in audit mode first to see the drift between ASC subscriptions, IAPs, and your RevenueCat products, entitlements, and offerings, then apply mode to create missing items and wire up the mappings. It matches on store identifiers, won't auto-delete anything, and handles the full flow from creating ASC subscription groups down to attaching products to RevenueCat packages with the right identifier conventions. The main value is deterministic bootstrapping and preventing the usual catalog drift headaches before release. Needs both systems already authenticated and you'll want a write-enabled RevenueCat API key for applying changes.

skills.sh installs: 6.3K
GitHub stars: 1.1K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add rorkai/app-store-connect-cli-skills --skill asc-revenuecat-catalog-sync --agent claude-code

Installs into .claude/skills of the current project.

Files

asc RevenueCat catalog sync

Use this skill to keep App Store Connect (ASC) and RevenueCat aligned, including creating missing ASC items and mapping them to RevenueCat resources.

When to use

You want to bootstrap RevenueCat from an existing ASC catalog.
You want to create missing ASC subscriptions/IAPs, then map them into RevenueCat.
You need a drift audit before release.
You want deterministic product mapping based on identifiers.

Preconditions

asc authentication is configured (asc auth login or ASC_* env vars).
RevenueCat MCP server is configured and authenticated.
In Cursor and VS Code, OAuth auth is available for RevenueCat MCP. API key auth is also supported.
You know:
- ASC app ID (APP_ID)
- RevenueCat project_id
- target RevenueCat app type (app_store or mac_app_store) and bundle ID for create flows
Use a write-enabled RevenueCat API v2 key when applying changes.