Skip to main content
Glama
desamtralized

ADB Screenshot MCP Server

by desamtralized
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to ADB Screenshot MCP Server

No user-submitted related servers found.

    Related Servers

    • ADB MCP Server

      richard0913
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that provides Android Debug Bridge functionality for automating Android devices, enabling remote device management, screen operations, app management, file operations, and shell command execution.
      20
      4 npm
      1
      MIT

    • MCP Android Agent

      nim444
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI agents to control and automate Android devices through natural language, supporting actions like app management, UI interactions, and device monitoring.
      59
      MIT

    • airtest-mcp

      Heand-Broken
      A
      license
      B
      quality
      C
      maintenance
      A local Model Context Protocol server that enables MCP clients to control Android, iOS, and Windows devices through AirtestIDE, supporting device listing, screenshots, touch, swipe, key events, and app management.
      10
      1
      MIT

    • DroidMind

      hyperb1iss
      A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol (MCP) server that enables AI assistants to control and interact with Android devices, allowing for device management, app debugging, system analysis, and UI automation through natural language commands.
      8
      432
      Apache 2.0

    • android-adb-mcp

      Web4w3
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Android device management via ADB, enabling inspection and configuration of Android devices over USB or Wi-Fi.
      9 npm
      Apache 2.0
    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

    A3.5/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no ambiguity: connecting, disconnecting, listing devices, getting device info, and taking screenshots. The actions and targets are well-defined and non-overlapping, making it easy for an agent to select the correct tool.

    Naming Consistency5/5

    All tools follow a consistent 'adb_verb_noun' pattern (e.g., adb_connect_wifi, adb_device_info). The naming is uniform, using snake_case throughout, with clear verbs that describe the action and nouns specifying the target or resource.

    Tool Count5/5

    With 5 tools, the server is well-scoped for its purpose of managing ADB connections and taking screenshots. Each tool earns its place, covering essential operations without being overly sparse or bloated, making it efficient for the domain.

    Completeness4/5

    The toolset covers core workflows for ADB device management and screenshot functionality, but there are minor gaps such as missing tools for advanced device interactions (e.g., adb_shell for commands) or file transfer. However, agents can likely work around these for basic use cases.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources