MCP server exposing Gbox Android control tools via Model Context Protocol
Android Tester MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Android Tester MCP directly instead of describing what you should do. MCP server exposing Gbox Android control tools via Model Context Protocol.
A Model Context Protocol (MCP) plugin for automating Android devices using the Gbox SDK. This plugin provides tools for creating Android boxes, taking screenshots, performing AI-powered UI actions, and managing applications.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Once Android Tester MCP is connected, these are the calls the assistant has available:
create_android_box — Create a new Android box with specified configurationlist_boxes — List all current boxes belonging to your API keyget_box — Get detailed information about a specific boxget_screenshot — Take a screenshot of the Android deviceai_action — Perform UI actions using natural language (e.g., "click the login button")install_apk — Install an APK file from local path or URLuninstall_apk — Uninstall an app by package nameopen_app — Launch an installed applicationYou will need one environment variable: GBOX_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Android Tester MCP's toolset — create_android_box, list_boxes, get_box and 5 more — is a fair guide to whether it matches your workflow. It is maintained by zhenweiwang1990; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| create_android_box | Create a new Android box with specified configuration |
| list_boxes | List all current boxes belonging to your API key |
| get_box | Get detailed information about a specific box |
| get_screenshot | Take a screenshot of the Android device |
| ai_action | Perform UI actions using natural language (e.g., "click the login button") |
| install_apk | Install an APK file from local path or URL |
| uninstall_apk | Uninstall an app by package name |
| open_app | Launch an installed application |
{
"mcpServers": {
"gbox-android": {
"command": "node",
"args": ["/YOU_PATH_TO_THIS_REPO/android-tester-mcp/dist/index.js"],
"env": {
"GBOX_API_KEY": "YOUR API KEY"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| GBOX_API_KEY | Credential the server authenticates with. | Yes |
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.