@betadrop/mcp
OfficialRelated Servers
Alternatives to @betadrop/mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceAutomate App Store Connect from your AI agent. Manage versions, metadata, builds, and submissions through natural language.10 npm8MIT
- FlicenseAqualityDmaintenanceEnables AI assistants to access TestFlight beta tester feedback, including screenshots, crash logs, and text comments from App Store Connect. It works across any platform without requiring Xcode, using official API keys and optional browser automation for full text feedback.8-
- AlicenseAqualityCmaintenanceEnables AI assistants to manage Apple App Store Connect resources like apps, builds, TestFlight, and reviews through natural language.207 npmMIT
- AlicenseNot gradedqualityBmaintenanceConnects AI coding clients like OpenCode, Codex, and Claude Code to Xcode and Apple development tools, enabling builds, tests, simulator and device management, profiling, asset handling, and more through natural language.157 npm1MIT
- AlicenseBqualityDmaintenanceTransforms AI assistants into mobile development powerhouses with 36 tools for Flutter, Android, and iOS development, including intelligent device management, automated builds, testing, and deployment workflows.3124 npm7MIT
- FlicenseAqualityCmaintenanceEnables AI coding tools to validate local projects and publish or update applications to Bedengan App Hub via API, with automated checks and live deployment without manual approval.5-
TDQS
Scored across 11 tools
Most tools map to a distinct action or resource (auth, publish, builds, tokens), and descriptions clarify intended use. However, betadrop_list_builds and betadrop_list_expired_builds overlap heavily, since the latter is just a filtered shortcut for the former, creating some selection ambiguity.
All tools share a uniform betadrop_ prefix and lowercase snake_case, which is helpful. But naming style is mixed: build commands use verb-first (list_builds) while token commands use noun-first (token_list, token_create), and whoami/login/logout are not verb_noun. Overall readable and mostly predictable.
Eleven tools is well-scoped for a BetaDrop-focused server; each tool covers a meaningful part of auth, publishing, build listing, and token management. No obvious bloat or redundancy.
Auth lifecycle, publishing/upload status, build listing, expired listing, and token management cover the core workflows an agent would need for BetaDrop. Minor gaps exist, such as no per-build detail/delete or expanded server info, but they are not dead ends.