Local Android MCP Server

Connect your account, then chat with AI to run tools.

Automate an Android emulator or USB device from Claude Code or Cursor — tap, swipe, type, screenshot, and launch apps through Appium over Desktop.

Best forAndroid DevelopersMobile QAEmulator TestingAgent Workflows

Try this workflow

Walk through an app build

Start a session on the emulator, launch the staging APK, complete login, and screenshot each step.

Start chatting

Managed

21 tools

Agent guide included

Opens MCPBundles Studio with this server selected. After sign-in, chat and run tools from the same thread.

Browse all tools

What you can do with Local Android

Built for

Android Developers, Mobile QA, Emulator Testing, Agent Workflows

Example workflows

Walk through an app build

Uses local Appium for fast in-loop Android QA.

Try this

Start a session on the emulator, launch the staging APK, complete login, and screenshot each step.

Test a mobile web page

Covers mobile web on a local Android session.

Try this

Open this URL in Chrome on the emulator, wait for load, and summarize layout issues at phone width.

Find and tap a control

Combines element find, tap, and screenshot.

Try this

Locate the checkout button on the current screen, tap it, and report what renders next.

Debug a stuck screen

Uses screenshot and hierarchy for mobile debugging.

Try this

Capture a screenshot and page source of the current view, then list tappable elements visible on screen.

Context to know first

What is Local Android best for?

It is best when you run an Android emulator or attached device locally and want your agent to drive it without cloud device farms.

Do I need MCPBundles Desktop?

Yes. Desktop bridges your agent to the Appium server on localhost. Install it on the machine where the emulator runs and keep Appium listening on port 4723.

How is Local Android different from Mobile Device?

Local Android drives an emulator or USB device on your machine through Desktop. Mobile Device provisions real phones and tablets in AWS Device Farm.

AI Skill
SKILL.md

Domain knowledge for Local Android — workflow patterns, data models, and gotchas for your AI agent.

Local Android

Automate a developer-machine Android emulator (or USB-attached device) via Appium UiAutomator2. The MCPBundles desktop proxy forwards backend traffic to 127.0.0.1:4723, so you can drive the emulator without exposing Appium publicly.

Data Model

Session — one Appium WebDriver session per user.
Elements — locate via accessibility id / xpath / class name; tap or type by element id.
Gestures — coordinate-based tap, swipe, and Android key codes for hardware buttons.
Navigation — Android VIEW intent for arbitrary URLs.

Gotchas

Boot the emulator BEFORE opening an Appium session.
Coordinates are WebDriver viewport units. Read viewport size first when sizing a coordinate tap.

Tools in this Server (21)

Local Android Create Session

Start a local Appium Android session through the MCPBundles desktop proxy. Requires a booted emulator and a running local Appium 2.x server. Returns t...

Local Android Find Element

Find a UI element on the active local Android session and return its WebDriver element id and visible text.

Local Android Get Contexts

List the Appium contexts on the active local Android session. ``NATIVE_APP`` is the native UI tree; ``WEBVIEW_<package>`` (Android) or ``WEBVIEW_<id>`...

Local Android Get Page Source

Return the current UI hierarchy from the active local Android session (XML for native apps, HTML for browser sessions). Use this before tapping or typ...

Local Android Get WebView HTML

Capture the WebView HTML on the active local Android session. Switches to the first WEBVIEW context (auto-detected) and returns ``document.documentEle...

Local Android Get Window Size

Return the WebDriver viewport size for the active local Android session, used for coordinate-based taps and swipes.

Local Android Install App

Install an app on the active local Android session via ``mobile: installApp``. The path is resolved on the developer machine running Appium, not the b...

Local Android Launch App

Activate (launch / foreground) an installed app on the active local Android session via ``mobile: activateApp``.

Local Android Navigate URL

Open a URL on the active local Android session. Android uses an Android VIEW intent through the active Appium session; iOS uses the Safari WebDriver s...

Local Android Press Button

Press an Android hardware / system button on the active local session — home, back, menu, power, volume_up, volume_down, enter, delete, tab, space, ca...

Local Android Screenshot

Capture a PNG screenshot from the active local Android Appium session. Returns the image so the agent can see what is on screen.

Local Android Session Info

Inspect the active local Android Appium session — WebDriver id, base URL, capabilities, and start time.

Local Android Stop Session

Stop the active local Android Appium session and release the WebDriver lease so the emulator/simulator is free for the next run.

Local Android Swipe

Swipe on the active local Android session via W3C Actions. Use ``up`` to scroll content up, ``down`` to scroll down, etc.

Local Android Switch Context

Switch the active Appium context on the local Android session. After switching to a WEBVIEW context, ``*_get_page_source`` returns HTML, ``*_find_elem...

Local Android Tap

Tap at ``(x, y)`` on the active local Android session using W3C Actions. Coordinates are WebDriver viewport units.

Local Android Tap Element

Tap a UI element by its WebDriver element id from a prior element find on this session.

Local Android Terminate App

Force-stop an app on the active local Android session via ``mobile: terminateApp``. Useful between test runs to start from a cold-launch state.

Local Android Type Text

Type text on the active local Android session, either into a specific element or the currently focused field.

Local Android Uninstall App

Uninstall an app from the active local Android session via ``mobile: removeApp``.

Local Android Wait For Element

Poll for a UI element on the active local Android session until it is found or the timeout elapses. Returns the WebDriver element id and its text once...

Frequently Asked Questions

What is Local Android best for?

It is best when you run an Android emulator or attached device locally and want your agent to drive it without cloud device farms.

Do I need MCPBundles Desktop?

Yes. Desktop bridges your agent to the Appium server on localhost. Install it on the machine where the emulator runs and keep Appium listening on port 4723.

How is Local Android different from Mobile Device?

Local Android drives an emulator or USB device on your machine through Desktop. Mobile Device provisions real phones and tablets in AWS Device Farm.

What do I need installed first?

Android SDK with ADB, a booted emulator or USB device with debugging enabled, Appium 2.x with the UiAutomator2 driver, and MCPBundles Desktop.

How do I connect Local Android to my AI agent?

Add the MCPBundles server URL to your MCP client configuration (Claude Desktop, Cursor, VS Code, etc.). The URL format is: https://mcp.mcpbundles.com/bundle/local-android. Authentication is handled automatically.

How many tools does Local Android provide?

Local Android provides 21 tools that can be called by AI agents, along with a SKILL.md that gives your AI agent domain knowledge about when and how to use them.

What authentication does Local Android require?

Local Android uses API Key. Local Android requires credentials. Connect via MCPBundles and authentication is handled automatically.

Setup Instructions

Connect Local Android to any MCP client in minutes

MCP URL

https://mcp.mcpbundles.com/bundle/local-android

Claude.ai Cursor VS Code VS Code Insiders Goose LM Studio Cherry Studio ChatGPT

One-click install:

Install on Claude.ai Install for organization (admins)

The link prefills the Add custom connector dialog — you still review the values and click Add, then Connect to complete OAuth.

Or add manually

Open claude.ai → Settings → Connectors.
Click the + button and choose Add custom connector.
Set Name to Local Android and paste the MCP URL into Remote MCP server URL.
Click Add. Local Android will appear under Not connected — select it and click Connect to complete OAuth.