expo-app-scaffold-mcp
Related Servers
Alternatives to expo-app-scaffold-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceProvides comprehensive tools for React Native development, automating project initialization, version management, upgrades, Expo integration, and development workflows through AI assistance.233 npm21MIT
- AlicenseNot gradedqualityDmaintenanceEnables programmatic interaction with Expo/React Native projects and EAS (Expo Application Services) for managing builds, publishing OTA updates, submitting apps to stores, and accessing comprehensive documentation.6MIT
- FlicenseNot gradedqualityNot gradedmaintenanceA Model Context Protocol server designed to streamline Expo and React Native development for AI assistants like Cursor and Claude. It provides a comprehensive suite of tools for project initialization, EAS builds, OTA updates, and development server management.1-
- AlicenseNot gradedqualityCmaintenanceEnables natural language management of Expo and EAS projects, including SDK documentation, cloud builds, CI workflows, store submission, and TestFlight crash and feedback data.MIT
- AlicenseNot gradedqualityBmaintenanceAutomates bootstrapping new Flutter applications with architectural structures, dependencies, routing, databases, networks, and shared utilities.MIT
- AlicenseNot gradedqualityCmaintenanceEnables automated testing and development of Expo/React Native apps through session-based Expo dev server management and Maestro UI automation tools for tapping, text input, screenshots, and flow execution.236,906 npm5MIT
TDQS
Scored across 3 tools
The three tools have clearly distinct purposes: discovery, creation, and store configuration. No two tools overlap in action or resource, so an agent can easily select the right one.
All tool names use consistent snake_case and follow a verb_noun pattern: list_apps, scaffold_app, setup_store_config. The convention is predictable throughout.
Three tools are appropriately scoped for a specialized Expo app scaffold server. Each tool covers a distinct phase of the workflow without unnecessary bloat.
The surface covers discovery, creation, and store configuration, which are the core workflows. Minor gaps exist around updating or removing existing apps, but these are not central to the stated scaffold purpose.