Skip to main content
Glama
vs4vijay

espresso-mcp

by vs4vijay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to espresso-mcp

Related Servers

  • polyscreen-mcp

    Shenepoy
    A
    license
    A
    quality
    A
    maintenance
    An Android-first MCP server for automating real devices, including multi-display handhelds and emulators, with structured tools for device inspection, input, app lifecycle, and diagnostics via ADB.
    33
    16 npm
    Mozilla Public 2.0

  • adb-mcp

    myNameArnav
    A
    license
    Not graded
    quality
    D
    maintenance
    MCP server for controlling Android devices over ADB, using direct commands and semantic accessibility selectors with a Kotlin helper APK.
    73 npm
    MIT

  • android-mcp

    tomdwipo
    F
    license
    Not graded
    quality
    C
    maintenance
    A lightweight MCP server for Android operating system automation. This server provides tools to interact directly with Android devices and app interaction with control
    3
    -

  • replicant-mcp

    thecombatwombat
    A
    license
    B
    quality
    B
    maintenance
    An MCP server that enables AI assistants to build, test, and debug Android applications by interacting directly with the Android development environment. It provides tools for managing emulators, executing Gradle tasks, running ADB commands, and performing UI automation via accessibility trees.
    14
    43 npm
    16
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3/5.0

Scored across 22 tools

Disambiguation3/5

Most tools are clearly separated by resource and action, but clear_and_type_text and replace_text describe essentially the same operation, which creates real ambiguity. The unrelated fetch_weather tool also muddies the tool surface.

Naming Consistency4/5

The overwhelming majority of tools follow a clear verb_noun snake_case pattern (list_apps, start_emulator, take_screenshot). Minor deviations include short gesture verbs like tap and swipe, plus the redundant clear_and_type_text vs replace_text naming.

Tool Count3/5

22 tools is on the heavy side but mostly justifiable for Android emulator/device automation. The count feels inflated by the duplicate text-replacement tools and the off-topic weather tool, which could be trimmed.

Completeness3/5

Core emulator and app lifecycle operations are covered well, along with common UI interactions. Obvious gaps include no AVD creation/deletion, no device/serial selection, and no test-running or assertion tools despite the espresso name.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources