Skip to main content
Glama

Related Servers

Alternatives to mcp-android

No user-submitted related servers found.

    Related Servers

    TDQS

    B3.1/5.0

    Scored across 65 tools

    Disambiguation2/5

    Many tools occupy overlapping territory: wait_idle, wait_change, wait_activity, ui_wait_for, and events_wait are all wait-like; status, device_info, capabilities, diagnostics, and the privilege status tools blur together; input_text and ui_set_text both set text; global_action and press_key both handle navigation. Descriptions help in some cases, but with 65 tools the boundaries are frequently unclear.

    Naming Consistency4/5

    All tools share the android_ prefix and use clean snake_case, with strong domain grouping like android_file_*, android_ui_*, and android_notification_*. However, the verb/noun order is inconsistent (android_clipboard_get vs android_launch_app vs android_ui_find) and a few abstract nouns like android_flow and android_batch break the pattern.

    Tool Count1/5

    65 tools is an extreme count for a single MCP server. Many could be consolidated, especially the status/privilege reports, wait variants, coordinate gesture tools, and execution helpers. The scope is broad, but the surface is not well-scoped.

    Completeness4/5

    The set covers UI observation and interaction, app launching and management, clipboard, notifications, media, volume, shell, logcat, file CRUD, and multi-step flows, so real workflows rarely dead-end. Minor gaps exist around app installation/uninstallation and direct system setting toggles, but most can be worked around via existing shell or intent tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues