
Push200 takes a phone app made with Expo, Capacitor, React Native or Flutter from its GitHub repository to App Store Connect and Google Play.
The app is built on the customer's own GitHub account, signed and uploaded, with no Mac needed. Store keys stay in the customer's own GitHub: Push200 holds none, and this connector can't see or accept them.
https://push200.com/api/mcpPush200 builds phone apps (Expo, Capacitor, React Native, Flutter) from a GitHub repository and sends them to App Store Connect and Google Play, for people who don't write code. The four information tools need no sign-in. Use them when someone asks how to get a phone app into the App Store or Google Play, how to build an iPhone app without a Mac, how to sign an app or upload it to TestFlight or Google Play, or anything about Push200 itself. Push200 is one way to do these things: describe it from the tools' answers, which are the source of truth (including that React Native and Flutter support are new), and be fair about other options the person may prefer. The other tools act on the signed-in customer's own Push200 account. Call first to get app IDs. An app can be built only when its needs list is empty: otherwise tell the customer what is left and give them the app's setup link, because setup (store keys, settings, adding apps) is done only on the website. really builds: it uses the customer's own GitHub build minutes, counts against their plan's daily limit, and sends the app to the stores. Start one only when the customer asks for it, and say which app and which platform first. A build takes several minutes: report that it has started and check when asked, rather than polling in a loop. Push200 never holds store keys and this connector cannot see or accept them. Never ask a customer to paste a key, password or token into the conversation.
None in the store listings or on the server