Automate Google Play closed testing with AI agents

Updated November 2026

If you already ship code with an AI agent, you can hand it most of the busywork of Google Play's closed testing requirement too: listing your app, recruiting testers, checking progress and pulling numbers for the production access form. Tester Exchange has an MCP server, a one-endpoint HTTP API and an A2A agent card for this. This guide shows how to connect Claude Code, Claude Desktop, Cursor and other clients, what to ask, and the parts no agent can do for you.

Real people open your app on their own phones for 14 days. Pay once, or test other apps for free.Get 12 testers

What an agent can and can't do

Google requires personal developer accounts created after 13 November 2023 to run a closed test with at least 12 testers opted in for 14 continuous days before applying for production. Most of the work around that is coordination, which agents handle well.

An agent can: add your app, open a tester campaign, apply your credits, check how many testers are active, pause or close a campaign, fetch the daily-activity report and help draft production access answers from it.
A human must: add the testers' Google Group to the closed track in Play Console, publish the release, pay for credits (checkout always happens in a person's browser) and click Apply for production.
Nobody can automate: the 14 days of real use. That is done by real people on their own Android phones, which is the whole point of Google's rule.

1. Create a token

Sign in at https://testerexchange.com/api.
Create a personal token. It starts with tx_. Copy it now and store it like a password.
Tokens can be revoked at any time. A token can spend credits on campaigns, but it can't pay, withdraw money or delete your account.

2. Connect the MCP server

The MCP server uses Streamable HTTP at https://vvrlxzbngxfxddywidoq.supabase.co/functions/v1/mcp. Send your token in the header Authorization: Bearer tx_YOUR_TOKEN.

Claude Code: run this once in your terminal.

claude mcp add --transport http tester-exchange https://vvrlxzbngxfxddywidoq.supabase.co/functions/v1/mcp --header "Authorization: Bearer tx_YOUR_TOKEN"

Claude Desktop, Cursor, VS Code and other clients with a JSON config: add a server named tester-exchange with type http, the URL above, and a headers entry with Authorization set to Bearer tx_YOUR_TOKEN. The exact config file location depends on your client; check its MCP documentation.

Clients that only take a URL (some ChatGPT and web connectors): the docs at https://testerexchange.com/agents/ list a URL form for them. Without a token, the public tools (what Tester Exchange is, pricing, platform stats) still work.

3. The one tool to start with: get_testers

You don't need to learn the whole tool list. The main tool is get_testers(package_name, name?). One call adds your app, opens its test, applies your credits and returns your progress plus the steps only a human can do, such as adding the Google Group in Play Console. Call it again any time to check progress.

Other tools cover the details: my_apps, campaign_report (testers, daily activity, feedback and production-access data), add_testers, set_campaign_status (pause, resume or close; unused credits go back to your balance), share_kit and buy_credits_links, which returns checkout links for a human to pay.

Prompts that work

"Get 15 testers for com.example.app and tell me what I need to do in Play Console."
"Check my Tester Exchange campaign for com.example.app. How many testers were active each day this week?"
"Pull the campaign report and draft my production access answers. Use only the real numbers."
"Close the campaign for com.example.app now that production access is approved."

Ask for 15 testers rather than 12, so a dropout can't take you under Google's minimum.

HTTP API for scripts and CI

If your tool doesn't speak MCP, use the HTTP endpoint: POST https://vvrlxzbngxfxddywidoq.supabase.co/rest/v1/rpc/agent_call. The body is JSON with p_token (your tx_ token), p_action (for example help, my_apps or start_campaign) and p_args (for example a package_name and a tester count). Send the public apikey header shown in the docs.

Call the help action first: it returns every action and its arguments. The full schema is at https://testerexchange.com/openapi.json, which works with ChatGPT custom GPT actions and other OpenAPI tools.

A2A agent card

For agent-to-agent setups, Tester Exchange publishes an A2A agent card at https://testerexchange.com/.well-known/agent-card.json. Orchestrators that support the A2A protocol can discover what the agent offers and how to call it. Use the same tx_ token for anything tied to your account.

A full run, start to finish

You upload your first .aab to the closed track in Play Console.
Your agent calls get_testers for your package name and tells you to add testerexchange-testers@googlegroups.com under Google Groups on the closed track.
You add the group, save, and make sure the release is published.
If you lack credits, the agent gives you a checkout link. You pay ($12.99 for 12 testers, $14.99 for 15, $22.99 for 25) or earn credits free by testing other apps at https://testerexchange.com/earn.
Real testers install and use your app for 14 days. Your agent checks progress daily and warns you if active testers fall.
On day 15, the agent pulls the campaign report and drafts your production access answers. You review them and click Apply for production.

Safety notes

Keep tokens out of git. Put them in your client's secret store or an environment variable.
Tokens are stored only as hashes on our side and are limited to 10 per account. Revoke any token you no longer use.
Read what the agent writes in your production form before you submit. Google asks you to describe your test truthfully.

Frequently asked questions

Can an AI agent complete the 14-day test for me?

No. The 14 days need real people using your app on their own phones. Agents handle setup, monitoring and reporting.

Can the agent pay for testers?

No. It can return checkout links, but payment always happens in a human's browser.

Which clients work with the MCP server?

Any client that supports remote MCP over Streamable HTTP with a custom header, including Claude Code, Claude Desktop, Cursor and VS Code. Others can use the HTTP API.

Where do I get a token?

At https://testerexchange.com/api after signing in. Tokens start with tx_ and can be revoked at any time.

Does the agent change anything in my Play Console?

No. It has no access to your Play Console. It tells you the steps to do there.