OtaKit
OfficialRelated Servers
Alternatives to OtaKit
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceCapgo: push fixes to your Capacitor users in minutes, build signed iOS and Android apps without a Mac, and roll back in one click.213AGPL 3.0
- AlicenseAqualityCmaintenanceEnables 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.7Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables 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 npm1MIT

@appdropper/mcpofficial
AlicenseAqualityCmaintenanceEnables coding agents to upload local .apk or .ipa builds and receive tester install links without leaving the editor.6209 npmMIT- AlicenseAqualityBmaintenanceProvides AI assistants with access to Capawesome documentation and Cloud management tools, enabling app, build, and deployment operations via API token authentication.362 npm2MIT
- AlicenseNot gradedqualityBmaintenanceLets 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
Scored across 23 tools
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.
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.
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.
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.