1. Conduid
  2. Blockchain
  3. Expo Dev Assistant
MCP server · Blockchain

Expo Dev Assistant

Manage Expo and React Native projects from setup to release. Trigger cloud builds, publish over-the-air updates, and submit releases to App Store and Google Play with clear status and logs. Run diagnostics, validate configuration, and access relevant docs to resolve issues faster.

Unclaimed last commit 10 months ago blockchain
34Low

Scored 7 months ago · breakdown

About Expo Dev Assistant

Expo Dev Assistant is an MCP server published by CaullenOmdahl in the Blockchain category: manage Expo and React Native projects from setup to release. Trigger cloud builds, publish over-the-air updates, and submit releases to App Store and Google Play with clear status and logs. Run diagnostics, validate configuration, and access relevant docs to resolve issues faster.

The repository has 6 stars and 3 forks, with the last commit 10 months ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/CaullenOmdahl/expo-mcp-server

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Expo Dev Assistant

Powered by Claude · Grounded in docs

I know everything about Expo Dev Assistant. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ✓README presentThe repository ships documentation.

5 checks have not been run yet.

README

Expo MCP Server

npm version MCP

Model Context Protocol server for Expo.dev — programmatically manage Expo projects and EAS services through AI assistants like Claude.

What It Does

This MCP server gives AI assistants full control over Expo/React Native development workflows:

Category Capabilities
Project Setup Initialize projects, install packages, configure apps, generate native code
Cloud Builds Trigger iOS/Android builds, monitor progress, view logs, cancel builds
OTA Updates Publish updates to branches, manage channels, instant deployments
App Submission Submit to App Store Connect and Google Play Console
Diagnostics Run health checks, validate configurations

Quick Start

Install via Smithery

npx @smithery/cli install expo-mcp-server

Or Add to MCP Config

{
  "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

Tools

Project Management

  • 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

  • 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 (OTA)

  • eas_update_publish — Publish over-the-air updates
  • eas_update_list — List published updates
  • eas_channel_create — Create update channels

EAS Submit

  • eas_submit_ios — Submit to App Store Connect/TestFlight
  • eas_submit_android — Submit to Google Play Console

Utilities

  • expo_doctor — Run project diagnostics
  • expo_whoami — Check authentication status
  • eas_project_info — Get EAS project metadata

Resources

The server exposes documentation as MCP resources:

expo://docs/llms           # Complete Expo docs (LLM-optimized)
expo://docs/eas-build      # EAS Build guide
expo://docs/eas-update     # EAS Update guide
expo://docs/eas-submit     # EAS Submit guide
expo://docs/cli-reference  # Expo CLI reference

Example Workflows

"Build my app for both platforms"

→ eas_build_create(platform: "all", profile: "production")

"Push a hotfix to production"

→ eas_update_publish(branch: "production", message: "Fix auth bug")

"Submit the latest build to TestFlight"

→ eas_submit_ios(buildId: "abc-123")

Output Formats

All tools support:

  • markdown (default) — Human-readable tables
  • json — Structured data for processing

Development

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

Architecture

src/
├── index.ts              # Server entry point
├── types.ts              # Shared schemas
├── resources/            # Documentation resources
├── tools/                # Tool implementations
│   ├── project.ts        # Project management
│   ├── build.ts          # EAS Build
│   ├── update.ts         # EAS Update
│   └── submit.ts         # EAS Submit
└── utils/                # CLI execution, formatting

Built with TypeScript, MCP SDK, and Zod validation.

Requirements

  • Node.js 18+
  • Expo account with access token

Links

License

MIT

README copy captured when this server was indexed; it may lag the repository. The original is authoritative.

Questions

About Expo Dev Assistant

How do I install Expo Dev Assistant?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Expo Dev Assistant safe to use with an AI agent?

Its trust score is 34 out of 100 (low). It passes 1 of the 1 static security checks run so far. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Expo Dev Assistant still maintained?

The last commit was 10 months ago. That's long enough that you should check whether the maintainer is responding to issues before depending on it.