Expo
by Expo
Start EAS builds, run CI/CD workflows and reply to App Store reviews from your AI assistant. 25 tools, OAuth sign-in on a single mcp:access scope, and a build_run tool that spends real money.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Expo via MCP
https://mcp.expo.dev/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Expo Tools & Capabilities (25)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- One scope, no read-only option.
mcp:accessis all-or-nothing, as described above. search_documentationneeds a paid EAS plan. Expo's MCP tool table marks it "Server (requires an EAS paid plan)"; the other 24 carry no plan marking.- Free is "fair use limited". Expo's plan comparison marks the MCP Server row as "Fair use limited" on Free and a plain checkmark on the three paid tiers. Expo publishes no numeric MCP rate limit, and its
/eas/fair-uselink redirects to the general Acceptable Use Policy, which carries no MCP figures. build_runneeds GitHub. Expo documents the tool as requiring a connected GitHub repository.- Builds queue rather than parallelise. One concurrency on Free and Starter, two on Production, five on Enterprise; extras are $50 each, up to five extra.
- Build timeouts differ by plan. 45 minutes on Free, two hours on paid plans. Free builds also use the low-priority queue, where Expo warns peak waits can exceed 90 minutes.
- 50 pending builds per platform per account. New builds are rejected past that.
- Google Play reviews are roughly one week deep, and only production reviews with text.
- Local capabilities are macOS-and-simulator only on iOS, support a single dev server at a time, and require SDK 54 or later.
- Reaching the public App Store still needs a human.
build_submitgets a build into App Store Connect and TestFlight; App Review is a separate manual step. On Google Play, the destination track and rollout come from youreas.jsonsubmission profile, not from the tool call — a profile configured for the production track will submit there. - No tool schemas or safety annotations were read. The server is OAuth-gated. Everything above comes from Expo's documentation and Anthropic's directory listing.
Frequently asked questions
Which Expo plan do you need to use the Expo MCP server?
Any plan, including Free. Expo's pricing comparison lists the Expo MCP Server as included on all four tiers, marked Fair use limited on Free and a plain checkmark on Starter, Production and Enterprise. One tool is gated separately: Expo's MCP documentation marks search_documentation as requiring an EAS paid plan, so Free accounts get the other twenty-four.
What happens when I use up the Free plan's monthly quota?
New builds stop until the calendar month resets. Expo's billing FAQ states that Free plan accounts do not incur overage charges, and that once the monthly quota of free builds is used, new builds are unavailable until the quota resets on the first day of the next calendar month. The documented alternatives are upgrading to Starter or running builds locally.
How much does an EAS build started by an agent cost?
Between one and four dollars per build on a paid plan. Expo's pricing page charges a flat rate per build by platform and worker size: one dollar for a medium Android build, two for a large Android or medium iOS build, and four for a large iOS build. Builds cancelled before any work is done are not charged.
How do I increase build concurrencies on my account?
Buy them as an add-on, which requires a paid plan. Expo's billing FAQ directs paid subscribers to the Add-ons section under Billing, and tells Free plan users to set up a paid subscription first. Expo's pricing page lists one concurrency on Free and Starter, two on Production and five on Enterprise, at fifty dollars per extra concurrency.
Can the Expo connector publish an app to the App Store on its own?
No. Expo's iOS submission guide states that a submitted build appears in TestFlight after processing, and that releasing to production requires signing in to App Store Connect and submitting the build for App Review. On Android, Expo documents that a first submission creates a release on the internal testing track and the app stays in draft until you complete the store listing.
Can a reply an agent posts to an App Store review be undone?
It can be edited or deleted, but not silently. Apple's App Store Connect help states that only one response per review appears on your product page, that responses may take up to twenty-four hours to appear, and that edited responses carry a notation indicating they have been edited. The connector exposes appstore_delete_review_response for removal.
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Developer Tools
- Developer
- Expo
- Tools
- 25
- Domain
- mcp.expo.dev
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.