Allows managing iOS app releases and builds on App Store Connect, including listing apps and builds, and initiating release workflows.
Receives EAS Build and EAS Submit webhooks to react to build and submission events and automate release workflows.
Receives GitHub Actions workflow webhooks to react to CI/CD events and trigger automated release processes.
Allows managing Android app releases on Google Play Console, including uploading builds, managing tracks, and releasing to production.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mobile-release-mcp List my App Store apps and the latest build for each one."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Release orchestration MCP for App Store Connect + Google Play
Ask your agent “can I ship?” — get blockers, a plan, and safe dry-runs before touching production.
npm: storepilot-mcp · CLI: storepilot
Golden path · Quick start · Demo · Tools · Compare · Launch post
Not the same as silviosotelo/mobile-release-mcp (Fastlane/build focus).
StorePilot = store operations + release orchestration for AI agents.
Other MCP servers | StorePilot |
90+ low-level tools, agent picks one-by-one | Snapshot → blockers → intent → execute |
No project memory |
|
Writes hit production immediately |
|
Apple or Google depth | Both, plus escape hatch for long tail |
No CI hooks | EAS + GitHub webhooks built in |
~131 typed tools · 91 in release toolset · App Store Connect · Google Play · provenance on npm
Related MCP server: app-publish-mcp
Three steps from zero to “agent knows if you can ship”:
storepilot.yaml to your app repocp path/to/StorePilot/storepilot.example.yaml ./storepilot.yaml
# Edit stores.ios.appId and stores.android.packageproject: my-app
stores:
ios:
appId: "1234567890"
bundleId: com.example.app
android:
package: com.example.app
release:
defaultRollout: 0.1{
"mcpServers": {
"storepilot": {
"command": "npx",
"args": ["-y", "storepilot-mcp@latest"],
"env": {
"APPLE_KEY_ID": "YOUR_KEY_ID",
"APPLE_ISSUER_ID": "YOUR_ISSUER_ID",
"APPLE_PRIVATE_KEY_PATH": "/path/to/AuthKey.p8",
"GOOGLE_SERVICE_ACCOUNT_KEY_PATH": "/path/to/play-service-account.json",
"STOREPILOT_CONFIG_PATH": "/path/to/your-app/storepilot.yaml",
"MCP_TOOLSET": "release"
}
}
}
}"Load my project and explain what's blocking release."
→ load_project / get_release_snapshot / explain_release_blockers
"Plan a 10% production rollout (don't execute yet)."
→ execute_release_intent { intent: "rollout_production", percentage: 10, dryRun: true }
"When ready: promote Android internal → production at 10%."
→ execute_release_intent { intent: "promote_to_production", dryRun: false, confirm: true }CLI (no IDE):
export STOREPILOT_CONFIG_PATH=./storepilot.yaml
# + Apple/Google env vars — see docs/CREDENTIALS.md
storepilot snapshot # blockers + next actions
storepilot projects # multi-app registryFull walkthrough: docs/DEMO.md
npx -y storepilot-mcp@latestCredentials: docs/CREDENTIALS.md — EAS webhooks do not replace App Store / Play API keys.
get_release_snapshot — production vs candidate, cross-platform blockers
explain_release_blockers — human-readable “what to do next”
execute_release_intent — rollout, promote, submit (dry-run default)
list_projects — multi-app registry via STOREPILOT_PROJECTS_DIR
promote_release, configure_rollout, create_tester_group
confirm: true on destructive writes; workflows skip confirm when dryRun is true (default)
Toolsets: MCP_TOOLSET=release | readonly | all
Escape hatch: apple_api_call, google_api_call for long-tail API
Webhooks: EAS Build/Submit + GitHub Actions → list_pending_webhooks
Transports: stdio (Cursor/Claude) or HTTP /mcp
Tests: npm test (42+), npm run smoke (live, needs credentials)
Apple: builds, TestFlight, metadata, screenshots, export compliance, submission preflight
Google: tracks, uploads, subscriptions, internal app sharing, deobfuscation maps
See docs/TOOLS.md · docs/COMPARISON.md
Variable | Description |
| Path to |
| Directory of app repos for |
|
|
| Store API credentials — CREDENTIALS.md |
| Map EAS project → store IDs for webhooks |
| Set |
Full env reference: .env.example
EAS/GitHub → POST /webhook/* → verify → persist
→ list_pending_webhooks
→ get_release_snapshot
→ execute_release_intent (dryRun → confirm)
→ mark_webhook_processedgit clone https://github.com/Jeronimo0228/StorePilot.git
cd StorePilot
npm install
npm test
npm run build
npm run storepilot -- snapshot # from sourceTry it without cloning: npx storepilot-mcp@latest + scripts/try-storepilot.sh
src/
├── core/ Release snapshot, workflows, release-intent
├── tools/ MCP registrations (orchestrator, apple, google, escape)
├── providers/ App Store Connect + Google Play clients
├── plugins/ Plugin hook contract (v1.0)
├── cli.ts storepilot CLI
└── webhook/ EAS + GitHub
docs/ DEMO, TOOLS, COMPARISON, LAUNCH (LinkedIn draft)Early v1 — we want real-world reports: Try StorePilot feedback
MIT — see LICENSE.
This server cannot be installed
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
MCP server for Appcircle mobile CI/CD platform.
MCP server for interacting with the Supabase platform
The MCP server for Azure DevOps, bringing the power of Azure DevOps directly to your agents.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jeronimo0228/StorePilot'
If you have feedback or need assistance with the MCP directory API, please join our Discord server