Expo
listing.by
Search Expo docs, manage EAS builds and workflows, and test React Native apps in a simulator from your AI assistant.
listing.connect
listing.explain.oauth
listing.note.oauth
listing.share.h
listing.share.p
mcp.tc/i/expolisting.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.
listing.can
- 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
listing.tools
listing.notools.oauth
listing.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
listing.setup.h
listing.setup.oauth
Claude Code
- Run this in a terminal, in your project folder:
claude mcp add --transport http expo https://mcp.expo.dev/mcp- 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
- Open Settings → Connectors and click Add custom connector.
- Name it Expo and paste this URL:
https://mcp.expo.dev/mcp- 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
- Open the connector form on claude.ai. This button fills in the name and URL for you:
- Check that the URL reads
https://mcp.expo.dev/mcpand click Add. - 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
- On chatgpt.com, open Settings → Security and login and turn on Developer mode.
- Go to
chatgpt.com/pluginsand click + to create an app for a remote MCP server. - Paste
https://mcp.expo.dev/mcpas 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
Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):
{
"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 a11y.new_tab
Or from a terminal:
code --add-mcp '{"name":"expo","type":"http","url":"https://mcp.expo.dev/mcp"}'Or commit it to the repo in .vscode/mcp.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
- Add it to
~/.config/devin/mcp_config.json(macOS and Linux) or%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"expo": {
"serverUrl": "https://mcp.expo.dev/mcp"
}
}
}- 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
codex mcp add expo --url https://mcp.expo.dev/mcp
codex mcp login expoOr edit ~/.codex/config.toml directly:
[mcp_servers.expo]
url = "https://mcp.expo.dev/mcp"Gemini CLI
gemini mcp add --transport http expo https://mcp.expo.dev/mcpThen, 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.
{
"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.
listing.faq
Can I paste mcp.tc/i/expo into my MCP client?
No. mcp.tc links are pages, not server addresses. Connect with https://mcp.expo.dev/mcp, so your client talks to Expo directly. The sign-in token only works there anyway. The quick link is for sharing: it opens this page, with setup steps for every client.
Does Expo need an API key or a sign-in?
Yes, you need a Expo account. The first time your client connects, it opens Expo's sign-in page. The token goes straight to the server's own URL, never through mcp.tc.
Is Expo a remote or a local server?
Remote. Expo hosts it at https://mcp.expo.dev/mcp, and it speaks Streamable HTTP. There's nothing to install.
What can Expo do?
You can search and read the latest Expo documentation, install compatible Expo packages with npx expo install and trigger and monitor EAS builds.
Which clients can use it?
Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT in developer mode, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.
Who wrote this page?
mcp.tc's robot read Expo's own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can't confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.
listing.em.h
listing.em.lead listing.em.how
listing.em.badge
[](https://mcp.tc/i/expo)<a href="https://mcp.tc/i/expo"><img src="https://mcp.tc/i/expo/badge.svg" alt="Expo on mcp.tc" height="20"></a>listing.em.badge_note
listing.em.widget
<script src="https://mcp.tc/w/expo.js" async></script>listing.em.widget_note
iframe
<iframe src="https://mcp.tc/embed/expo" title="Expo on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>listing.em.iframe_note
listing.disclaimer_checked