← Explore all mcp servers

MOBILE DEVELOPMENT / Expo

Expo Development MCP

Connects assistants to Expo documentation, EAS operations and optional local simulator or DevTools capabilities.

“Expo MCP Server is a remote MCP server hosted by Expo”

01 / THE REASONING

Why this made the selection.

  • Separates hosted operations from local development tools.
  • Documents workflow, build and store-operation boundaries.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • https://docs.expo.dev/mcp/
  • https://docs.expo.dev/mcp.md
  • Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.

Our findings

  • Remote tools remain available without local simulator access.
  • Build logs require a completed build; workflow execution uses a workflow present at the chosen Git reference.
  • MCP lane cross-review compared retained publisher setup/capability evidence with this proposed record before integration; no installation or authenticated calls were performed.
  • Local screenshots and development data are proxied through the hosted Expo MCP service; they are not confined to a local MCP connection.

Not established by this review

  • Authentication, live tool execution, hosted implementation and security isolation were not tested.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Connect a server deliberately.

Upstream setup instructions ↗
  1. Connect through OAuth with the intended Expo account.
  2. For local tools, install expo-mcp and start Expo with EXPO_UNSTABLE_MCP_SERVER=1 using the same account.
  3. Reconnect after starting or stopping the development server.
  4. Install expo-mcp as a development dependency and start the supported development server path for local capabilities, then refresh the client after starting or stopping it.

Before you start

  • Expo account and compatible project.
  • Local capabilities require the documented development environment.

Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

{
  "mcpServers": {
    "expo": {
      "type": "http",
      "url": "https://mcp.expo.dev/mcp"
    }
  }
}

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://docs.expo.dev/mcp/

    Supports: summary, upstreamDescription, whySelected, bestFor, limitations, review, install, access, compatibility, transports, configExample

  2. https://docs.expo.dev/mcp.md

    Supports: summary, upstreamDescription, whySelected, bestFor, limitations, review, install, access, compatibility, transports, configExample

Evidence & Ask