Skip to main content
Glama

Android Tester MCP

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.

Features

  • Create Android Boxes: Spin up virtual or physical Android devices

  • Screenshot Capture: Take screenshots of the current display

  • AI-Powered Actions: Perform UI actions using natural language instructions

  • App Management: Install, uninstall, and launch Android applications

  • Box Management: List and get information about your Android boxes

Related MCP server: ADB MCP Server

Setup

  1. Install Dependencies

    npm install
  2. Set Environment Variables

    Create a .env file in the project root:

    GBOX_API_KEY=your_gbox_api_key_here
  3. Build the Project

    npm run build

Usage

This is an MCP server that provides tools for Android automation. Once running, you can use the following tools:

Config in Cursor

{
  "mcpServers": {
    "gbox-android": {
      "command": "node",
      "args": ["/YOU_PATH_TO_THIS_REPO/android-tester-mcp/dist/index.js"],
      "env": {
        "GBOX_API_KEY": "YOUR API KEY"
      }
    }
  }
}

Available Tools

  • 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

Requirements

  • Node.js and npm

  • Valid Gbox API key

  • TypeScript (for development)

Sample Prompts in Cursor

Test the apk of this project like a user, just create an android environment on gbox, and install it and test it by instructing the MCP tool ai_action. Keep developing and testing until all requirements are met.

Available Tools

9 tools
ai_actionB

Perform an action on the UI of the android box (natural language instruction).

Inputs: boxId (required), instruction (required), background, includeScreenshot, +2 more.

create_android_boxB

Create a fresh Android box and return its metadata.

Inputs: config, wait.

get_boxB
Read-only

Get box information by ID.

Inputs: boxId (required).

get_screenshotB
Read-only

Take a screenshot of the current display for a given box.

Inputs: boxId (required), outputFormat.

install_apkB

Install an APK file into the Gbox Android box.

Inputs: boxId (required), apk.

list_boxesB
Read-only

List all current boxes belonging to this API Key.

Inputs: deviceType, labels, page, pageSize, +2 more.

open_appA

Launch an installed application by package name on the Android box.

Inputs: boxId (required), packageName (required).

open_live_viewA

Open the live-view URL of the Android box in the default browser.

Inputs: boxId (required).

uninstall_apkA

Uninstall an app from the Android box by package name.

Inputs: boxId (required), packageName (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools have distinct purposes targeting specific resources like boxes, APKs, or UI actions, but 'ai_action' is broad and could overlap with more specific tools like 'open_app' or 'install_apk' if natural language instructions cover those tasks. The descriptions help clarify boundaries, but some ambiguity remains.

    Naming Consistency4/5

    Tools follow a consistent verb_noun pattern (e.g., 'create_android_box', 'get_screenshot', 'install_apk') with minor deviations like 'ai_action' (which uses a prefix instead) and 'list_boxes' (where 'boxes' is plural but aligns with the resource). Overall, the naming is readable and mostly predictable.

    Tool Count5/5

    With 9 tools, the count is well-scoped for managing Android boxes, covering creation, listing, interaction, and app management. Each tool earns its place by addressing a core aspect of the domain without being excessive or sparse.

    Completeness4/5

    The toolset provides good coverage for Android box management, including CRUD-like operations (create/list/get boxes) and app lifecycle (install/uninstall/open). Minor gaps exist, such as no tool for updating box configurations or handling system settings, but agents can work around these with the available tools.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that enables AI assistants to control and interact with Android devices, allowing for device management, app debugging, system analysis, and UI automation through natural language commands.
      8
      452
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      A MCP server that enables AI assistants to control Android devices via ADB, supporting device info, screen control, input simulation, app management, shell execution, file transfer, and UI parsing.
      20
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A powerful MCP server that provides comprehensive Android device automation capabilities through ADB, enabling AI agents to interact with Android devices for testing, automation, and device control tasks.
      1
      -