asc-revenuecat-catalog-sync

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.

913stars48forksUpdated 7/17/2026

#ios #subscriptions #app-store-connect #revenuecat #cli #catalog-sync

Security Assessment

Safe(100/100)

Security Score100/100

About asc-revenuecat-catalog-sync

asc-revenuecat-catalog-sync keeps an App Store Connect (ASC) subscription and in-app purchase catalog aligned with RevenueCat products, entitlements, offerings, and packages. It solves the problem of drift between the two systems by reconciling them against a canonical identifier: the ASC productId, which maps to RevenueCat's store_identifier. The skill can bootstrap RevenueCat from an existing ASC catalog, create missing ASC subscriptions and IAPs before mapping them into RevenueCat, and produce a drift audit before a release.

The workflow uses the asc CLI to read and create ASC resources and the RevenueCat MCP server to configure RevenueCat resources. It operates in two modes. Audit mode (the default, read-only) reads both catalogs, builds a diff of items missing in ASC, missing in RevenueCat, and mapping conflicts, then presents a plan and waits for confirmation. Apply mode executes approved actions in order: ensure ASC groups/subscriptions/IAPs, then RevenueCat apps/products, entitlements and product attachments, and finally offerings/packages. Concrete commands include asc subscriptions groups list, asc subscriptions setup, asc iap create, and asc validate subscriptions --strict, alongside MCP tools such as mcp_RC_get_project, mcp_RC_list_products, and mcp_RC_list_entitlements. Product type mappings are defined explicitly (e.g., ASC CONSUMABLE to RevenueCat consumable).

It targets developers setting up or syncing subscription catalogs across ASC and RevenueCat. Preconditions include configured asc authentication (asc auth login or ASC_* env vars), a configured and authenticated RevenueCat MCP server, the ASC app ID, the RevenueCat project_id, and a write-enabled RevenueCat API v2 key for applying changes. Safety defaults require starting in audit mode, explicit confirmation before writes, never deleting resources, and continuing on per-item failures while reporting them at the end. A stated boundary is that RevenueCat MCP does not create ASC products directly; asc must create them first.

FAQ

What are the prerequisites to run this skill?

You need asc authentication configured (via asc auth login or ASC_* environment variables), a configured and authenticated RevenueCat MCP server, the ASC app ID (APP_ID), the RevenueCat project_id, and the target RevenueCat app type (app_store or mac_app_store) with bundle ID for create flows. To apply changes you must use a write-enabled RevenueCat API v2 key.

Will it make changes without my approval?

No. It starts in audit mode, which is read-only, and requires explicit confirmation before any writes. It also never deletes resources in this workflow.

How are products matched between ASC and RevenueCat?

The primary cross-system key is the ASC productId matched to RevenueCat's store_identifier. Display names are never used as unique identifiers, and productId should stay stable once products are live.

Can RevenueCat MCP create the App Store Connect products for me?

No. RevenueCat MCP configures RevenueCat resources only; it does not create ASC products directly. You use asc commands to create missing ASC subscription groups, subscriptions, and IAPs before mapping them into RevenueCat.