Codex 및 기타 MCP 클라이언트를 위한 Agent-operated App Store 및 monetization 운영.

StoreOps MCP는 일반적으로 App Store Connect 및 RevenueCat를 통해 생활하는 작업을 위한 AI 에이전트를 제공합니다: App Store metadata, ASO 필드, 로컬라이제이션, 스크린 샷 및 미리보기 자산, 인앱 구매, 구독, 구독 그룹, RevenueCat 제품, 제목, 오퍼링, paywalls, 고객 및 수익 미터.

대부분의 모바일 팀이 여전히 수동으로 작동 할 수있는 불편한 중간 접지를 위해 제작됩니다. 카탈로그 drift, 현지화 된 메타 데이터를 채우고, IAP 사본을 준비하고 RevenueCat에 대한 App Store 설정을 비교하고, 상점 / Paywall 관측을 콘크리트 발사 작업으로 전환하십시오.

StoreOps MCP는 두 개의 별도의 로컬 MCP 서버를 포함합니다:

• appstoreconnect-mcp: App Store는 앱, 빌드, 앱 버전, 메타데이터, 스크린 샷, 인앱 구매, 구독, 가격, 고객 리뷰 및 분석 보고서에 대한 API 도구를 연결합니다.

StoreOps MCP

Agent-operated App Store and monetization operations for Codex and other MCP clients.

StoreOps MCP gives an AI agent a controlled operating layer for the work that normally lives across App Store Connect and RevenueCat: App Store metadata, ASO fields, localization, screenshots and preview assets, in-app purchases, subscriptions, subscription groups, RevenueCat products, entitlements, offerings, paywalls, customers, and monetization metrics.

It is built for the uncomfortable middle ground where most mobile teams still work manually: checking catalog drift, filling localized metadata, auditing subscriptions, preparing IAP copy, comparing App Store setup against RevenueCat, and turning store/paywall observations into concrete launch tasks.

StoreOps MCP contains two separate local MCP servers:

• appstoreconnect-mcp: App Store Connect API tools for apps, builds, app versions, metadata, screenshots, in-app purchases, subscriptions, pricing, customer reviews, and Analytics Reports for ASO-style analysis.
• revenuecat-mcp: RevenueCat API tools for projects, apps, products, entitlements, offerings, customers, customer subresources, paywalls, metrics overview, and monetization analysis.

The servers are intentionally split because App Store Connect and RevenueCat have different auth models, permissions, APIs, and failure modes. Together, they let an agent inspect and coordinate the full store-to-purchase path.

Use it as a store growth command layer: audit App Store listings, localizations, screenshots, IAPs, subscriptions, reviews, Sales and Trends, and Analytics Reports; edit supported metadata/localization resources with explicit writes; then connect that store picture to RevenueCat products, entitlements, offerings, customers, paywalls, and metrics. Use Superwall’s hosted OAuth MCP alongside StoreOps when you want to coordinate paywall campaigns, templates, placements, and experiments with the App Store and RevenueCat catalog.

What You Can Manage

StoreOps is not just a reader. It includes read-first tools plus explicit production write tools for the App Store Connect resources that are safe to target by ID.

• App Store app records, app info, app versions, builds, supported locales, and version localizations.
• App Store marketing fields including name/subtitle-style app info fields, promotional text, description, keywords, support/marketing URLs, and localized release metadata where Apple’s API allows updates.
• IAP and subscription catalog inspection, including IAPs, IAP localizations, subscription groups, subscriptions, subscription localizations, and subscription group localizations.
• IAP/subscription localization updates, so an agent can help prepare product names, descriptions, and localized purchase copy.