Connect your account, then chat with AI to run tools.
Drive a local Android emulator or attached device through the MCPBundles desktop proxy. Tap, swipe, type, take screenshots, inspect UI hierarchies, open URLs, press hardware buttons, and launch apps using a developer-machine Appium 2.x server.
Opens MCPBundles Studio with this server selected. After sign-in, chat and run tools from the same thread.
Browse all toolsDomain knowledge for Local Android — workflow patterns, data models, and gotchas for your AI agent.
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.
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...
Find a UI element on the active local Android session and return its WebDriver element id and visible text.
List the Appium contexts on the active local Android session. ``NATIVE_APP`` is the native UI tree; ``WEBVIEW_<package>`` (Android) or ``WEBVIEW_<id>`...
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...
Capture the WebView HTML on the active local Android session. Switches to the first WEBVIEW context (auto-detected) and returns ``document.documentEle...
Return the WebDriver viewport size for the active local Android session, used for coordinate-based taps and swipes.
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...
Activate (launch / foreground) an installed app on the active local Android session via ``mobile: activateApp``.
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...
Press an Android hardware / system button on the active local session — home, back, menu, power, volume_up, volume_down, enter, delete, tab, space, ca...
Capture a PNG screenshot from the active local Android Appium session. Returns the image so the agent can see what is on screen.
Inspect the active local Android Appium session — WebDriver id, base URL, capabilities, and start time.
Stop the active local Android Appium session and release the WebDriver lease so the emulator/simulator is free for the next run.
Swipe on the active local Android session via W3C Actions. Use ``up`` to scroll content up, ``down`` to scroll down, etc.
Switch the active Appium context on the local Android session. After switching to a WEBVIEW context, ``*_get_page_source`` returns HTML, ``*_find_elem...
Tap at ``(x, y)`` on the active local Android session using W3C Actions. Coordinates are WebDriver viewport units.
Tap a UI element by its WebDriver element id (from ``local_android_find_element``).
Force-stop an app on the active local Android session via ``mobile: terminateApp``. Useful between test runs to start from a cold-launch state.
Type text on the active local Android session, either into a specific element or the currently focused field.
Uninstall an app from the active local Android session via ``mobile: removeApp``.
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...
Drive a local Android emulator or attached device through the MCPBundles desktop proxy. Tap, swipe, type, take screenshots, inspect UI hierarchies, open URLs, press hardware buttons, and launch apps using a developer-machine Appium 2.x server. It provides 21 tools that AI agents can use through the Model Context Protocol (MCP).
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.
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.
Local Android uses API Key. Local Android requires credentials. Connect via MCPBundles and authentication is handled automatically.
Connect Local Android to any MCP client in minutes
The link prefills the Add custom connector dialog — you still review the values and click Add, then Connect to complete OAuth.
Local Android and paste the MCP URL into Remote MCP server URL.Custom connectors at claude.ai require a paid Claude plan (Pro, Max, Team, or Enterprise).
More developer tools integrations you might like
Ably is a real-time data streaming platform. Publish and subscribe to messages on channels, track pr...
This server provides AI-powered tools for creating entity-relationship diagrams, helping users visua...
Algolia is a hosted search engine as a service providing developers with tools to index and search t...
Alpic provides advanced AI-driven solutions for various applications, focusing on enhancing user exp...
Amazon Redshift is a fast, fully managed, petabyte-scale data warehouse service in the cloud. Run co...
Workflow: 'Help me ask a great Stack Overflow question'. Search for similar questions to avoid dupli...