A coding assistant that knows Expo and checks its own work.

Mobile developers get an assistant that can see the results of its changes, reading EAS build logs, installing libraries at compatible versions, and tapping and screenshotting the running app.

What it is

A remote MCP server Expo hosts at mcp.expo.dev/mcp, for Claude, Claude Code, Cursor, VS Code and other AI tools. It works on your Expo projects through your own Expo account. Some tools run against Expo's EAS build service; a second set needs a local development server on your machine.

What you get

The latest Expo documentation searched and read on demand
Expo libraries installed at compatible versions, with usage notes
EAS builds started, cancelled, inspected and their logs read; finished builds submitted to the App Store or Google Play
EAS workflows created, checked, run and debugged from their logs
TestFlight and Google Play crash reports and user feedback pulled in
App Store and Google Play reviews read and publicly answered
With a local dev server: screenshots of the running app, taps on its views, app logs and React Native DevTools

Requirements

An Expo account, an Expo project on the latest SDK, and an AI tool with remote MCP support; you sign in to Expo in your browser.
The local testing tools need SDK 54 or later, the expo-mcp package, and a dev server started with MCP turned on.
Searching the docs needs an EAS paid plan.
Replies it posts to App Store or Google Play reviews are public and replace any earlier reply.
Restart the MCP connection whenever you start or stop the dev server, so the local tools appear.

Setup effort

Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen