@appdropper/mcpofficial
A
licenseA
qualityC
maintenanceEnables coding agents to upload local .apk or .ipa builds and receive tester install links without leaving the editor.
6
MIT
OtaKit
Officialby OtaKit
Related Servers
Alternatives to OtaKit
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceProvides AI assistants with access to Capawesome documentation and Cloud management tools, enabling app, build, and deployment operations via API token authentication.341 npm2MIT
- AlicenseAqualityAmaintenanceGives AI assistants access to current Capacitor documentation, plugin listings, and Ionic blog posts so they can provide accurate answers about Capacitor APIs and CLI usage.449 npm1MIT
- AlicenseAqualityBmaintenanceLets coding agents manage apps in App Store Connect through workflow-level tools: shipping TestFlight builds, managing testers and groups, editing listings, replacing and reordering screenshots, handling subscriptions, replying to reviews, downloading sales reports, and submitting for App Review. It is read-only unless writes are explicitly enabled, and destructive actions run as dry runs until confirmed.31MIT
- AlicenseAqualityBmaintenanceShare 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.12569 npmMIT
- AlicenseAqualityAmaintenanceEnables MCP-capable agents to manage Apple App Store Connect listings by validating repository-based metadata, planning changes, and applying approved updates through Apple's documented APIs.206 npmMIT
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
ResponsivenessUnresponsive