Skip to main content
Glama
fullread

DeepADB

by fullread
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to DeepADB

No user-submitted related servers found.

    Related Servers

    • adb-mcp

      FlashZ
      A
      license
      Not graded
      quality
      B
      maintenance
      A comprehensive MCP server for Android Debug Bridge, enabling AI agents to control Android devices through structured tools like launching apps, UI automation, file operations, and log capture.
      1
      MIT

    • android-adb-mcp

      qinxiandiqi
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that wraps Android ADB functionality into AI assistant tools, enabling device management, shell execution, file operations, app management, media capture, and log analysis via natural language.
      14 npm
      2
      MIT

    • android-mcp-server

      jaye773
      F
      license
      Not graded
      quality
      D
      maintenance
      A powerful MCP server that provides comprehensive Android device automation capabilities through ADB, enabling AI agents to interact with Android devices for testing, automation, and device control tasks.
      1
      -

    • Agent-Android

      xiaoran7
      A
      license
      B
      quality
      A
      maintenance
      A local MCP server that controls Android devices via ADB, enabling AI agents and users to manage devices, execute UI automation, and perform testing through 27 MCP tools and an optional web console.
      27
      1
      MIT

    • ADB MCP Server

      LLL-404
      F
      license
      A
      quality
      D
      maintenance
      A MCP server that enables AI assistants to control Android devices via ADB, supporting device info, screen control, input simulation, app management, shell execution, file transfer, and UI parsing.
      20
      -
    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

    B3.3/5.0

    Scored across 204 tools

    Disambiguation3/5

    Many tools have clearly distinct purposes, but there are several overlapping families: generic adb_input vs specialized gesture tools, adb_screencap vs annotated/compressed/baseline/diff variants, and numerous telephony/snapshot tools with subtle differences. Descriptions are detailed and usually clarify scope, but selection across 204 tools remains ambiguous in places.

    Naming Consistency4/5

    All tools share the adb_ prefix and use snake_case consistently, with a predominantly verb_noun pattern (list, get, start, stop, install, push, etc.). Minor deviations exist such as adb_devices vs adb_device_info, adb_screencap vs adb_screenshot_*, and adb_start_app vs adb_start_activity, but the overall style is predictable and readable.

    Tool Count1/5

    204 tools is an extreme count for any server, even for the broad ADB domain. It forces agents to navigate a massive surface with many near-duplicate specialized variants, creating significant cognitive load and selection overhead.

    Completeness5/5

    The tool surface is exceptionally comprehensive, covering device lifecycle, package management, filesystem operations, UI automation, networking, telephony, performance, security, testing, QEMU, workflows, and firmware analysis. Few standard adb operations (e.g., root/unroot, backup/restore) are missing, but the breadth makes those gaps negligible.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources