No user-submitted related servers found.
Scored across 77 tools
Family prefixes (xcodebuild-, simctl-, idb-) help, but the set contains several overlapping groups: simctl-launch/install/terminate mirror idb-launch/install/terminate, workflow-build-and-run overlaps workflow-fresh-install, and simctl-io overlaps screenshot for capture duties. Boundaries between simctl-get-app-container vs simctl-container and idb-ui-describe vs idb-ui-find-element vs accessibility-quality-check also blur, so agents must read deep documentation to avoid misselection.
Most tools follow a readable {prefix}-{verb}-{object} pattern with consistent family prefixes like simctl-boot, cache-get-stats, and persistence-enable. However, there are notable exceptions: standalone names (screenshot, rtfm), noun-only resources (idb-targets), operation-parameter objects (simctl-status-bar), and inconsistent ordering (xcode-model-inspect, workflow-tap-element, localization-audit). The conventions are mixed but still broadly predictable.
At 77 tools, this is far beyond the well-scoped range and imposes a heavy selection overhead on agents; the mirrored simctl/idb surfaces and multiple composite workflow tools inflate the count unnecessarily. The genuinely broad Xcode/simulator/idb domain justifies a larger-than-average surface, which keeps it from being a total mismatch, but it remains excessive.
The surface covers the full test-automation lifecycle—build, clean, test, simulator lifecycle, app install/launch, UI automation, screenshots, logs, crash analysis, permissions, keychain, appearance, location, and push—plus useful extras like localization audit, visual diff, and hang detection. Notable gaps remain: no xcodebuild archive/export for distribution, no signing or provisioning profile management, and no build-settings query.