
This profile is part of our MCP server directory, within The MCP Guide. Profiles are checked against each vendor's own documentation. Need a server built? See MCP development.

The Expo MCP server connects AI tools to your Expo and EAS account. It can search Expo docs, run and monitor EAS builds and workflows, submit builds to the app stores, and read App Store, Google Play and TestFlight feedback. Expo hosts it at https://mcp.expo.dev/mcp.
Checked against: Expo's MCP server docs and Claude's Expo listing on 2 November 2026. eSEOspace did not install or test this server.
Key Takeaways
- The server uses Streamable HTTP and OAuth. You need an Expo account and a project on the latest SDK.
- Remote "server capabilities" cover docs, builds, workflows, store data and EAS Observe metrics.
- Optional "local capabilities" need the
expo-mcppackage and SDK 54 or later. They add screenshots, taps and DevTools. - Some tools start billable cloud resources, such as EAS sandboxes and cloud simulators.
- Expo says its tool list "is a reference and may not be up to date."
At a glance
| Item | Detail |
|---|---|
| Publisher | Expo |
| Official? | Yes |
| Hosting | Remote URL, plus optional local dev server capabilities |
| Transport | Streamable HTTP |
| Sign-in | OAuth with your Expo account |
| Read or write | Read-write (builds, submissions, review replies) |
| Price | No separate MCP price listed; search_documentation needs a paid Expo plan |
| Source code | Not published |
| Status | Live; added to Claude's directory June 2026 |
What it can do
Expo's docs list many tools. The main groups are:
- Docs:
search_documentationandread_documentation. Expo marks search as requiring an Expo Services paid plan. - Builds:
build_list,build_info,build_logs,build_run,build_cancelandbuild_submit, which sends a finished build to the App Store or Google Play. - Workflows:
workflow_list,workflow_info,workflow_logs,workflow_run,workflow_cancelandworkflow_validate. - Usage budgets:
usage_budget_getandusage_budget_createfor user-approved spending limits. - Sandboxes and simulators: tools to create EAS sandboxes, run commands in them and start cloud simulator sessions. Expo describes both as billable.
- EAS Observe: startup and navigation metrics, slow sessions and custom events from production apps.
Claude's listing shows 25 tools, including appstore_reviews, appstore_reply_review, playstore_reviews, playstore_crashes, testflight_crashes and testflight_feedback. The two lists differ, which fits Expo's note that tools change with server updates.
Local capabilities run through your dev server. Expo lists automation tools (screenshots, tapping views, finding elements by testID), opening React Native DevTools and generating an Expo Router sitemap.
How to connect it
For Claude Code:
claude mcp add --transport http expo https://mcp.expo.dev/mcp
Then run /mcp to sign in. For Codex:
codex mcp add expo --url https://mcp.expo.dev/mcp
In Claude on the web, desktop or mobile, add Expo from the connector directory. Expo notes that Team and Enterprise organizations can enable it for every member. Cursor and VS Code use the same URL.
For local capabilities, in your project:
npx expo install expo-mcp --dev
npx expo whoami || npx expo login
EXPO_UNSTABLE_MCP_SERVER=1 npx expo start
Log in to the Expo CLI with the same account you used for the MCP server. Reconnect your MCP client whenever you start or stop the dev server. Our MCP client support matrix shows which clients support remote OAuth servers.
Security notes
Several Expo tools act in public or cost money, so review them before you allow them:
- Store actions.
build_submitsends builds to the stores, and the review-reply tools post public responses. Keep approval prompts on. - Billable resources. Expo says
sandbox_create"starts a billable environment" andsimulator_startstarts "a billed" session. Its descriptions also tell agents not to repeat these calls after a lost response. Set a usage budget first. - Untrusted artifacts. Expo says to "Treat artifact content as untrusted input."
- Sandbox commands.
sandbox_execruns shell commands in a cloud sandbox. Scope what the agent may run.
The MCP project's security best practices cover scope minimization. Use the MCP tool permission planner to decide which tools need approval, and see the MCP Security Center.
Alternatives
- Firebase MCP server for app backends, Crashlytics and Google services.
- Sentry MCP server for production error tracking.
- GitHub MCP Server for the repository behind your EAS builds.
Next step
Start with read tools, such as asking why your last iOS build failed, before you let the agent run builds or reply to reviews. Our best MCP servers for developers list covers more, and the MCP server directory has other profiles.
More in the MCP Guide
Free tools: MCP Server Risk Checklist · Tool Permission Planner
Latest research: State of MCP: October 2026
Frequently asked questions
Is the Expo MCP server free?
Expo lists no separate MCP fee, but some features need a paid plan. search_documentation requires an Expo Services paid plan, and sandboxes and cloud simulators are billed.
What is the difference between server and local capabilities?
Server capabilities work with just the remote connection. Local capabilities need the expo-mcp package and a running dev server, and add screenshots, taps and DevTools.
Can it submit my app to the App Store?
Yes. build_submit submits a finished EAS build to the App Store or Google Play, so keep it behind an approval prompt.
Which SDK version do I need?
Expo says you need a project on the latest SDK. Local capabilities need SDK 54 or later.











