Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Nothing to run from here
Expo 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.
19
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Your Expo and EAS project in natural language: up to date SDK docs, cloud builds (status, logs, trig
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http mcp-dir-expo-mcp https://api.mcp.ai/p_expo
# 2 — ask your agent for something these tools do
# expo_add_library, expo_read_documentation, expo_search_documentation and 16 more
Expo costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
MDAll 1114 servers
mcp-dir1114 servers
18 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http mcp-dir-expo-mcp https://api.mcp.ai/p_expoReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
19 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.
Add an Expo library to the project using expo install and attach usage instructions when available
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectRoot | string | yes | — |
| libraryName | string | yes | — |
Fetch a single Expo documentation page and return its content as markdown. Returns up to ~5000 tokens per call. Use offset to paginate through long pages.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | — |
| offset | number | no | — |
Search the official Expo documentation and return page URLs ranked by relevance for a user query. Use read_documentation to fetch the full content of specific pages, starting from the top.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | — |
Learn Expo how-to for a specific topic and remember it for future conversations. Use this to teach the assistant about specific Expo features or workflows.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | — |
Creates a new EAS workflow YAML file for Expo projects or fetches workflow syntax documentation. Use this when users want to create CI/CD workflows in .eas/workflows/ or need to learn EAS workflow syntax. After creating, use workflow_validate to validate the file.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action | string | yes | — |
| projectRoot | string | no | — |
| fileName | string | no | — |
| workflowYaml | string | no | — |
Fetches detailed information about a specific EAS workflow run by ID. Use this to check the status, job results, errors, and artifacts of a workflow run. If workflow has multiple jobs, draw them in a diagram to show the dependencies between jobs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workflowRunId | string | yes | — |
Lists recent EAS workflow runs for a project. Provide either appId (from app.json "extra.eas.projectId") OR appFullName (e.g., "@owner/my-app").
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appId | string | no | — |
| appFullName | string | no | — |
| status | string | no | — |
| limit | number | no | — |
Fetches logs for a specific job in an EAS workflow run. Call without sectionIndex or phase to get a summary of log sections (phase names and line ranges); then call again with sectionIndex or phase to fetch that section.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workflowRunId | string | yes | — |
| jobKey | string | yes | — |
| sectionIndex | number | no | — |
| phase | string | no | — |
Triggers an EAS workflow run from a git reference. Provide either appId (from app.json "extra.eas.projectId") OR appFullName (e.g., "@owner/my-app"). The workflow file must exist at the specified git reference.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appId | string | no | — |
| appFullName | string | no | — |
| fileName | string | yes | — |
| gitRef | string | yes | — |
Cancels a running EAS workflow. Use workflow_info to get the workflow run ID.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workflowRunId | string | yes | — |
Validates EAS workflow YAML syntax and configuration. Use this after creating a workflow to ensure it is valid. Provide either appId (from app.json "extra.eas.projectId") OR appFullName (e.g., "@owner/my-app").
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appId | string | no | — |
| appFullName | string | no | — |
| workflowYaml | string | yes | — |
Lists EAS builds for a project. Provide either appId (from app.json "extra.eas.projectId") OR appFullName (e.g., "@owner/my-app"). Use this to see recent builds, their status, and available artifacts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appId | string | no | — |
| appFullName | string | no | — |
| platform | string | no | — |
| status | string | no | — |
| limit | number | no | — |
Fetches the status and detailed information about a specific EAS build by ID. Use this to check build status, errors, artifacts, and other details.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| buildId | string | yes | — |
Fetches the logs for a specific EAS build. The build must be completed (finished or errored) to have logs available.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| buildId | string | yes | — |
Submits an EAS build to the app store (Google Play Store for Android, App Store for iOS). The build must be a finished build with the appropriate distribution type. Provide either appId (from app.json "extra.eas.projectId") OR appFullName (e.g., "@owner/my-app").
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appId | string | no | — |
| appFullName | string | no | — |
| buildId | string | yes | — |
| platform | string | yes | — |
| track | string | no | — |
| ascAppIdentifier | string | no | — |
Triggers a new EAS build using a build profile from eas.json. Requires a GitHub repository to be connected to the project. Provide either appId (from app.json "extra.eas.projectId") OR appFullName (e.g., "@owner/my-app").
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appId | string | no | — |
| appFullName | string | no | — |
| platform | string | yes | — |
| buildProfile | string | yes | — |
| gitRef | string | yes | — |
| baseDirectory | string | no | — |
| autoSubmit | boolean | no | — |
| submitProfile | string | no | — |
Cancels an EAS build that is queued or in progress. Use build_info to check the current status first.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| buildId | string | yes | — |
Fetch TestFlight crash data. Without crashId, lists recent crashes. With crashId, returns the full crash log with stack trace.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bundleId | string | yes | — |
| crashId | string | no | — |
| limit | number | no | — |
Fetch screenshot feedback from TestFlight. Returns feedback metadata including device info, user comments, and screenshot URLs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bundleId | string | yes | — |
| limit | number | no | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- 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 or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.0.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish Expo can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.