mcp-to-mobilelisted

Flagship AiGNITE pipeline. Takes any AiGNITE MCP server URL, lists its tools, and scaffolds a complete React Native mobile app with one screen per public tool, Supabase auth, push notifications, and Stripe subscription billing. Converts B2B MCP infrastructure into a B2C consumer product without rebuilding the backend. Use this skill whenever the user mentions turning an MCP into a mobile app, wrapping an MCP as a consumer app, building a mobile front end for an MCP, MCP to mobile, or making a consumer app from an MCP server, even if they do not name the skill by name.
nuwansamaranayake/AiGNITEClaudeAssets · ★ 0 · AI & Automation · score 70

Install: claude install-skill nuwansamaranayake/AiGNITEClaudeAssets

# mcp-to-mobile ## Purpose Convert an existing AiGNITE MCP server into a paid consumer mobile app in one orchestrated pipeline. Compose the other seven skills in the suite into a single command. ## When to trigger Trigger on these user phrases. Match loosely. - "turn this MCP into an app" - "wrap my MCP server as a mobile app" - "build a consumer app for [MCP name]" - "mobile front end for [MCP product]" - "consumer app from MCP" - "MCP to mobile" ## Inputs to collect 1. MCP server URL, or one of the AiGNITE shortcuts: `beacon-gom`, `regscope`, `recallwatch`, `floodpulse`, `airshield`, `cosmic-nexus`. 2. Target app name (defaults to a derived form). 3. Target bundle ID (defaults to `com.aignite.<slug>`). 4. Whether to include subscription billing (default yes). 5. Whether to include push notifications (default yes for alert-style MCPs, off for request-response). ## Behavior ### Step 1: list tools - Resolve the shortcut to a URL using [references/aignite-mcp-catalog.md](references/aignite-mcp-catalog.md). - Call the MCP server's `tools/list` endpoint. - Print the full tool list. - Apply the public-safe whitelist for the chosen MCP server. The whitelist lives in the catalog. ### Step 2: select screens - Show the user the filtered tool list. - Ask the user to pick which tools become user-facing screens. - Default to all read-only tools. - Refuse to expose any tool not on the public-safe whitelist. ### Step 3: scaffold the project Call `mobile-app-scaffold` with the