Skip to main content
Glama
vwww-droid

algorithmaide-mcp

by vwww-droid
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to algorithmaide-mcp

No user-submitted related servers found.

    Related Servers

    • LuckyStar MCP Server

      lilyco-42
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that lets AI agents drive the LuckyStar/LS_KTool Android memory-debugging stack, exposing tools for memory read/write, scanning, pointer operations, and device/process management via the Model Context Protocol.
      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.
      17 npm
      2
      MIT

    • DroidAgentKit

      iVamsi
      F
      license
      Not graded
      quality
      A
      maintenance
      MCP server that provides AI coding agents real Android development tools—Gradle, adb, logcat, lint, crash triage—through a local, permissioned interface. Enables agents to inspect projects, run safe Gradle tasks, capture logs/screenshots, and triage crashes.
      1
      -

    • HexForge Gateway

      boy-offi9-inc
      A
      license
      A
      quality
      B
      maintenance
      This server enables AI-assisted APK reverse-engineering entirely on-device, orchestrating jadx, apktool, adb, frida, and APKiD through a job/workflow engine, and exposing those agents as native MCP tools for Claude without any cloud dependency.
      38
      20
      7
      MIT

    • ThumbAgent

      LiuShiYi1027
      A
      license
      Not graded
      quality
      A
      maintenance
      Local-first MCP server that enables AI agents to safely control and observe Android mobile devices, supporting device diagnostics, app lifecycle management, async task execution, and performance monitoring through a policy-constrained interface with explicit confirmations.
      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

    C2.7/5.0

    Scored across 23 tools

    Disambiguation3/5

    Several tool pairs have overlapping purposes (e.g., multiple log querying tools, add/inject/replace hooks), which may confuse an agent about which to use. However, descriptions help differentiate most tools.

    Naming Consistency4/5

    All tools follow a consistent verb_noun snake_case pattern, but some verbs are vague (e.g., 'get' vs 'query' vs 'read') and import_hook_json breaks the config naming pattern.

    Tool Count4/5

    23 tools is reasonable for the specialized domain of Frida hook management. The count slightly exceeds the ideal 3-15 range but is still manageable.

    Completeness4/5

    The tool surface covers most lifecycle operations: config, hooks, profiles, logs, and workflows. Minor gaps include lack of explicit hook removal and a dedicated disable function.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources