A
licenseNot graded
qualityD
maintenanceEnables automated management of iOS apps, builds, TestFlight beta testing, and user access control through Apple's App Store Connect API.
10 npm
MIT
flutter-ios-bridge-mcp
Related Servers
Alternatives to flutter-ios-bridge-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables coding agents to build, test, archive, and run iOS apps on a remote Mac fleet from any environment, with XcodeBuildMCP-compatible tools and live simulator access.1159 npmMIT
- AlicenseAqualityCmaintenanceBuild, sign, and publish iOS and Android apps through AI agents. Integrates Codemagic CI/CD, App Store Connect, and Google Play in one server.639 npm1MIT
- FlicenseNot gradedqualityCmaintenanceEnables TestFlight deployment and App Store Connect build lookup for iOS projects, including project registration, rsync/ssh deployment, and retrieving build numbers.-
- AlicenseNot gradedqualityCmaintenanceAn MCP server for headless mobile QA automation that controls real Safari, Flutter, and native iOS apps on Xcode Simulators via WebKit Remote Debugging Protocol, enabling parallel multi-device testing and persistent login sessions.44 npm15MIT
- 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.3129 npm7MIT
TDQS
B3.2/5.0
Scored across 44 tools
Disambiguation5/5
Despite the size, every tool is scoped to a distinct backend/resource/action: project config, CI, signing, ASC/TestFlight, remote Mac, or USB device. The prefix plus explicit target (e.g. mac_build vs ci_trigger_build) makes misselection unlikely.
Naming Consistency4/5
Tools consistently use lowercase snake_case with backend prefixes and mostly verb_object forms. A few noun-style names (`bridge_status`, `ios_doctor`, `testflight_builds`) break the strict verb_noun pattern, but the convention is otherwise predictable.
Tool Count2/5
44 tools is well above the 25+ threshold and creates a large discovery burden for an agent. The multi-backend scope explains the count, but splitting into smaller per-backend servers would make the surface far more manageable.
Completeness4/5
The surface covers the full Flutter iOS bridge lifecycle: audit/config, CI workflow, signing/ASC resources, TestFlight distribution, remote Mac build/run, and USB device operations. Minor gaps exist, such as no direct provisioning-profile deletion and no App Store Connect app-creation step, but core workflows have no dead ends.
Maintenance
ActivityNo data
ResponsivenessNo issues