expo-stack vs Expo
expo-stack is a plugin bundle for AI coding tools published by Flying Web Solutions. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Expo is an MCP server published by mcp-dir. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Expo | |
|---|---|---|
| Community marketplace flyingwebie/skills | Listed Version: 0.3.0 Forks (GitHub): 1 Stars (GitHub): 10 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.0 Forks (GitHub): 0 (last published figure) Stars (GitHub): 0 (last published figure) Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | expo-stack | Expo |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 10 | 0 (last published figure) |
| Forks (GitHub) (differs) | 1 | 0 (last published figure) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (api.mcp.ai/p_expo) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 24 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/flyingwebie/skills | github.com/mcp-dir/expo-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-18 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 12 h ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
expo-stack
Scaffolds a production-grade Expo app on one opinionated stack — Expo Router + Convex (cloud or self-hosted) + Better Auth + Uniwind + react-i18next + pre/post sign-in onboarding, with an Expo-UI-first UI layer (FlashList v2, TrueSheet, keyboard-controller, gifted-charts, calendars, pager-view), a react-native-ease / Reanimated / Skia motion split, deep linking through +native-intent (Universal/App Links plus the deferred-install gap), a premium-UI audit that verifies on a real device via argent alongside a screenshot-driven visual-design critique, revenue decisions backed by subscription data (trial length, hard vs freemium, Android billing recovery), ASO as part of the ship loop, and post-scaffold commands — /setup, /rebrand, /customize-onboarding, /configure-monetization, /add-language, /ship. Always resolves the latest Expo SDK — nothing is pinned except the mandatory better-auth version set, which is derived from the Convex component. bun/pnpm/yarn workspaces with the hoisting React Native actually needs
Expo
Your Expo and EAS project in natural language: up to date SDK docs, cloud builds (status, logs, trig
How to run each
expo-stack As a Claude Code plugin
/plugin marketplace add flyingwebie/skills
/plugin install expo-stack@fws-skillsExpo As a remote MCP server
claude mcp add --transport http expo-mcp https://api.mcp.ai/p_expoCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Expo has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: expo-stack · What it can do: Expo · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.