benchfleet-mcp
Allows AI agents to safely interact with real Android phones through BenchFleet, including listing devices, viewing screens, reading UI elements, tapping, typing, launching apps, running workflows, taking screenshots, and managing device tasks with permission controls and audit logging.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
benchfleet-mcp
Let AI agents use your real Android phones, safely. benchfleet-mcp connects Claude Code, Codex, Cursor, Claude
Desktop and any other MCP client to BenchFleet, the
self-hosted control hub for real Android phones. The agent can list your phones, look at their screens, read the
elements on them, tap, type, open apps and run your published workflows — only on the phones and with the actions
you allow, with approvals for anything sensitive and every step in BenchFleet's audit log.
It is a thin connector: it forwards MCP messages to the BenchFleet app running on the same computer and reaches nothing else. The tools, the permissions and the phones are all in the app.
Set up
Install BenchFleet from https://benchfleet.com/download and connect your phones (or use its demo phones).
In BenchFleet: Settings → AI clients → Connect an AI client…, choose what the client may do (Look only, Look and operate, or chosen capabilities) and on which phones, and copy the token it shows once.
Add the server to your client:
Claude Code
claude mcp add benchfleet --env BENCHFLEET_TOKEN=<token> -- npx -y benchfleet-mcpCodex (
~/.codex/config.toml)[mcp_servers.benchfleet] command = "npx" args = ["-y", "benchfleet-mcp"] env = { BENCHFLEET_TOKEN = "<token>" }Claude Desktop, Cursor and other clients (
mcpServers){ "mcpServers": { "benchfleet": { "command": "npx", "args": ["-y", "benchfleet-mcp"], "env": { "BENCHFLEET_TOKEN": "<token>" } } } }
The app must be running. Disconnect in BenchFleet stops the token at once.
Related MCP server: Karagöz
Tools
list_devices, get_device, get_screen, get_ui_tree, find_element, read_text, wait_for, tap_element,
long_press_element, type_text, type_secret (a password from BenchFleet's vault, never its value), swipe,
scroll_to, press_key, launch_app, stop_app, take_screenshot, get_device_logs, list_workflows,
run_workflow, queue_task (a workflow, or a goal in plain words for the phones' AI agents), get_task_status,
pause_device, resume_device, request_manual_control. A client sees only the tools its access allows. There is
no shell, file transfer or install tool. A phone a person is controlling, a paused phone and a phone without
Automation allowed refuse every action; CAPTCHAs and other human-only checks stop the agent and ask a person.
Settings
Variable | Meaning |
| Required: the client's token from the app ( |
| Optional: the app's address, when it is not found in its data folder |
| Optional: the app's data folder, when it is not the default one |
Plans: AI clients need BenchFleet Pro or Team (https://benchfleet.com/pricing); the personal edition has no limits. Support: support@benchfleet.com.
Use it in Claude Code as a plugin
/plugin marketplace add benchfleet/benchfleet-mcp
/plugin install benchfleet@benchfleet-pluginsSet BENCHFLEET_TOKEN in your environment first (the token from BenchFleet: Settings → AI clients).
Use it in Gemini CLI
gemini extensions install https://github.com/benchfleet/benchfleet-mcpRelated MCP Connectors
Give your AI agent a real cloud Android phone: push APKs, drive it, get screenshots and logs.
Let AI agents control Android and iOS devices on Mobilerun Cloud: screen, input, apps, workflows.
Cloud Android phones for AI agents: create a phone, read the screen, tap, type, install APKs, park.
Cloud Android phones for AI agents: read the screen, tap, type, install APKs, park and resume.
Related MCP Servers
- FlicenseNot gradedqualityBmaintenanceEnables an agent to control a real Android phone by reading structured UI elements and performing actions such as tapping, swiping, typing, and extracting fields from known app screens.1-
- AlicenseBqualityBmaintenanceEnables AI agents to automate Android and iOS devices, including emulators and physical devices, by capturing screenshots, reading UI accessibility trees, performing touch and text input, and managing app lifecycle and logs.184MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to visually perceive and directly control Android devices via ADB and screen-control tooling, including screenshots, taps, swipes, typing, app management, UI inspection, file transfer, shell commands, and audio/video streaming.365 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to remotely control a real Android phone over MCP with no ADB, root, or emulator, by connecting a broker server to a sideloaded APK. Exposes tools to list devices, capture screenshots, read the UI tree, open links and deep links, and perform taps, swipes, typing, and global navigation actions.1MIT