PlugWiki

Expo MCP Server, Expo's hosted MCP server

OfficialRemote

Lets Claude Code, Cursor or Claude read Expo docs, run and fix EAS builds, and test your app in a simulator. Sign in with your Expo account.

This is Expo's own connection for AI coding assistants, and Expo runs it for you. Your assistant can read current Expo docs, start and check EAS builds and workflows, look at crash reports and app performance, and, with a small package in your project, take screenshots and tap through your app in a simulator. It can also submit builds to the stores and reply to app reviews in public, and some tools cost money, so check each action before you approve it.

Good for

  • React Native developers building with Expo in Claude Code, Cursor, VS Code or Codex
  • Teams on EAS who want an assistant to start builds and explain why one failed
  • Developers who want the assistant to check its UI changes with screenshots and taps
  • App owners tracking crashes, startup speed and store reviews after a release

Works in

5 supported · 9 should work

Tap an app to see how to set it up and any known problems.

Install Expo MCP

Claude Code

  1. 1

    Copy this prompt.

    Add the Expo MCP server to Claude Code. Run this command:
    
    claude mcp add --transport http expo https://mcp.expo.dev/mcp
    
    Then check that it loaded and tell me if I need to sign in or restart.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires An Expo account, Sign-in with your Expo account.

Run /mcp in Claude Code to sign in. If you installed Expo's expo plugin, it already adds this server; just run /mcp. For screenshots, taps and logs, also add the local tools to your project (SDK 54 or later): run npx expo install expo-mcp --dev, make sure npx expo whoami shows the same Expo account, then start the dev server with EXPO_UNSTABLE_MCP_SERVER=1 npx expo start. Reconnect the server in your AI app whenever you start or stop the dev server.

From the vendor's docs. Source.

Tools

  • Searches the official Expo docs for pages about your question

    Searches Expo's documentation and returns the most relevant pages. Needs an EAS paid plan.

    Try: “Search the Expo docs for implementing deep linking”

    Read · search_documentation

  • Reads one Expo docs page in full

    Fetches a single Expo documentation page as text, in parts for long pages.

    Try: “Read the Expo Router docs page”

    Read · read_documentation

  • Lists recent EAS builds for a project and their status

    Lists the EAS builds for a project, with their status and download links.

    Try: “List the recent builds for this project”

    Read · build_list

  • Shows the status and details of one build

    Gets the status, errors and files of a specific EAS build.

    Try: “Get the status of my latest iOS build”

    Read · build_info

  • Reads the logs of a finished or failed build

    Fetches the logs of an EAS build once it has finished or failed.

    Try: “Show me the logs for the failed build”

    Read · build_logs

  • Starts a new EAS build from a build profile

    Starts a new EAS build using a profile from eas.json. The project needs a connected GitHub repository.

    Try: “Run a production build for iOS”

    Write · build_run

  • Cancels a build that is queued or running

    Cancels an EAS build that has not finished yet.

    Try: “Cancel the build that is currently in progress”

    Write · build_cancel

  • Submits a finished build to the App Store or Google Play

    Sends a finished EAS build to the App Store (iOS) or Google Play (Android) for release.

    Try: “Submit the latest build to the App Store”

    Write · build_submit

  • Lists recent EAS workflow runs for a project

    Lists the latest EAS workflow runs for a project.

    Try: “List the recent workflow runs”

    Read · workflow_list

  • Shows the status, jobs and errors of a workflow run

    Gets the status, job results, errors and files of an EAS workflow run.

    Try: “Get the status of the latest workflow run”

    Read · workflow_info

  • Reads the logs of a job in a workflow run

    Fetches the logs for one job in an EAS workflow run, a section at a time.

    Try: “Show me the logs for the build job in the workflow”

    Read · workflow_logs

  • Starts an EAS workflow from a branch or commit

    Runs an EAS workflow from a git branch, tag or commit where the workflow file exists.

    Try: “Run the build-and-deploy workflow”

    Write · workflow_run

From the official docs

Pros and cons

Good

  • Built and run by Expo, with nothing to install for the main features.
  • Your assistant reads current Expo docs instead of guessing from old training data.
  • It can find out why an EAS build or workflow failed and read its logs.
  • With the local package, it checks its own UI changes with screenshots and taps.
  • It pulls crash reports, startup metrics and store reviews into the chat.

Watch out

  • Searching the docs needs an EAS paid plan.
  • Cloud sandboxes and simulator sessions are billed.
  • Local iOS tools work only in simulators on a Mac.
  • Windows users report the local automation tools failing.
  • Only one development server can be connected at a time.
  • Expo says the tools may change without notice.

Permissions

medium risk · 5 things to watch

Medium risk

Your assistant can start builds, submit apps to the stores, post public replies to reviews and start cloud machines that cost money, all from your Expo account. Turn on your AI app's setting that asks before each action, and read every store reply before you approve it.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • It can start builds and submit to the stores

    It can run and cancel EAS builds and workflows, and send a finished build to the App Store or Google Play. Approve these one at a time. docs.expo.dev

  • It can post public replies to app reviews

    Replies on the App Store and Google Play are public and replace any earlier reply. The first call shows a preview, so read it before you confirm. docs.expo.dev

  • Some tools cost money

    Cloud sandboxes and EAS Simulator sessions are billed. Set a usage budget and stop sessions you no longer need. docs.expo.dev

  • It can run commands in cloud sandboxes

    It can run shell commands inside an EAS sandbox it starts. Check commands before you approve them. docs.expo.dev

  • Screenshots pass through Expo's server

    Local screenshots and logs travel through Expo's server to your AI app. Expo says it does not train AI models on this data. docs.expo.dev

Security advisories

No published security advisories as of Nov 1, 2026.

Technical details
Talks tomcp.expo.dev; local screenshots and logs are proxied through Expo's server to your AI app
Sign-in and keysAccess token generated after browser sign-in with your Expo account, kept by your AI app.
Data retentionExpo says it does not use data sent to the MCP server to train AI models; your AI app and its model provider apply their own retention.
Scopes
  • Expo account access via OAuth sign-in: projects, EAS builds, workflows, Observe data, TestFlight and store data the account can reach

Alternatives

Use Expo's own server; it is the only one that reaches your EAS builds, crash data and store reviews. Add Expo Agent Bridge only if you want the assistant to tap through your app on a real phone.

ServerOfficialRunsSign-inToolsPopularity
Expo MCP ServerThis pageOfficialHostedExpo account53–
Expo Agent BridgeCommunityLocal––182/wk

What people say

People find it helpful to have current Expo knowledge in their assistant, and most complaints are about the local simulator tools on Windows.

What people like

  • Gives the assistant current Expo docs and patterns

Common complaints

  • Local automation tools fail on Windows
  • Cannot choose which device to use when several simulators are running
  • Workflow runs cannot pass custom inputs

In their words

Questions

What is the Expo MCP server URL?

https://mcp.expo.dev/mcp. You sign in with your Expo account in the browser the first time.

Is Expo MCP free?

Mostly. You need an Expo account, and searching the docs needs an EAS paid plan. Cloud sandboxes and simulator sessions are billed.

Do I need to install expo-mcp in my project?

Only for the local tools, such as screenshots, taps, app logs and DevTools. They need SDK 54 or later and a dev server started with MCP turned on, as shown in the install box.

Why don't the screenshot and tap tools show up?

They only appear while your dev server runs with MCP turned on. Reconnect the server in your AI app each time you start or stop the dev server.

Does it work on Windows or with a real iPhone?

The connection works anywhere, but local iOS tools need a Mac and a simulator, not a physical iPhone. Windows users report the local automation tools failing.

Can it submit my app to the App Store?

Yes. It can send a finished EAS build to the App Store or Google Play, so approve that step yourself.

Is it safe to connect Expo to my AI assistant?

It acts on your Expo account and can post public review replies and start paid sessions. Keep your AI app asking before each action, and read previews before you confirm.

Does Expo train AI on my data?

No. Expo says it does not use data sent to the MCP server to train models, but your AI app's provider has its own rules.

Examples

  • Find out why the latest iOS build failed

    Investigate why my most recent iOS build on EAS failed

    Source
  • Check startup speed after a release

    Did startup get slower in the latest release?

    Source
  • Build a UI change and check it with a screenshot

    Add a blue circle view and make sure it renders correctly

    Source
  • Review recent TestFlight crashes

    Show me recent TestFlight crashes

    Source

Information

updated Nov 2, 2026

Publisher
Official
Transport
Streamable HTTP
Auth
OAuth
Last commit
Jul 29, 2026

DocsGitHubnpmIn the Claude directory

Other Expo MCP servers

Sources

Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.

Show all 6
  1. Using Model Context Protocol (MCP) with Expo · docs.expo.dev
  2. GitHub · github.com
  3. GitHub · github.com
  4. Hacker News · news.ycombinator.com
  5. GitHub · github.com
  6. GitHub · github.com

Facts from the official MCP registry, GitHub, npm, PyPI and the Docker catalog. Updated Nov 2, 2026.