Expo MCP Server
Enables programmatic interaction with Expo/React Native projects and EAS (Expo Application Services) for managing builds, publishing OTA updates, submitting apps to stores, and accessing comprehensive documentation.
README
Expo MCP Server
Model Context Protocol (MCP) server for Expo.dev that enables programmatic interaction with Expo projects and EAS (Expo Application Services).
Overview
This MCP server provides comprehensive tools for managing Expo/React Native projects, including:
- Project Management: Initialize projects, install packages, configure apps
- Development Workflow: Run diagnostics and health checks
- EAS Build: Create, monitor, and manage cloud builds for iOS and Android
- EAS Update: Publish over-the-air updates and manage update channels
- EAS Submit: Submit builds to App Store and Google Play
- Documentation Access: Direct links to official Expo and React Native documentation
Features
Tools
Project Management:
expo_init_project- Create new Expo projects with templatesexpo_install_packages- Install packages with automatic version validationexpo_get_config- View and validate app configurationexpo_prebuild- Generate native iOS/Android project directories
Development:
expo_doctor- Run comprehensive project diagnostics
EAS Build:
eas_build_create- Trigger cloud builds for iOS, Android, or botheas_build_list- List recent builds with filteringeas_build_status- Get detailed build status and logseas_build_cancel- Cancel in-progress builds
EAS Update (OTA):
eas_update_publish- Publish over-the-air updates to branches/channelseas_update_list- List published updateseas_channel_create- Create update channels for distribution
EAS Submit:
eas_submit_ios- Submit iOS builds to App Store Connect/TestFlighteas_submit_android- Submit Android builds to Google Play Console
Information:
expo_whoami- Check authentication statuseas_project_info- Get EAS project configuration and metadata
Resources
The server exposes documentation resources that link to official Expo and React Native docs:
Expo Documentation:
expo://docs/llms- Complete Expo documentation (LLM-optimized)expo://docs/eas-build- EAS Build guideexpo://docs/eas-update- EAS Update guideexpo://docs/eas-submit- EAS Submit guideexpo://docs/cli-reference- Expo CLI referenceexpo://docs/development-builds- Development builds guideexpo://docs/programmatic-access- Authentication and API accessexpo://docs/config-plugins- Config plugins guideexpo://docs/debugging- Debugging guide
React Native Documentation:
expo://docs/react-native/llms- React Native docs (LLM-optimized)expo://docs/react-native/troubleshooting- Troubleshooting guideexpo://docs/react-native/debugging- Debugging guide
Installation
Using Smithery (Recommended)
npx @smithery/cli install expo-mcp-server
From Source
git clone <repository-url>
cd expo-mcp-server
npm install
npm run build
Configuration
Authentication
The server requires an Expo access token for EAS operations. You can provide it in two ways:
- Environment Variable (recommended):
export EXPO_TOKEN=your_token_here
- Server Configuration:
{
"expoToken": "your_token_here",
"defaultFormat": "markdown"
}
To create an access token:
- Visit https://expo.dev/settings/access-tokens
- Create a new token
- Set it as
EXPO_TOKENenvironment variable
MCP Client Configuration
Add to your MCP client settings (e.g., Claude Code):
{
"mcpServers": {
"expo-dev": {
"command": "npx",
"args": ["-y", "expo-mcp-server"],
"env": {
"EXPO_TOKEN": "your_token_here"
}
}
}
}
Usage Examples
Create a New Expo Project
// Use the expo_init_project tool
{
"projectName": "my-awesome-app",
"template": "blank-typescript",
"format": "markdown"
}
Trigger a Production Build
// Use the eas_build_create tool
{
"platform": "all",
"profile": "production",
"format": "markdown"
}
Publish an OTA Update
// Use the eas_update_publish tool
{
"branch": "production",
"message": "Fix critical authentication bug",
"format": "markdown"
}
Check Build Status
// Use the eas_build_status tool
{
"buildId": "abc-123-def-456",
"format": "markdown"
}
Output Formats
All tools support two output formats:
markdown(default): Human-readable tables and formatted textjson: Structured data for programmatic processing
Error Handling
The server provides actionable error messages with:
- Clear descriptions of what went wrong
- Suggested next steps for resolution
- Links to relevant documentation resources
- Context-specific troubleshooting guidance
Common errors include:
- Authentication errors: Points to programmatic access documentation
- Build failures: Links to EAS Build troubleshooting
- Configuration errors: Suggests config validation steps
- React Native errors: Links to RN troubleshooting guides
Requirements
- Node.js: 18.0.0 or higher
- Expo Account: Required for EAS operations
- Access Token: For programmatic API access
Development
# Install dependencies
npm install
# Build the server
npm run build
# Run in development mode with Smithery playground
npm run dev
Architecture
The server is built with:
- TypeScript: Type-safe implementation
- MCP SDK: Official Model Context Protocol SDK
- Zod: Runtime schema validation
- execa: CLI command execution
Project Structure
src/
├── index.ts # Main server entry point
├── types.ts # Shared types and schemas
├── resources/
│ └── documentation.ts # Documentation resource registrations
├── tools/
│ ├── project.ts # Project management tools
│ ├── development.ts # Development workflow tools
│ ├── build.ts # EAS Build tools
│ ├── update.ts # EAS Update tools
│ ├── submit.ts # EAS Submit tools
│ └── info.ts # Information tools
└── utils/
├── cli.ts # CLI execution utilities
├── format.ts # Response formatting
├── parse.ts # Output parsing
└── errors.ts # Error handling
Contributing
Contributions are welcome! Please:
- Fork the repository
- Create a feature branch
- Make your changes
- Add tests if applicable
- Submit a pull request
License
MIT License - see LICENSE file for details
Resources
Support
For issues and questions:
- GitHub Issues: [Create an issue]
- Expo Forums: https://forums.expo.dev/
- Expo Discord: https://chat.expo.dev/
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.