Skip to main content
Glama
fastmcp-me

Android Project MCP Server

by fastmcp-me

Related Servers

Alternatives to Android Project MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to build, install, and launch Android apps on emulators and physical devices, automate UI interactions, inspect logcat/crash diagnostics, measure JaCoCo coverage, and discover or scaffold projects through an MCP server.
      9,072 npm
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Lets AI coding agents build, test, and lint Android projects with Gradle, control devices and emulators via adb, automate UI through screenshots and input injection, and use a live IDE bridge for refactoring, code inspection, and run configurations. Works with any MCP client over stdio or authenticated HTTP.
      46
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables controlling an Android device from an MCP client via ADB, including wireless debugging discovery, UI-tree inspection, and performing taps, swipes, typing, app actions, and shell commands without relying on screen coordinates.
      1 npm
      MIT
    • A
      license
      B
      quality
      C
      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.
      4
      14
      66 npm
      18
      MIT
    • 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
      -

    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