为Codex和其他MCP客户端提供代理操作的App Store和变现运营。

StoreOps MCP 为 AI 代理提供了一个受控的操作层，涵盖通常存在于 App Store Connect 和 RevenueCat 的工作：App Store 元数据、ASO 字段、本地化、截图和预览资产、应用内购买、订阅、订阅组、RevenueCat 产品、权限、产品、付费墙、客户和变现指标。

它为一个令人不安的中间地带设计，大多数移动团队仍手动操作：检查目录漂移、填写本地化元数据、审核订阅、准备内购文案、将App Store设置与RevenueCat进行比较，并将商店/付费墙观察转化为具体的启动任务。

StoreOps MCP 包含两个独立的本地 MCP 服务器：

• appstoreconnect-mcp：应用、构建、版本、元数据、截图、应用内购买、订阅、定价、客户评价及ASO风格分析报告的App Store Connect 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.