Skip to main content
Glama
0x-Professor

Android Forensics ADB MCP Server

by 0x-Professor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Android Forensics ADB MCP Server

No user-submitted related servers found.

    Related Servers

    • adb_mcp_server

      wolfcoming
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables remote control of Android devices via ADB, including screen operations, input, app management, file transfer, and advanced tools like UI testing and performance analysis.
      24
      MIT

    • android-device-mcp

      prashant1507
      F
      license
      B
      quality
      D
      maintenance
      Provides comprehensive Android device management capabilities through ADB, including device management, app management, file operations, and system monitoring.
      18
      1
      -

    • Android DevTools MCP

      xleepy
      A
      license
      A
      quality
      C
      maintenance
      Enables an agent to inspect and interact with Android emulators or physical devices via ADB, capturing UI snapshots, tapping nodes, typing text, and reading app logs.
      10
      MIT

    • MSC MCP Server

      NakanoSanku
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables control of Android devices through ADB, allowing users to list connected devices, capture screenshots using multiple methods (adb, droidcast, minicap, mumu), and retrieve device information.
      -

    • Enhanced ADB MCP Server

      rahulkr
      A
      license
      C
      quality
      D
      maintenance
      Enables comprehensive control of Android devices via ADB for Flutter development, UI testing, and visual QA workflows. Provides 60+ tools for device management, UI inspection, app testing, performance profiling, and debugging through natural language.
      77
      MIT
    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

    A4/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct forensic data source or action: root status, logcat, dmesg, packages, settings, network, processes, file extraction, partitions, and accounts. There is no overlap; even capture_logcat and capture_dmesg are clearly differentiated as system/app logs vs kernel buffer.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case (check_root_status, capture_logcat, get_installed_packages, etc.). The verbs are varied but predictable, and the structure is uniform across the set.

    Tool Count5/5

    10 tools is well-scoped for an Android forensics server, covering the major data sources without unnecessary redundancy. The count falls comfortably within the ideal 3-15 range, and each tool earns its place in the toolkit.

    Completeness4/5

    The set covers core forensic acquisition and analysis: device status, logs, installed apps, settings, network, processes, file extraction, partitions, and accounts. Minor gaps exist, such as dedicated tools for SMS/call logs or media files, but the generic extract_with_root can access these if the path is known, making it a workable limitation.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources