MCP Vysor Starter

    1

    See an Android screen, tap, swipe, and confirm the UI through the local mcp-vysor server.

    Free

    1 useSecurity scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    MCP Vysor Starter

    Example session with this skill installed

    The phone is connected with USB debugging. Open the profile screen, find the push notifications control, turn it off, and confirm with a new screenshot that the label changed.

    • Read your context and instructions
    • Compiled the mcp vysor starter

    Summary

    Push notifications were turned off on the connected Android device. The follow-up screenshot shows the control label changed to the enable state.

    What the agent did

    1. adb_list_devices — one device online (S98Pro, 1080x2340, density 480).
    2. adb_screenshot_with_grid with grid_step 100 to locate the profile tab.
    3. adb_tap on the profile tab, then a second screenshot of the profile screen.
    4. adb_tap on the push notifications toggle.
    5. adb_screenshot again. The control description changed to the enable-notifications state and the screen showed that notifications were disabled.
    StepToolCheck
    Deviceadb_list_devicesstatus device, not unauthorized
    Screenadb_get_screen_info1080 x 2340
    Beforeadb_screenshot_with_gridprofile tab visible
    Actionadb_taptoggle pressed
    Afteradb_screenshotnotifications disabled

    Next steps

    • Keep ADB_PATH=adb in the MCP config.
    • If a second device appears, set ADB_DEVICE to the serial you want.
    • For labeled controls, prefer adb_find_elements and adb_tap_element before guessing pixels.
    • On WebView screens, fall back to the grid when the UI dump misses a button.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    This skill teaches an agent how to drive a real Android device with the open-source mcp-vysor server. Agensi does not host the server. You install it locally with npx -y mcp-vysor, connect a phone or emulator with USB debugging, and the agent follows a fixed loop: list devices, read the screen size, capture a screenshot with a coordinate grid, tap or swipe, then capture again to confirm the change.

    What you get

    • Cursor config template (npx -y mcp-vysor)
    • Setup checklist: Node.js 18+, adb on PATH, unlocked screen, ADB_DEVICE when more than one device is online
    • Default loop for screenshots, labeled taps, pixel taps, and percent taps
    • Rules for WebView screens, where the UI dump can miss controls and the grid is the fallback

    What stays free and yours

    The MCP server remains on GitHub and npm. This listing is non-exclusive. The paid playbook pack is a separate skill.

    https://github.com/glira/mcp-vysor https://www.npmjs.com/package/mcp-vysor

    Needs a local install of mcp-vysor (npx -y mcp-vysor), Node.js 18+, and adb. The phone or emulator must show as device in adb devices, with the screen unlocked. This pack does not host the MCP server. WebView screens can omit controls from the UI dump; use the coordinate grid in that case. One device at a time unless ADB_DEVICE is set.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    1 use

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    • Free with an Agensi account

    Requires

    Vysor MCP
    before
    Node.js

    Permissions

    No special permissions declared or detected

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    This skill allows your AI agent to bridge the gap between digital instructions and physical hardware by using ADB to capture screens, parse UI elements, and execute precise touches on Android devices. It solves the issue of agents 'hallucinating' coordinates by using a coordinate-grid system and state validation loops.

    You will need Node.js 18 or higher, the Android Debug Bridge (ADB) installed on your system path, and the `mcp-vysor` server running to facilitate the connection between the agent and your device.

    Yes, while designed for physical hardware, this skill is fully compatible with Android emulators as long as they are detectable via ADB and have USB debugging/developer options enabled.

    Standard prompts struggle to translate visual screen data into accurate pixel coordinates for input; this skill handles the complex scaling math and UI tree parsing automatically to ensure clicks land exactly where intended.

    The skill supports any AI agent or platform that is compatible with the Model Context Protocol (MCP) and has access to your local environment where ADB is installed.

    Currently, the skill is optimized for interacting with a single active device; if multiple devices are connected, you must specify the unique Device ID (serial number) to ensure the agent targets the correct hardware.

    New in Mobile Development