Skip to main content
Glama
znm2500

aul_uploader

by znm2500
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to aul_uploader

No user-submitted related servers found.

    Related Servers

    • aimade-mcp

      elliothimmelfarb
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to publish games through typed MCP tools, including creating games, uploading builds, defining achievements, attaching media, and publishing without human dashboard interaction.
      41
      Apache 2.0

    • APK-MCP

      tkb-bit
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides AI agents with a unified MCP interface for Android APK reverse engineering, metadata analysis, Smali/resource editing, rebuilding, signing, verification, and ADB device testing.
      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.
      9 npm
      2
      MIT

    • adb-mcp-server

      sfaizi24
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables MCP-compatible agents to control an Android device over the network via ADB, providing tools for shell commands, screen capture, UI inspection, file operations, and input simulation.
      5 npm
      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

    A3.8/5.0

    Scored across 8 tools

    Disambiguation4/5

    Each tool covers a distinct resource or action: token validation, config fetching, cover upload/download, release asset publishing, entry addition, APK ID generation, and the composite full upload flow. The only mild ambiguity is that full_upload_game overlaps with the individual upload steps, but its description clearly positions it as the complete one-click alternative.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern like check_tokens, get_config, add_game_entry, upload_cover_image, and get_apk_id. The main deviation is full_upload_game, which does not start with the verb, but the overall naming is still predictable and readable.

    Tool Count5/5

    With 8 tools, the set is well scoped for an upload pipeline: it covers authentication, config retrieval, APK parsing, cover image handling, asset release, entry creation, and a composite workflow. Each tool earns its place without the set feeling bloated or too sparse.

    Completeness4/5

    The core upload lifecycle is fully supported: token validation, config fetching, adding entries, uploading covers, publishing release assets, and the full end-to-end flow. Minor gaps exist, such as the lack of update/delete operations for game entries and no release tag creation, but these are mostly outside the primary uploader scope and can be worked around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources