Expo

Model Context Protocol server for Expo.dev - enables programmatic interaction with Expo projects and EAS services
  • javascript

4

GitHub Stars

javascript

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

You can use the Expo MCP Server to programmatically manage Expo and EAS workflows through AI assistants, enabling project setup, cloud builds, OTA updates, app submissions, and health checks from a single MCP Endpoint or local process.

How to use

You interact with the MCP server through an MCP client that exposes a set of labeled actions. These actions span project creation, package management, configuration validation, native code generation, triggering cloud builds, publishing OTA updates, submitting builds to app stores, and running diagnostics. You can combine actions to automate end-to-end workflows, such as initializing a project, prebuilding native directories, kicking off a mobile build, publishing an update to a channel, and submitting the latest build for review.

How to install

Prerequisites you need before installing and using the MCP server are a Node.js runtime and a valid Expo account with an access token.

# Install the MCP server client via Smithery (recommended single command setup)
npx @smithery/cli install expo-mcp-server

# Or add to your MCP configuration using the example below
{
  "mcpServers": {
    "expo-dev": {
      "command": "npx",
      "args": ["-y", "expo-mcp-server"],
      "env": {
        "EXPO_TOKEN": "your_token_here"
      }
    }
  }
}

Get your token at expo.dev/settings/access-tokens.

## Configuration and usage notes

The MCP server supports a collection of tools that map to Expo and EAS workflows. You can run them via an MCP client to perform project setup, builds, updates, and submissions. The server exposes documentation resources for quick reference, and you can monitor build progress, view logs, and cancel builds when needed.

## Examples of common workflows

Build my app for both platforms: trigger cloud builds for iOS and Android in production profile.

Push a hotfix to production: publish an OTA update to the production channel with a descriptive message.

Submit the latest build to TestFlight: submit iOS build metadata to App Store Connect for review.

## Available tools

### expo\_init\_project

Create new Expo projects with templates.

### expo\_install\_packages

Install packages with version validation.

### expo\_get\_config

View and validate app configuration.

### expo\_prebuild

Generate native iOS/Android directories.

### eas\_build\_create

Trigger cloud builds (iOS, Android, or both).

### eas\_build\_list

List builds with filtering.

### eas\_build\_status

Get build status and logs.

### eas\_build\_cancel

Cancel in-progress builds.

### eas\_update\_publish

Publish over-the-air updates.

### eas\_update\_list

List published updates.

### eas\_channel\_create

Create update channels.

### eas\_submit\_ios

Submit to App Store Connect/TestFlight.

### eas\_submit\_android

Submit to Google Play Console.

### expo\_doctor

Run project diagnostics.

### expo\_whoami

Check authentication status.

### eas\_project\_info

Get EAS project metadata.
Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational