expo

This Expo MCP Server provides a programmable interface to manage Expo and EAS workflows through AI assistants. It exposes a suite of tools for project setup, dependency management, OTA updates, cloud builds, and app submission, all accessible via MCP resource calls. You can initialize Expo projects, install packages with version checks, generate native code, trigger and monitor EAS cloud builds, publish OTA updates to channels, and submit builds to App Store Connect or Google Play Console. The server also includes diagnostics and authentication helpers to keep projects healthy and securely connected to Expo services. Use the provided commands and tool names (e.g., expo_init_project, eas_build_create, eas_update_publish, eas_submit_ios) to instruct the agent to perform specific tasks.

To get started with Expo MCP Server, configure your MCP client to point to the expo-dev server, authenticate with your Expo access token, and then issue tool calls as structured actions. Tools return structured results (and logs where available) to help you iterate quickly on development, builds, and submissions.

Prerequisites:

• Node.js 18+ installed on your machine
• npm or pnpm package manager
• An Expo account with a valid access token

Installation steps:

1. Install the MCP server via Smithery integration or npm install approach as described in the repo documentation. For quick setup, you can install the server package and start using it with the MCP config below.
2. Ensure you have an Expo access token ready for authentication with expo.dev APIs.
3. Create or update your MCP config to point to the Expo MCP Server (see mcp_config in this document).

Example commands:

• Quick install via Smithery (from README): npx @smithery/cli install expo-mcp-server

• Local development clone and run (from repository): git clone https://github.com/CaullenOmdahl/expo-mcp-server cd expo-mcp-server npm install npm run build npm run dev # Run with Smithery playground

Environment setup:

• Create an Expo access token at https://expo.dev/settings/access-tokens and store it securely.
• Set EXPO_TOKEN in your MCP environment as described in the mcp_config section.

Tips and considerations:

• The server requires an Expo access token; ensure it has appropriate scopes for the tasks (builds, submissions, etc.).
• When using EAS Build and Submit tools, keep your credentials and project IDs ready; some operations may require additional project configuration (app.json/app.config.js, eas.json).
• Tools support both markdown and json outputs; request json if you need structured data for automation.
• If you encounter build or submission failures, check logs exposed by the tool calls (especially for authentication, project configuration, and native code generation steps).
• For local development, ensure Node.js 18+ is installed and that your environment variables (like EXPO_TOKEN) are not exposed in logs.