Mimi Seed MCP

What @yoonion/mimi-seed-mcp MCP server does

The @yoonion/mimi-seed-mcp MCP server exposes app launch and operations workflows through MCP. Its supported service areas include Firebase, AdMob, Google Play, App Store Connect, Google Cloud IAM, and release-readiness checks. Developers can use an AI client to inspect project state, prepare release material, manage selected store data, and connect the services needed by a mobile app.

The repository also includes Release Doctor, a local checker for Expo, React Native, Android, iOS, and Unity repositories. It examines repository evidence for app identifiers, Android target API requirements, Google Play Billing dates, App Store upload requirements, and legacy Firebase Cloud Messaging usage. Results include evidence, suggested actions, and official sources. The checker can emit JSON and fail CI when blockers are found.

How it works

The package can run as a local stdio MCP server on the developer’s machine. The local mode is intended for broader write operations, including release-note application, screenshot uploads, submission workflows, and Firebase, AdMob, and IAM management. It uses Google OAuth and requires Node 20 or newer.

A separate remote MCP endpoint is available through the Mimi Seed web console. Remote access requires an account and personal access token. That mode covers readiness, blockers, drafts, checklists, published screenshots, workspace-shared BigQuery, and App Store IAP review-note or review-screenshot writes. Broader store writes remain local-only according to the documented split.

Before connecting accounts, npx mimi-seed check --local can scan a repository without the full MCP package or network access. After accounts are connected, the same command can add remote checks for listings, screenshots, uploaded builds, and submission state. A passing local check is not presented as proof of store approval.

Setup and configuration

Install the local server with the package command used by the client. For Claude Code, the bare registration is claude mcp add mimi-seed-local -- npx -y @yoonion/mimi-seed-mcp@latest. Claude Desktop uses the same npx command in its MCP configuration, while Codex can register the command in config.toml or through the documented plugin installation.

After installation, start a new client session so the tools become available. Claude Code loads the large tool catalog lazily; if the first call reports an input validation error, the documented recovery is to ask the agent to load the Mimi Seed tools with ToolSearch first.

Run npx mimi-seed init inside an app repository to detect project identifiers and create agent context files. The command supports common Expo, Gradle, iOS, and Unity project evidence. Run npx mimi-seed setup to connect stores, CI, and social accounts through a guided wizard. The remote configuration uses MIMI_SEED_TOKEN for the personal access token.

Tools and capabilities

Capabilities described in the material include:

• Checking release blockers and readiness evidence locally or remotely.
• Generating release-note drafts and applying them to supported stores in local mode.
• Reviewing or managing store screenshots, builds, and submission state.
• Adding Android apps to Firebase and downloading google-services.json.
• Managing Firebase, AdMob, IAM, and related connected Google services through the local workflow.
• Sharing selected workspace data through BigQuery and handling App Store IAP review notes or screenshots remotely.

The exact tool catalog is broader than the examples above, and the available operations depend on whether the local or remote MCP is configured.