rn-sim-mcp
Related Servers
Alternatives to rn-sim-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for interacting with Xcode build tools, iOS Simulator, and Apple notarization services.12 npm5MIT
- AlicenseNot gradedqualityBmaintenanceFirst-party MCP server and CLI for Xcode and iOS Simulator automation. Enables control of Xcode and iOS Simulator via MCP tools for tasks like building, testing, and automation.164 npm1MIT
- AlicenseNot gradedqualityAmaintenanceA plugin-based MCP server for React Native runtime debugging, inspection, and automation via Chrome DevTools Protocol. Works with Expo, bare React Native, and any Metro + Hermes project without app code changes.836 npm81MIT
- AlicenseNot gradedqualityAmaintenanceThis MCP server enables real-time debugging and inspection of running React Native apps, providing access to console logs, errors, network requests, navigation state, storage, and performance profiling.1MIT
- AlicenseNot gradedqualityCmaintenanceLocal MCP server for iOS Simulator and macOS app automation with a TypeScript MCP layer and Swift native bridge. Enables UI inspection, input automation, and simulator control through unified generic tools.76 npm26MIT
- AlicenseAqualityDmaintenanceAn MCP server for iOS simulator automation with reliable clipboard-based text input that works with React Native.187 npm1MIT
TDQS
Scored across 24 tools
While many tools are distinct, there is notable overlap between screenshot tools (screenshot vs sim_screenshot_hires vs snapshot_ui) and UI inspection tools (ui_describe_all vs snapshot_ui, ui_find_element vs rn_component_tree). Descriptions clarify intent, but an agent could easily misselect between tools that appear to perform similar actions.
Tool names follow inconsistent patterns: some use domain prefixes (rn_, ui_, sim_), some are bare verbs (build, launch, stop, test), and structures vary between verb_noun (build_run_sim, launch_app_sim) and noun_phrase (sim_screenshot_hires, rn_component_tree). This mix makes the naming chaotic and unpredictable.
24 tools is at the heavy end, but the server aggregates functionality for Xcode builds, RN debugging, and UI automation, so each tool has a purpose. The count is justified but feels somewhat bloated due to overlapping screenshot and inspection tools.
The tool set covers the full lifecycle for React Native iOS simulator work: building, running, testing, launching, stopping, UI interaction, component/styles inspection, and layout auditing. Minor gaps exist (e.g., no explicit reset or uninstall tool), but core workflows are well-supported.