expo-app-scaffold-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scaffold_appA | Scaffolds a new Expo + React Native app from the FSD template. Copies the template, updates app.json, package.json, eas.json, sets up i18n, and initializes a git repo. |
| setup_store_configA | Configures App Store and Google Play submission settings for an existing Expo project. Sets up fastlane Appfile/Fastfile, updates eas.json submit section, and optionally configures AdMob. |
| list_appsA | Lists all Expo apps found in ~/works/ by scanning for app.json files with expo configuration. Shows app name, slug, bundle ID, version, and path for each app. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.