Get your 12 Google Play testers from your AI coding tool
Updated November 2026
Whether you vibe-coded your Android app or wrote it by hand with an AI editor, Google Play still wants 12 testers opted in for 14 days before a new personal developer account can publish to production. This hub lists a Tester Exchange guide for each AI tool: how to produce the Android App Bundle, how to start closed testing, and how to get the testers, free by testing other apps first, or paid and faster. Each page also shows the exact copy-paste setup so your AI tool can drive Tester Exchange itself.
Guides by tool
More tools are added regularly. Today:
- Cursor: https://testerexchange.com/guide/get-12-testers-cursor/ - build the AAB with Gradle, then connect Tester Exchange to Cursor with .cursor/mcp.json.
- Claude Code: https://testerexchange.com/guide/get-12-testers-claude-code/ - build the AAB with Gradle, then add Tester Exchange with one claude mcp add command.
- Windsurf: https://testerexchange.com/guide/get-12-testers-windsurf/ - build the AAB with Gradle, then add Tester Exchange to ~/.codeium/windsurf/mcp_config.json.
- VS Code + Copilot: https://testerexchange.com/guide/get-12-testers-vscode-copilot/ - build the AAB with Gradle, then add Tester Exchange to .vscode/mcp.json.
The two routes to testers
- Free: test other developers' apps at https://testerexchange.com/earn on your phone. Each app you test brings one tester to your app, so you can fill your 12 seats without paying.
- Paid and faster: pay once for a pack of testers; current prices are on https://testerexchange.com/llms.txt. Paid apps get testers before anyone else.
What Google requires
Google's Play Console Help says personal developer accounts created after 13 November 2023 must run a closed test with at least 12 testers opted in continuously for at least 14 days before they can apply for production access (https://support.google.com/googleplay/android-developer/answer/14151465). No AI tool can do those 14 days for you: they must be real people on real phones.
Let your AI tool do the setup
Tester Exchange has an MCP server, an HTTP API and an A2A agent. The full list of clients and config snippets is at https://testerexchange.com/agents/. The general guide is https://testerexchange.com/guide/automate-closed-testing-with-ai-agents/.
Frequently asked questions
Do I need an AI tool to use Tester Exchange?
No. The website works on its own. The MCP server and API are optional shortcuts for people who already work with an AI tool.
Can the AI tool pay for testers?
No. It can return a checkout link, but payment happens in your browser. The free route is testing other apps at https://testerexchange.com/earn.
Is Tester Exchange an official integration of these tools?
No. It is an independent service. These pages only show how to connect a tool's standard MCP or HTTP support to Tester Exchange.