Skip to main content
Glama
fastmcp-me

Android Project MCP Server

by fastmcp-me
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Android Project MCP Server

No user-submitted related servers found.

    Related Servers

    • 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

    • DroidAgentKit

      iVamsi
      F
      license
      Not graded
      quality
      A
      maintenance
      MCP server that provides AI coding agents real Android development tools—Gradle, adb, logcat, lint, crash triage—through a local, permissioned interface. Enables agents to inspect projects, run safe Gradle tasks, capture logs/screenshots, and triage crashes.
      1
      -

    • Codex Android MCP

      zifanersuotang
      A
      license
      A
      quality
      C
      maintenance
      Enables Codex to inspect, test, and control Android emulators through adb with strict typed tools, returning screenshots as native MCP images and keeping physical devices and Gradle execution behind explicit opt-in policies.
      19
      MIT

    • android-build-mcp

      jjs03111
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that gives coding agents hands and eyes on an Android device, providing 19 tools for building, testing, installing, UI inspection, input, logs, and toolchain diagnosis. It returns concise, structured results to make the build-debug loop efficient.
      19
      1
      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

    C2.8/5.0

    Scored across 3 tools

    Disambiguation4/5

    Build is clearly distinct from testing, but 'instrumentedTest' and 'test' are ambiguous: the names are too similar and descriptions lack differentiation, potentially causing confusion.

    Naming Consistency2/5

    Naming is inconsistent: 'build' and 'test' are lowercase, while 'instrumentedTest' uses camelCase. No clear verb_noun pattern.

    Tool Count2/5

    Only 3 tools for an Android project is minimal. Common tasks like linting, cleaning, or building variants are missing, making the surface feel thin.

    Completeness2/5

    The tool surface lacks essential Android build operations (e.g., clean, lint, assembleDebug, generate signed APK). Testing coverage is incomplete without specifying unit vs integration.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources