create_android_boxLABSCO SUMMARY
A test device that appears when you need one.
The loop it closes is build, install, drive, screenshot — with the driving done from natural-language instructions instead of selectors that break when the layout moves. Devices live on Gbox, so nothing has to be plugged in or emulated locally.
What it is
An MCP server for Android automation built on the Gbox SDK, creating Android boxes and driving apps on them from an MCP client.
What you get
- Android boxes created — virtual or physical devices — with the configuration you specify
- Every box under your API key listed, and any one of them inspected in detail
- Screenshots taken of the current display
- UI actions performed from natural-language instructions rather than element selectors
- APKs installed from a local path or a URL, apps uninstalled by package name, and installed apps launched
Requirements
A Gbox API key in GBOX_API_KEY, and Node with npm for the build. Devices run on Gbox rather than on your machine.
Setup effort
Build from source — git clone https://github.com/zhenweiwang1990/android-tester-mcp.git
USE CASES
01
Testing the APK you just built
Create a box, install the APK from your local path, launch it, and drive it through the flow.
02
Seeing what the app actually looks like right now
Take a screenshot of the current display instead of describing the state from logs.
03
Walking a user journey without writing selectors
Give the instruction in plain language and let it locate the control, so the test survives a layout change.
04
Keeping track of the devices you have running
List every box under your key and inspect the one you are using.
05
Starting from a clean install
Uninstall by package name, then install the new build so nothing carries over from the last run.
8 tools
Listed in project docs. Your client may show a different list.
list_boxesget_boxget_screenshotai_actioninstall_apkuninstall_apkopen_appBEFORE YOU INSTALL
What to know first
Tools you get
8 tools named in the project's documentation.
Requires
- node on PATH
- GBOX_API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/zhenweiwang1990/android-tester-mcp.git
cd android-tester-mcp
npm install
npm run buildMCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"gbox-android": {
"command": "node",
"args": [
"<YOUR_PATH_TO_THIS_REPO>/android-tester-mcp/dist/index.js"
],
"env": {
"GBOX_API_KEY": "<YOUR_GBOX_API_KEY>"
}
}
}
}<YOUR_PATH_TO_THIS_REPO> is the folder you cloned into, so the path ends at the android-tester-mcp/dist/index.js the build produced.
