Reconcile App Store Connect subscriptions and in-app purchases with RevenueCat products, entitlements, offerings, and packages using asc and RevenueCat MCP. Use when setting up or syncing subscription catalogs across ASC and RevenueCat.

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. Safety defaults Start in audit mode (read only). Require explicit confirmation before writes. Never delete resources in this workflow. Continue on per item failures and report all failures at the end. Canonical identifiers Primary cross system key: ASC productId == RevenueCat store identifier . Keep productId stable once products are live. Do not use display names as unique identifiers. Scope boundary RevenueCat MCP configures RevenueCat resources; it does not create App Store Connect products directly. Use asc commands to create missing ASC subscription groups, subscriptions, and IAPs before RevenueCat mapping. Modes 1) Audit mode (default) 1. Read ASC source catalog. 2. Read RevenueCat target catalog. 3. Build a diff with actions: missing in ASC missing in RevenueCat mapping conflicts (identifier/type/app mismatch) 4. Present the plan. Audit only requests finish with findings; apply requests require approval covering the complete current diff. Reuse prior approval if the refreshed diff is unchanged. 2) Apply mode (explicit) Execute approved actions in this order: 1. Ensure ASC groups/subscriptions/IAP exist. 2. Ensure RevenueCat app/products exist. 3. Ensure entitlements and product attachments. 4. Ensure offerings/packages and package attachments. 5. Verify and print a final reconciliation summary. Step by step workflow Step A Read current ASC catalog Step B Read current RevenueCat catalog (MCP) Use these MCP tools (with project id and pagination where applicable): mcp RC get project mcp RC list apps mcp RC list products mcp RC list entitlements mcp RC list offerings mcp RC list packages Step C Build mapping plan Map ASC product types to RevenueCat product types: ASC subscription RevenueCat subscription ASC IAP CONSUMABLE RevenueCat consumable ASC IAP NON CONSUMABLE RevenueCat non consumable ASC IAP NON RENEWING SUBSCRIPTION RevenueCat non renewing subscription Suggested entitlement policy: subscriptions: one entitlement per subscription group (or explicit map provided by user) non consumable IAP: one entitlement per product consumable IAP: no entitlement by default unless user asks Step D Ensure missing ASC items (if requested) Resolve every parent and version before writing. Match groups by exact reference name and products by productId ; never treat a display name as identity. Reuse the canonical ID when the resource already exists, and run a create command only when the fully paginated read proves it is missing. A RevenueCat product mapping is not proof that the corresponding ASC subscription is review ready. Each adjacent create/update pair above is conditional, not a sequence to run blindly: create when the list has no match, update when the resolved match has different values, and do nothing when it already matches. Capture .data.id from a create response or .data[].id from the preceding list as the canonical ID used by later commands. For each version list, zero PREPARE FOR SUBMISSION matches means create, one means reuse that ID, and more than one means stop and require the user to choose an explicit version ID. Do not create a version to resolve ambiguity: parent deletion did not reliably cascade IAP or subscription versions in live testing. subscriptions setup finishes the parent, App Review screenshot delivery, complete App Store price matrix, and sale availability. The version scoped commands finish the group and subscription localizations that RevenueCat cannot. Keep sale availability scoped to the requested territories; pricing still needs Apple's complete equalized territory matrix. no verify is intentional in this split workflow because final verification must wait until the version metadata exists; the explicit readbacks and validator are the final gate. If an existing API created subscription remains MISSING METADATA even though the selected base price is unchanged, re run the same setup inputs with repair . Repair atomically rebuilds and re saves the complete equalized price matrix; it is not a duplicate single price POST. For every resolved ASC subscription, require this final gate before creating or attaching its RevenueCat product. Run it after the final ASC reconciliation even when the subscription and its selected version were reused without any ASC write: For every resolved ASC IAP, require the IAP gate before creating or attaching its RevenueCat product. Run it after the final ASC reconciliation even when the IAP and its selected version were reused without any ASC write: Both commands are strict mapping gates, not post write smoke tests. Do not map any resolved or reused subscription while validation reports warnings, errors, MISSING METADATA , a review screenshot that is not COMPLETE , or incomplete or unverified pricing coverage. Do not map any resolved or reused IAP while its validator reports warnings or errors. A zero write audit or apply run must still execute the applicable gate and require a zero exit status before RevenueCat product creation or attachment. Direct redirection preserves each validator's exit status. Retain ./audit/subscriptions validation.json and ./audit/iap validation.json as final audit evidence. Step E Ensure RevenueCat app and products Use MCP: create app if missing: mcp RC create app create products: mcp RC create product store identifier = ASC productId app id = RevenueCat app ID type from mapping above Step F Ensure entitlements and attachments Use MCP: list/create entitlements: mcp RC list entitlements , mcp RC create entitlement attach products: mcp RC attach products to entitlement verify attachments: mcp RC get products from entitlement Step G Ensure offerings and packages (optional) Use MCP: list/create/update offerings: mcp RC list offerings mcp RC create offering mcp RC update offering ( is current=true only if requested) list/create packages: mcp RC list packages mcp RC create package attach products to packages: mcp RC attach products to package with eligibility criteria: "all" Recommended package keys: ONE WEEK $rc weekly ONE MONTH $rc monthly TWO MONTHS $rc two month THREE MONTHS $rc three month SIX MONTHS $rc six month ONE YEAR $rc annual lifetime IAP $rc lifetime custom $rc custom <name Expected output format Return a final summary with: ASC created counts (groups/subscriptions/IAP) RevenueCat created counts (apps/products/entitlements/offerings/packages) attachment counts (entitlement products, package products) skipped existing items failed items with actionable errors Example: Agent behavior Always run audit first, even in apply mode. Reuse approval covering the complete current diff for its create/update operations. Ask again only when approval is absent or additional or materially changed actions fall outside it. Match by store identifier first. Use full pagination ( paginate for ASC, starting after for RevenueCat tools). Continue processing after per item failures and report all failures together. Never auto delete ASC or RevenueCat resources in this skill. For every resolved subscription, including a reused no write match, run asc validate subscriptions app "APP ID" strict output json pretty , save its JSON, and block RevenueCat creation or attachment unless the gate exits zero with no missing metadata or incomplete pricing. For every resolved IAP, including a reused no write match, run asc validate iap app "APP ID" strict output json pretty , save its JSON, and block RevenueCat creation or attachment unless the gate exits zero. Common pitfalls Wrong RevenueCat project id or app ID. Creating RC products under the wrong platform app. Accidentally assigning consumables to entitlements. Skipping the post create ASC re read step. Mapping a RevenueCat product before ASC setup finishes localization, review screenshot delivery, the complete price matrix, and availability. Missing offering/package verification after product creation. Additional resources Workflow examples: [examples.md](examples.md) Source references: [references.md](references.md)

asc-revenuecat-catalog-sync