Skip to main content
Glama
OtaKit

OtaKit

Official

Related Servers

Alternatives to OtaKit

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Capgo: push fixes to your Capacitor users in minutes, build signed iOS and Android apps without a Mac, and roll back in one click.
      213
      AGPL 3.0
    • 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
      Not graded
      quality
      B
      maintenance
      Enables coding agents to inspect projects, boot devices, run and control Flutter, Next.js, Vite, React Native/Expo, and native iOS/Android apps, then apply edits with hot reload or restart. It returns focused reload results, compiler and console errors, failed network requests, logs, and screenshots so agents can verify changes.
      137 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets coding agents such as Codex and Claude Code ship GitHub frontends, backend servers, Docker images and Compose stacks to CBGPU using an authenticated account session, then poll build status and logs, manage subdomains and custom domains, and roll back releases. It runs locally over stdio and deliberately exposes no tools for reading or writing secrets.
      Apache 2.0

    TDQS

    A3.7/5.0

    Scored across 23 tools

    Disambiguation4/5

    Most tools target a clearly distinct resource+action (bundles vs releases vs previews vs account), and the prepare/publish and prepare/revert pairs are explicitly framed as preview-vs-apply. The main overlap is upload_and_publish_bundle duplicating the upload_bundle + publish_release path, and get_release_state vs prepare_release vs list_releases require careful reading to distinguish.

    Naming Consistency5/5

    All names are snake_case with a consistent verb-first pattern (list_, get_, create_, delete_, upload_, prepare_, publish_, revert_, set_, revoke_, check_, inspect_). The only mild deviation is the compound upload_and_publish_bundle, which is still readable and predictable.

    Tool Count4/5

    23 tools is on the heavy side but the domain is genuinely broad (apps, bundles, releases, rollouts, reverts, previews, diagnostics, account). Most tools earn their place, though the combined upload_and_publish_bundle is redundant with the atomic upload/publish pair and could be consolidated.

    Completeness4/5

    Coverage spans the full bundle/release lifecycle including upload, publish, rollout, revert, preview, and diagnostics (health, events, audit, compatibility). Notable gaps are channel management (channels are referenced in filters but have no create/list/update tools) and app update/delete, which agents cannot perform.

    Maintenance

    ActivityActive
    ResponsivenessOutdated data