Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Expo Agent Bridge is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Let AI agents see, tap, type, scroll, screenshot and debug your Expo app on a real phone.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user expo-agent-bridge-mcp '--' npx -y expo-mcp-bridge
# 2 — ask your agent for something these tools do
# app_status, app_snapshot, app_layout and 14 more
Expo Agent Bridge costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Expo Agent Bridge as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user expo-agent-bridge-mcp '--' npx -y expo-mcp-bridgeReconnect, or start a new session, and the tools appear in the model’s tool list.
Nothing is required, but it can take EXPO_MCP_PORT (WebSocket port the phone connects to (default 8347)) if you want to set it.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
17 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Check whether the mobile app is connected and show device info. Call first.
No parameter schema on file.
Compact text outline of the current screen (buttons, inputs, text, lists) with refs like [e3] to act on. Prefer this over screenshots.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| maxLines | integer | no | default 400 |
Positions (dp, window coordinates) and font sizes of elements on the current screen. For layout checks and visual work; app_snapshot is cheaper for acting.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | max elements, default 250 |
JPEG screenshot of the app. Use only for visual/layout questions; app_snapshot is cheaper for finding elements. With saveTo, writes the file and returns only its path (no image tokens).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| maxWidth | integer | no | pixels, default 400 |
| quality | number | no | 0-1, default 0.6 |
| saveTo | string | no | file path (.jpg) to save instead of returning the image |
| area | string | no | auto (default) = visible screen; window = whole window incl. overlays |
| fullScroll | boolean | no | capture the whole content of the main scroll view as one tall image |
Run several actions in one call (fastest way to fill forms or walk a flow). Returns the screen once at the end. Steps: {action:"tap"|"type"|"scroll"|"toggle"|"navigate"|"wait"|"dismiss_keyboard", ...that tool's args}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| steps | array | yes | — |
Press a button/pressable element. Returns what changed on screen plus any new errors.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| long | boolean | no | long press |
Set text in an input (replaces by default). Target by ref, testID, or placeholder text.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| value | string | yes | — |
| append | boolean | no | — |
| submit | boolean | no | fire onSubmitEditing (like pressing enter) |
Scroll a list/ScrollView (first one on screen if no target).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| direction | string | no | — |
| amount | number | no | pixels, default ~70% of screen |
Flip a Switch (or set it with value).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| value | boolean | no | — |
Open a route (expo-router path like "/settings") or a full deep link.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | yes | — |
| replace | boolean | no | replace the current screen instead of pushing (keeps the stack shallow) |
Wait until text or a testID appears (or disappears with gone=true). Cheaper than polling snapshots.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | no | — |
| testID | string | no | — |
| gone | boolean | no | — |
| timeout | integer | no | ms, default 5000, max 30000 |
Console logs and JS errors captured in the app.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| level | string | no | "error" = errors only, "warn" = warnings and errors |
| search | string | no | — |
| since | integer | no | only entries after this cursor (returned as "cursor") |
| limit | integer | no | default 50 |
| clear | boolean | no | — |
HTTP requests made by the app (fetch/XHR) with status, timing and truncated bodies.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| failedOnly | boolean | no | — |
| search | string | no | substring of URL |
| since | integer | no | — |
| limit | integer | no | default 30 |
| bodies | boolean | no | include request/response bodies (default false) |
Run JavaScript inside the app (dev only) and return the JSON result. Expression or statements with return. bridge and RN (react-native) are in scope.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | — |
Reload the JS bundle (like pressing r in Metro).
No parameter schema on file.
Hide the on-screen keyboard.
No parameter schema on file.
Press a hardware/system key on an Android device via adb (USB or Wi-Fi debugging): ….
| Parameter | Type | Required | Notes |
|---|---|---|---|
| key | string | yes | — |
| repeat | integer | no | — |
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Expo Agent Bridge or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (17 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| app_status | no tags | |
| app_snapshot | no tags | |
| app_layout | no tags | |
| app_screenshot | no tags | |
| app_batch | no tags | |
| app_tap | no tags | |
| app_type | no tags | |
| app_scroll | no tags | |
| app_toggle | no tags | |
| app_navigate | no tags | |
| app_wait | no tags | |
| app_logs | no tags | |
| app_network | external-sink | external-sink: keyword "http_request" |
| app_eval | code-exec | code-exec: keyword "eval" in tool name |
| app_reload | no tags | |
| app_dismiss_keyboard | no tags | |
| device_key | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.3.2. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Expo Agent Bridge can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.