expo-app-controllisted
Install: claude install-skill Rudrasamadhiya/expo-mcp-bridge
# Controlling the running app
The `expo-app` MCP server talks to the app through `<AgentBridge />` (mounted in the app's root layout). Works in Expo Go and dev builds, on real phones over Wi-Fi.
## The loop
1. `app_status` — confirm the phone is connected. If not, show the user the help text it returns.
2. `app_snapshot` — the visible screen as a compact outline. Elements you can act on have refs like `[e4]` (refs stay stable between snapshots).
3. Act, targeting by `ref`, `testID`, or visible `text`:
- `app_tap` (`long: true` for long-press) · `app_type` (`submit: true` presses enter, `append: true` keeps text) · `app_scroll` (down/up/top/bottom) · `app_toggle` (switches) · `app_navigate` (expo-router path or deep link, `replace: true` to keep the stack shallow) · `app_dismiss_keyboard`
- Each action returns **only what changed** (`+` added, `-` removed, `~` changed) plus new JS errors and failed requests. Don't re-snapshot after an action.
4. Several steps (a form): one `app_batch` call, e.g. `[{action:"type", text:"Email", value:"…"}, {action:"type", text:"Password", value:"…"}, {action:"tap", text:"Log In"}]`.
5. Async content: `app_wait {text | testID, gone?}` instead of polling snapshots.
## Seeing more
- `app_screenshot` — only for visual questions (layout, colors, overlap). `saveTo` writes a file instead of returning the image; `fullScroll: true` captures a whole scrolling page as one tall image.
- `app_layout` — element positions (dp) and font sizes, for ali