🌐 Homepage ·
🔑 Get API Token ·
📦 npm ·
🇰🇷 한국어
How many tabs do you have open right now to ship one app?
Play Console · App Store Connect · Firebase · AdMob · Google Cloud IAM...
Write release notes, check screenshot specs, reply to reviews, wire up Firebase — all in separate dashboards, all manual.
Mimi Seed handles all of this through Claude Code or Codex conversation.
"Is my app ready to ship?"
→ Readiness Score 87/100 · 2 blockers: missing 6.9" screenshots, What's New empty
"Write release notes from commits since the last tag, Korean and English, and push to Play Store"
→ 3 tones (concise / detailed / marketing) × 2 locales generated · Apply now?
"Reply to this 1-star review with an empathetic tone"
→ Draft ready · Review before posting?
"Add an Android app to Firebase and download google-services.json"
→ App created · Add SHA-1 fingerprint?
30-Second Setup
Option A — Remote MCP (recommended for status & readiness · requires web console account)
# 1. Create account: https://mimi-seed.pryzm.gg/auth/signin
# 2. Issue a PAT: https://mimi-seed.pryzm.gg/workspace/api-tokens
# 3-a. Register in Claude Code:
claude mcp add --transport http mimi-seed https://mimi-seed.pryzm.gg/api/mcp \
--header "Authorization: Bearer <PAT>"
# 3-b. Or register in Codex:
npx mimi-seed mcp codex --write
Done. Start talking to Claude Code or Codex.
Remote vs Local — pick by what you need. Remote MCP exposes a ~16-tool read & diagnostic subset (readiness, blockers, drafts, checklist, publish screenshots). For full store-write automation — release-notes apply, screenshot upload, Firebase / AdMob / IAM / BigQuery (the 110+ tools below) — use Option B (Local MCP).
Option B — Local MCP (Google OAuth · runs on your machine)
# Claude Code
claude mcp add mimi-seed -- npx -y @yoonion/mimi-seed-mcp
Codex (~/.codex/config.toml):
[mcp_servers.mimi-seed]
command = "npx"
args = ["-y", "@yoonion/mimi-seed-mcp"]
enabled = true
# First-time auth (opens browser)
npx -y @yoonion/mimi-seed-mcp mimi-seed-auth
Claude Desktop (claude_desktop_config.json):
{
"mcpServers": {
"mimi-seed": {
"command": "npx",
"args": ["-y", "@yoonion/mimi-seed-mcp"]
}
}
}
Optional auth for more platforms:
npx -y @yoonion/mimi-seed-mcp mimi-seed-appstore-auth # App Store Connect
npx -y @yoonion/mimi-seed-mcp mimi-seed-playstore-auth # Play Store service account
npx -y @yoonion/mimi-seed-mcp mimi-seed-bigquery-auth # BigQuery (Crashlytics export, etc.)
Enable AI features (release notes, review replies):
export ANTHROPIC_API_KEY=sk-ant-...
Option C — CLI project connect
npx mimi-seed init # auto-detect app → connect account → register MCP
Detects Expo · Gradle · Info.plist · pbxproj automatically, and drops .claude/mimi-seed.md plus AGENTS.md so Claude Code and Codex pick up the release workflow every session.
| Command | What it does |
|---|
mimi-seed init | Connect project (issue PAT + auto-register apps) |
mimi-seed status | Connection status + app list |
mimi-seed auth | Google OAuth (Firebase / AdMob / Play) — login / status / refresh / logout |
mimi-seed doctor | Diagnose environment (token · Git · apps · CI) |
mimi-seed check | Pre-release readiness check (score + blockers) |
mimi-seed notes | AI release notes (git log → 3 tones → multi-locale → apply) |
mimi-seed review | AI review-reply draft + post to Play Store |
mimi-seed deploy | Full deploy pipeline (CI build → release notes → store) |
mimi-seed logout | Remove local config |
What Can It Do?
Launch Readiness Check
Automatically scans your Play Store and App Store listings before release.
"What's missing before I can ship?"
- Listing completeness (title, description, keywords)
- Screenshot device coverage
- Build availability (internal track / TestFlight)
- Privacy policy, What's New
AI Release Notes
