Uprate vs Expo MCP
Expo MCP connects your coding agent to an Expo project and to Expo's build, submit and crash tools, and it can read and answer store reviews. Uprate is a hosted MCP server and workspace for the store work after the build, on both stores, whatever your app is built with.
Choose Uprate if
- You want every review on both stores in one queue, with drafts in your tone and auto-replies.
- You want listing copy, screenshots and a check against App Review rules before you submit.
- You want the same store work whatever your app is built with, Expo included.
Choose Expo MCP if
- You build with Expo and want your agent to run builds, read crash reports and send builds to the stores.
- You want builds and over-the-air updates on one account with unlimited members.
- You answer a review now and then and are happy to write the reply with your own agent.
Three differences that matter
| What | Uprate | Expo MCP |
|---|---|---|
| Reply drafts in the reviewer's language | Drafted as reviews arrive once auto-draft is on, in your tone, learned from your past replies | Your own agent writes the reply; Expo shows it before posting |
| Build from source | Bring a build from App Store Connect or Google Play, or upload your IPA or AAB | Your agent starts an Expo build once a GitHub repository is connected; 15 iOS and 15 Android builds on Free |
| Entry plan | Indie $29 a month: 2 apps, 500 credits | Starter $19 a month plus usage: $45 of build credit |
Uprate reply drafts use AI credits and pause when your allowance runs out. Publishing and price checks start on Indie at $29 a month.
- Included
- Partly, or with limits
- Not included
- Not described on their public pages
Compare every feature
Open a category for features, plan limits and store differences.
MCP and agents
| What | Uprate | Expo MCP |
|---|---|---|
| Hosted MCP server | One URL for App Store Connect and Google Play, sign-in with OAuth | mcp.expo.dev with OAuth; a local part for SDK 54 and later runs on macOS |
| Tools | 28 tools for reviews, listings, releases, approvals and files, plus other Uprate actions | Docs, builds, workflows, submissions, crashes, cloud simulators and store reviews |
| Clients | Setup steps for Claude Code, Claude Desktop, Cursor, Codex and VS Code | Claude, Claude Code, Cursor, VS Code and Codex |
| Apps it works with | Any app on App Store Connect or Google Play, whatever it is built with | Expo projects; local tools need SDK 54 or later |
| Apps per connection | Every app, or only the apps you pick at sign-in | Not described on their public pages |
| Approval before store changes | Replies, live listing copy and submissions wait for you; you can let one connection approve up to 5, 20 or 100 a day | Review replies are previewed before they post; confirmation for builds and submissions is not described |
| Revoke access | Disconnect in Settings > MCP works right away; a connection lasts 30 days | Access tokens can be deleted in the dashboard; revoking the MCP connection is not described |
Reviews and replies
| What | Uprate | Expo MCP |
|---|---|---|
| One inbox for both stores | Both stores in one queue, sorted by what needs you first | Your agent reads App Store and Google Play reviews; no review inbox is described |
| Reply drafts in the reviewer's language | Drafted as reviews arrive once auto-draft is on, in your tone, learned from your past replies | Your own agent writes the reply; Expo shows it before posting |
| Auto-reply rules | Five-star thank-yous can go out on their own; the delay lets you catch one first (Indie and up) | Not described on their public pages |
| Topics and anomaly alerts | Checked daily for spikes in negative reviews and rating drops over the last 7 days; topics weekly on Studio and up | Not described on their public pages |
| Review history | Imported when you connect a store; the whole backlog can be drafted in one pass | Google Play reviews with text from about the last week |
Releases and submissions
| What | Uprate | Expo MCP |
|---|---|---|
| Build from source | Bring a build from App Store Connect or Google Play, or upload your IPA or AAB | Your agent starts an Expo build once a GitHub repository is connected; 15 iOS and 15 Android builds on Free |
| Builds and uploads | A build picked from App Store Connect or Google Play, or your IPA or AAB uploaded, to TestFlight or internal testing | A finished build sent to App Store Connect, TestFlight or Google Play |
| Pre-submission checks | Version, build number, bundle ID, encryption, age rating, category, privacy URL and screenshots checked before you press submit | Expo Metadata looks for common rejection pitfalls before a push; App Store only, in beta, not in MCP |
| App Review guideline check | 26 App Review rules checked against your code and listing, each finding with its evidence | Not described on their public pages |
| Submit for review | Sent to review only when you say so; a first release needs your sign-off | Google Play tracks and staged rollout; App Store review is started by hand in App Store Connect |
| Rejection help | Apple's reason in plain English and a resubmit button | Not described on their public pages |
| Crash reports | Google Play crash and app-not-responding rates, refreshed daily; App Store crashes not included | TestFlight crashes and feedback, Google Play crashes and app-not-responding data |
| Over-the-air updates | Not in Uprate | Expo Update, to 1,000 monthly active users on Free |
Listing and ASO
| What | Uprate | Expo MCP |
|---|---|---|
| Publish to the store | One click: live on Google Play, drafted into App Store Connect (Indie and up) | Expo Metadata pushes App Store details from a config file; in beta, no Google Play, not in MCP |
| Drafted listing copy | New copy per field and language, shown as a diff with the reason | Not described on their public pages |
| Listing check | Weak fields named with the fix, in the editor; 1 a month on Free, 10 on Indie, 50 on Studio | Not described on their public pages |
| Screenshots and icon | Sets generated and localized, pushed to Google Play (Indie and up) | Expo Metadata does not upload screenshots |
| Keyword rank tracking | Your rank read once a day from Apple's own search results | Not described on their public pages |
Plans and pricing
| What | Uprate | Expo MCP |
|---|---|---|
| Free plan | 1 app, 100 credits a month | $0: 15 iOS and 15 Android builds, MCP within fair use |
| Entry plan | Indie $29 a month: 2 apps, 500 credits | Starter $19 a month plus usage: $45 of build credit |
| Team plan | Studio $79 a month: 5 apps, 5 members, Slack and Teams | Production $199 a month plus usage: $225 of build credit, single sign-on |
| Users | 1 seat until Studio, then 5; unlimited on Enterprise | Unlimited members on every plan |
| MCP on every plan | On every plan, Free included; AI work such as reply drafts uses credits | Free within a fair use limit; MCP requests fail until the next billing cycle once it is reached |
| Pricing intelligence | Every market's price on one screen with outliers flagged; nothing changes without you (Indie and up) | Not described on their public pages |
How we checked
The Expo MCP column comes from Expo's public pages linked above, read on the verification date: the MCP docs for tools, sign-in and confirmations, the pricing page for plans, and the Submit and Metadata docs for what Expo does outside MCP. Older Expo posts say MCP needs a paid plan; we follow the current docs and pricing page, which include it on Free within fair use. Expo notes that its list of tools may not be up to date. The Uprate column comes from the product as it ships today. If something on the Expo side has changed or reads unfairly, email [email protected] and we will correct it.
Try it on one app
Connect one app and see the difference yourself.
The Free plan covers one app, reply drafts and submission checks. Nothing goes live until you approve it.