Skip to main content
Glama
appdropper-io

@appdropper/mcp

Official

Related Servers

Alternatives to @appdropper/mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Share Android and iOS builds with testers from your AI agent. Sets up the build for Expo, React Native, Flutter or native apps, uploads the .apk or .ipa, and returns an install link and QR code, plus tester feedback.
      12
      29 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to verify work on live cloud devices by uploading builds, starting sessions, driving UI through UI-tree refs, reading logs, and taking screenshots on iOS, Android, Apple TV, and Android TV.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to interact with Appcircle mobile CI/CD platform for build management, signing identities, testing distribution, and reporting.
      25
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables users to upload Android .aab files to Google Play test tracks and iOS .ipa files to TestFlight, then promote or release them to production through fastlane. Also supports rollout updates, release status checks, and confirmation-gated publishing actions.
      7
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      Ship over-the-air updates for Capacitor apps from an agent: inspect the project, check native compatibility, upload web bundles, publish releases after your approval, read rollout health, and revert.
      23
      50
      MIT

    TDQS

    A4.1/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: find_builds searches local files, list_apps lists remote apps, list_builds lists remote builds, get_build retrieves a single build, upload_build writes, and whoami checks auth. The similar names find_builds and list_builds are clearly differentiated by their descriptions (local directory search vs. remote app builds), leaving no real ambiguity.

    Naming Consistency4/5

    All names use snake_case and follow a verb_noun pattern (upload_build, find_builds, list_apps, list_builds, get_build). The only deviation is whoami, which is a single word rather than verb_noun, but it is a standard, readable convention.

    Tool Count5/5

    Six tools is well-scoped for a build distribution service. Each tool has a clear purpose (upload, local discovery, app listing, build listing, single build retrieval, auth) and none appear redundant.

    Completeness4/5

    Core build distribution workflows are covered: find local build, upload, list apps, list builds, get build details, and verify auth. Missing operations like deleting a build or updating release notes are minor gaps that agents can work around, but they slightly limit full lifecycle coverage.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues