Codex などの MCP クライアント向けに、アプリストアや収益化業務を運用

StoreOps MCP は、通常、App Store Connect と RevenueCat: App Store のメタデータ、ASO のフィールド、ローカリゼーション、スクリーンショット、プレビューアセット、アプリ内購入、サブスクリプション、サブスクリプショングループ、RevenueCat 製品、資格、提供、ペイウォール、顧客、および収益評価指標を管理します。

これは、ほとんどのモバイルチームが手動で動作する不快なミドルグラウンドのために構築されています: カタログのドリフトをチェックし、ローカライズされたメタデータを充填し、サブスクリプションを監査し、IAPのコピーを準備し、RevenueCatに対するApp Storeのセットアップを比較し、ストア/ペイウォールの観察を具体的な起動タスクに変換します。

StoreOps MCP には、ローカルの MCP サーバを 2 台追加します。

• [appstoreconnect-mcp]: App Storeは、アプリ、ビルド、アプリのバージョン、メタデータ、スクリーンショット、アプリ内購入、サブスクリプション、価格設定、顧客レビュー、およびASOスタイルの分析のための分析レポートの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.