Skip to main content
Glama
MauricePutinas

Android Studio MCP

by MauricePutinas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Android Studio MCP

No user-submitted related servers found.

    Related Servers

    • android_emulator

      huguangyu666
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides 23 Android development tools for Gradle builds, emulator/device lifecycle, APK install/launch, screenshots, logs, ADB and UI Automator automation, along with an android-dev skill for guided workflows.
      224 npm
      MIT

    • Enhanced ADB MCP Server

      rahulkr
      A
      license
      C
      quality
      D
      maintenance
      Enables comprehensive control of Android devices via ADB for Flutter development, UI testing, and visual QA workflows. Provides 60+ tools for device management, UI inspection, app testing, performance profiling, and debugging through natural language.
      77
      MIT

    • mobilerun-mcp

      impeterwayne
      A
      license
      C
      quality
      B
      maintenance
      Enables AI agents to control Android phones, emulators, redroid containers, iOS devices, and cloud-hosted devices through a perceive-act-verify loop of screen reading, taps, gestures, typing, and app launching. Exposes 138 tools for driving screens, elements, and files over adb, Portal APIs, and ios-portal without running ARM-only code on the device.
      94
      0
      1
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.6/5.0

    Scored across 73 tools

    Disambiguation4/5

    Most tools have distinct purposes with clear names and descriptions, but the large number (73) introduces some potential for confusion, especially among similar ADB and logcat tools. Overall, an agent can differentiate them.

    Naming Consistency5/5

    All tools follow a consistent as_<category>_<verb> pattern (e.g., as_adb_devices, as_gradle_assemble). The naming is predictable and well-structured throughout the entire set.

    Tool Count2/5

    73 tools is excessive for most use cases. While the server covers many sub-domains, this number is far above the typical well-scoped range (3-15), making it difficult to navigate and manage.

    Completeness4/5

    The tool set is very comprehensive, covering IDE control, ADB, Gradle, AVD, SDK, project management, and diagnostics. Minor gaps exist (e.g., limited ADB shell commands), but overall it addresses the Android development domain thoroughly.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources