Mimi Seed SDK

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

Three steps: 1 Install → 2 Connect → 3 Verify. This page is the short version — for the complete account setup → CI build → release check → store deploy → social announcement journey, follow the Mimi Seed User Guide.

Three things that trip every first install:

1. The local MCP server requires Node 20+.
2. Open a new session after installing an MCP server or plugin (and after package updates) — tools only appear in fresh sessions.
3. In Claude Code the 150+ tool schemas load lazily; if a first call fails with InputValidationError, tell Claude: "load the mimi-seed tools with ToolSearch first" (agent guide).

More → troubleshooting.

1 · Install — pick where Mimi Seed runs

Pick by what you want to do (they can also be installed side by side):

Local MCP — recommended (store-write automation · Google OAuth · runs on your machine, Node 20+)

Claude Code — plugin install (recommended): bundles the MCP server plus the skills that auto-handle deferred tool loading (trap #3) and auth recovery. One fresh session after install is still needed (trap #2):

/plugin marketplace add jeonghwanko/mimi-seed-sdk
/plugin install mimi-seed@yoonion

Codex — plugin install (recommended): installs the Codex marketplace plus the same skill bundle.

codex plugin marketplace add jeonghwanko/mimi-seed-sdk
codex plugin add mimi-seed@yoonion

Or register the bare MCP server without skills:

# Claude Code
claude mcp add mimi-seed-local -- npx -y @yoonion/mimi-seed-mcp

Codex (~/.codex/config.toml; plugin install registers this automatically):

[mcp_servers.mimi-seed-local]
command = "npx"
args = ["-y", "@yoonion/mimi-seed-mcp"]
enabled = true

Claude Desktop (claude_desktop_config.json):

{
  "mcpServers": {
    "mimi-seed-local": {
      "command": "npx",
      "args": ["-y", "@yoonion/mimi-seed-mcp"]
    }
  }
}

Remote MCP (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
# The config references MIMI_SEED_TOKEN instead of storing the PAT.
# Set it in the environment that launches Codex, then restart Codex.
export MIMI_SEED_TOKEN="<PAT>"        # bash/zsh
# PowerShell: $env:MIMI_SEED_TOKEN="<PAT>"

What the Remote MCP can and can't do. It exposes a read & diagnostic subset (readiness, blockers, drafts, checklist, publish screenshots) plus workspace-shared BigQuery and App Store IAP review-note/review-screenshot writes. Broader store writes — release-note apply, listing screenshots, Firebase / AdMob / IAM — need the Local MCP (full tool catalog).

2 · Connect your project and accounts

cd <your-app>
npx mimi-seed init    # project: auto-detect app → browser sign-in → register apps → agent context files
npx mimi-seed setup   # accounts: one guided wizard for stores · CI · social

init 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. (Skipped the plugin and registered the bare MCP server instead? npx mimi-seed init --local chains the Google sign-in and the local-MCP registration into the same pass.)

You don't need every account on day one — most people need two or three. One Google sign-in covers Firebase, AdMob, Play, Google Ads, Search Console, GA4, IAM, and BigQuery; the same wizard also connects App Store Connect, a Play service account, Jenkins, GitHub/GitLab CI, and Facebook / Instagram / Threads whenever you need them → What do you actually need?

On first run setup asks for your language (Korean by default, English available), then shows what's connected, asks only about what isn't, and skips anything you've already done (so you can quit and resume). At each step press ? to see exactly where to get that token — the full reference is docs/credentials.md. Reconnect the three Meta platforms any time with npx mimi-seed auth meta; switch language with mimi-seed lang en / mimi-seed lang ko (or MIMI_SEED_LANG=en for one command).

Using the bare MCP server without the CLI? The Google sign-in alone is:

# First-time auth (opens browser)
npx -y @yoonion/mimi-seed-mcp mimi-seed-auth

⚠️ Google says "access_denied" / "unverified app"? The OAuth app is in testing mode — only registered test users can sign in, and retrying will never work until you're added. Full recovery → troubleshooting.

3 · Verify, then ask your agent

npx mimi-seed doctor   # every credential + the exact fix command for anything missing

Open a new Claude Code / Codex session (trap #2 above) and ask:

"Is my app ready to ship?" — plugin installs can also run /mimi-seed:getting-started for a guided first tour. (The slash prefix follows your server name — a bare registration exposes it as /mimi-seed-local:getting-started; the Remote MCP has no prompts.)

CLI quick reference

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

git commits → user-friendly release notes → push to stores.

"Write release notes from commits since v2.1.0 in Korean and English, then apply to Play Store"

• 3 tones: concise / detailed / marketing
• Multiple locales in one shot (ko · en-US · ja · zh-TW …)
• Generate → review → apply in one flow

AI Review Replies

"Reply to this 2-star review with a professional tone"

Tones: friendly · professional · empathetic · brief
Post directly with playstore_reply_review after review.

AI-generated replies are drafts. Always review before posting.

Screenshot Spec Validation

Validate local files against store requirements before uploading.

"Do these screenshots meet the iPhone 6.9-inch spec?"

iOS: APP_IPHONE_69 · APP_IPHONE_67 · APP_IPAD_PRO_3GEN_129
Android: phoneScreenshots · sevenInchScreenshots · featureGraphic

Firebase & AdMob Automation

"Add Android and iOS apps to my-app project and download both config files"
"Create a banner ad unit"
"What's today's AdMob revenue?"

Service Account End-to-End

Need a service account JSON for Play Store receipt verification on your server?

"Create a play-verifier service account in my-project and issue a JSON key"

Creates IAM account → issues key → walks you through Play Console permissions.

One-Command Deploy

Drive the whole release from one command: CI build → blocker check → release notes → store apply.

npx mimi-seed deploy                          # Android, auto-detect CI
npx mimi-seed deploy --platform ios           # iOS
npx mimi-seed deploy --skip-build --version-code 142   # notes-only apply

Works with Jenkins · GitHub Actions · GitLab CI (auto-detected, or force with --ci).

Team-Shared BigQuery (Remote MCP)

Give a whole team read-only BigQuery access (GA4 export analysis, etc.) with one shared service account — no per-machine key files, and immune to the Google Workspace OAuth reauth policy (invalid_rapt) that breaks personal tokens.

A workspace owner/admin registers the service account once (encrypted, workspace-scoped):

"Register a BigQuery service account for the workspace"
→ register_integration(provider="bigquery", key="serviceAccountJson", value=<SA key JSON>)
→ register_integration(provider="bigquery", key="projectId",          value="my-gcp-project")

Then every workspace member (invite them at /workspace/members, they issue a PAT at /workspace/api-tokens) connects the Remote MCP and queries with no local key:

claude mcp add --transport http mimi-seed https://mimi-seed.pryzm.gg/api/mcp \
  --header "Authorization: Bearer <PAT>"

"List BigQuery datasets"                       # bigquery_list_datasets
"Run: SELECT COUNT(*) FROM `proj.ga4.events_*` WHERE ..."   # bigquery_run_query (SELECT/WITH only)

Members can use the SA for read-only queries but cannot read the key back (no tool returns stored secret values), and write statements are blocked. Recommended IAM on the SA: roles/bigquery.jobUser + roles/bigquery.dataViewer.

The Local MCP also has bigquery_* tools, but those authenticate with your own ~/.mimi-seed key/OAuth — the shared SA lives on the Remote endpoint.

Project Manifest — per-teammate setup guidance

Drop a .mimi-seed.json at your repo root declaring the services the project needs. mimi_seed_status (MCP) and mimi-seed doctor (CLI) read it and tell each teammate exactly what they're missing + the precise setup command — instead of a generic scan.

{
  "project": "my-app",
  "socialProfiles": {
    "instagram": "my-app",
    "threads": "my-app"
  },
  "services": {
    "oauth":     { "required": true },
    "bigquery":  { "required": true, "projectId": "my-gcp-project", "dataset": "analytics_123",
                   "workspaceProvider": "bigquery" },
    "playstore": { "required": true, "packageName": "com.example.app" },
    "appstore":  { "required": true, "keyId": "ABC123", "issuerId": "..." },
    "jenkins":   { "required": false, "url": "https://jenkins.example.io" }
  }
}

socialProfiles selects named local credentials from ~/.mimi-seed/social-profiles/<profile>.json. A profile file may hold both instagram and threads credentials, and different projects can map either platform to a different profile. When no mapping is present, the legacy ~/.mimi-seed/instagram.json and threads.json files remain the defaults. Create or refresh a named profile with mimi-seed auth instagram --profile my-app and mimi-seed auth threads --profile my-app.

A teammate who clones the repo just runs mimi-seed doctor (or asks the agent "what am I missing?") and follows the ❌ items. bigquery reports honestly whether a service account or OAuth fallback is present.

Slash Commands (MCP Prompts)

Available in any MCP client (Claude Code, Codex, etc.) as native slash commands:

Plus MCP resources: mimi-seed://auth/status (token state) · mimi-seed://agent/guide (the full agent guide, served over MCP) · mimi-seed://tools/catalog (every tool by domain, with the credential each domain needs).

Skills & Agent Guide

Bundled skills (auto-loaded by the Claude Code / Codex plugin from skills/):

Building an agent on top of Mimi Seed? Read docs/agent-guide.md — how tools load (the deferred-tool / ToolSearch select: pattern), the right call order, auth model, and which actions are irreversible.

Contributing to the SDK? The domain ontology in docs/domain/ maps the architecture, the full tool catalog, the auth/credential model, and known pitfalls — start at docs/domain/_index.md.

Local MCP Tool List (150+ tools · 19 domains)

These run via the Local MCP — Google OAuth on your machine. The Remote MCP exposes a smaller read/diagnostic subset plus App Store IAP review-note/review-screenshot writes. Always-current catalog: docs/domain/tool-catalog.md.

Full catalog → docs/domain/tool-catalog.md · source → packages/mcp-server

CI/CD Integration

Auto-generate and apply release notes on tag push:

- name: Generate and apply release notes
  env:
    MIMI_SEED_TOKEN: ${{ secrets.MIMI_SEED_TOKEN }}
    ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
  run: |
    npx mimi-seed notes --apply --no-interactive --locale ko,en-US
    npx mimi-seed check --fail-on-blocker

Issue MIMI_SEED_TOKEN at Dashboard → API Tokens.

Packages

Web console (Remote MCP): mimi-seed.pryzm.gg/tool

Environment Variables

Legacy Compatibility

Data from the Preseed era (~/.preseed/) is picked up automatically — no re-auth needed.

• Reads ~/.preseed/tokens.json and ~/.preseed/appstore.json if present
• Still honors PRESEED_GOOGLE_CLIENT_ID / PRESEED_GOOGLE_CLIENT_SECRET

New data is written to ~/.mimi-seed/.

License

PolyForm Noncommercial License 1.0.0 — noncommercial use only.

Commercial licensing: [email protected]

Required Notice: Copyright 2026 Pryzm GG (https://mimi-seed.pryzm.gg)