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-mcp-toolkit

      Dante3750
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to build, test, lint, and debug Android projects with concise Gradle output, filtered logcat, and connected-device inspection and interaction. It also supports setup across several agent clients and caps noisy output to save tokens.
      13 npm
      MIT

    • mcp-android

      dockndevai
      A
      license
      B
      quality
      B
      maintenance
      Enables Claude to control an Android phone over ADB by viewing screenshots and UI hierarchy and performing taps, typing, key presses, app launches, alarms/timers, and notification reads, with safe-by-default access modes and gated destructive actions.
      7
      36 npm
      MIT

    • 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.
      66 npm
      MIT

    • android_lab

      supart
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables Codex to discover, lease, start, control, and release registered local Android Studio emulators through a 63-tool catalog with readiness checks, screen-state reads, and lease-bound UI automation.
      -
    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
    ResponsivenessUnresponsive

    Resources