Skip to main content
Glama
Sign In
ShenghaiWang

Android Project MCP Server

by ShenghaiWang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Android Project MCP Server

No user-submitted related servers found.

    Related Servers

    • Raccoon MCP

      luoluoluo22
      A
      license
      C
      quality
      C
      maintenance
      A local-first Model Context Protocol server that enables AI-assisted development through scoped file access, opt-in shell and process execution, Git automation, development pipelines, and optional Windows desktop and Android/ADB tools. It supports streamable HTTP and stdio transports with secure local-only defaults.
      105
      MIT

    • Codex MCP Server

      hailangx
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server for local repository indexing and code understanding, enabling semantic search, AST analysis, dependency tracking, and symbol resolution.
      1,539 npm
      ISC

    • Xcode MCP Server

      PolarVista
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants to build and test Xcode projects directly through a standardized interface, with capabilities for running tests, monitoring progress, and accessing logs in real-time.
      18
      210 npm
      53
      MIT

    • Cline Memory Bank

      dazeb
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that provides persistent project context management for AI-assisted development, specifically designed for the Cline VSCode Extension.
      4
      61
      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

    B3.1/5.0

    Scored across 3 tools

    Disambiguation4/5

    The three tools have mostly distinct purposes: building, running tests, and running instrumented tests. However, 'test' and 'instrumentedTest' could be slightly ambiguous as instrumented tests are a subset of tests, but the descriptions clarify this distinction.

    Naming Consistency5/5

    All tool names follow a consistent snake_case pattern with clear, descriptive verbs ('build', 'test', 'instrumentedTest'). There are no deviations in naming conventions, making the set predictable and readable.

    Tool Count3/5

    With only 3 tools, the server feels thin for an Android project domain, which typically involves more operations like linting, debugging, or emulator management. While the tools cover core build and test workflows, the scope seems limited.

    Completeness2/5

    The tool surface is significantly incomplete for Android development. It lacks essential operations such as cleaning, linting, deploying, debugging, or managing dependencies, which are common in this domain and could lead to agent failures in broader tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources