# Expo MCP server

> Search Expo docs, manage EAS builds and workflows, and test React Native apps in a simulator from your AI assistant.

- Listing: https://mcp.tc/i/expo
- Connect: use the server's own URL `https://mcp.expo.dev/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Developer Tools](https://mcp.tc/c/developer-tools)
- Vendor: Expo
- Homepage: <https://docs.expo.dev/mcp/>

## About

Expo MCP Server gives AI assistants access to the Expo SDK documentation and your Expo projects. It can fetch current docs on demand, install compatible packages with npx expo install, trigger and monitor EAS builds, run workflows, and pull TestFlight crash data and feedback. With the expo-mcp package in a project, it can also screenshot and interact with the running app in a simulator.

It runs as a hosted remote server at https://mcp.expo.dev/mcp using streamable HTTP. Users sign in with an Expo account through OAuth. Some tools require an EAS paid plan. The local simulator features need the expo-mcp package added to the project's dependencies.

## What it can do

- Search and read the latest Expo documentation
- Install compatible Expo packages with npx expo install
- Trigger and monitor EAS builds
- Run and inspect EAS workflows
- View TestFlight crashes and feedback
- Screenshot and interact with the app in a simulator via expo-mcp

## Example prompts

- "Search the Expo docs for implementing deep linking"
- "Investigate why my most recent iOS build on EAS failed"
- "Show me recent TestFlight crashes for my app"
- "Install expo-camera and show me how to take photos"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http expo https://mcp.expo.dev/mcp
```

2. Start Claude Code, type `/mcp`, pick **expo** and choose **Authenticate**. A browser window opens for the Expo sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Settings → Connectors** and click **Add custom connector**.

2. Name it **Expo** and paste this URL:

```url
https://mcp.expo.dev/mcp
```

3. Click **Add**, then **Connect**, and sign in when Expo asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Expo&connectorUrl=https%3A%2F%2Fmcp.expo.dev%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://mcp.expo.dev/mcp` and click **Add**.

3. Click **Connect** and sign in when Expo asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**.

2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server.

3. Paste `https://mcp.expo.dev/mcp` as the server URL and choose **OAuth**. ChatGPT sends you to Expo to sign in.

Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=expo&config=eyJ1cmwiOiJodHRwczovL21jcC5leHBvLmRldi9tY3AifQ%3D%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "expo": {
      "url": "https://mcp.expo.dev/mcp"
    }
  }
}
```

Cursor shows **Needs login** next to the server. Click it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=expo&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.expo.dev%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"expo","type":"http","url":"https://mcp.expo.dev/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "expo": {
      "type": "http",
      "url": "https://mcp.expo.dev/mcp"
    }
  }
}
```

VS Code asks you to sign in the first time the server starts.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "expo": {
      "serverUrl": "https://mcp.expo.dev/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add expo --url https://mcp.expo.dev/mcp
codex mcp login expo
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.expo]
url = "https://mcp.expo.dev/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http expo https://mcp.expo.dev/mcp
```

Then, inside Gemini CLI, run `/mcp auth expo` to sign in.

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

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

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.expo.dev/mcp`.

## Details

- Last checked: 2026-10-03 (reachable, asks for credentials)
- Listed: 2026-10-03
- Updated: 2026-10-03

---
Source: https://mcp.tc/i/expo (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report