Skip to content

Summary

Expo's official remote MCP server — searches Expo docs, installs compatible SDK packages, triggers and monitors EAS builds, and drives iOS/Android simulators.

Features

  • Hosted remote server at https://mcp.expo.dev/mcp over Streamable HTTP with OAuth
  • Fetches and searches current Expo SDK documentation on demand
  • Installs compatible dependency versions through npx expo install
  • Triggers and monitors EAS builds and workflows
  • Pulls TestFlight crash data, tester feedback and App Store reviews
  • Local mode drives simulators: screenshots, tap and testID lookup, app logs
  • React Native DevTools integration and Expo Router sitemap generation
  • Available on the Free plan with a monthly usage allowance

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it.
  3. Restart the agent — the "Expo MCP Server" tools will be available.
{
  "mcpServers": {
    "expo-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.expo.dev/mcp"
      ]
    }
  }
}

Description

The Expo MCP Server is the official Model Context Protocol server from Expo, the team behind the React Native framework and the EAS build service. It is aimed at developers who build native iOS and Android apps with Expo and want their coding agent to work against the real project rather than from memory of an SDK version that has since moved on.

It runs as a hosted remote server over Streamable HTTP at https://mcp.expo.dev/mcp, authenticated with OAuth against an Expo account, so there is nothing to install to get the server-side half of it. Those hosted tools cover four jobs: fetching and searching the current Expo documentation on demand, resolving dependencies through npx expo install so the agent picks versions that are actually compatible with the project's SDK, triggering and monitoring EAS builds and workflows, and pulling TestFlight crash reports, tester feedback and App Store reviews back into the conversation.

A second, local half unlocks once the project adds the expo-mcp dev dependency (Expo SDK 54 or newer) and the dev server is started with EXPO_UNSTABLE_MCP_SERVER=1 npx expo start. That gives the agent a running simulator to work with: it can capture screenshots, tap and find elements by testID, read app logs, attach to React Native DevTools, and generate an Expo Router sitemap. The practical effect is that an agent can make a change and then look at the result, instead of reporting a fix it never saw render.

Expo lists Claude (web, desktop and mobile), Claude Code, Cursor, VS Code and Codex as supported clients, and publishes a Claude Connector that needs no local install at all. An Expo account is required. Since the 26 May 2026 changelog the server is available on the Free plan with a monthly usage allowance shared across a billing account, though search_documentation still requires a paid EAS plan.

Related MCP Servers

MCP: Hugging Face

by Hugging Face

Hugging Face's official MCP server — search the Hub's models, datasets and Spaces, read repository files, and call thousands of Gradio applications as tools from one remote endpoint.

JFrog's official remote MCP server: 100+ tools across Artifactory, Xray and Curation, hosted on JFrog Cloud with OAuth and no client install.

Appwrite's official MCP server exposes databases, users, teams, functions and storage as agent tools, over a hosted OAuth endpoint or a local stdio bridge.

Glide's official remote MCP server for GlideOS — create projects, publish and roll back apps, query and modify app databases, run workflows, and read or write project files and backend code.

Browse all MCP servers →