Expo for agents
DevOps. MCP servers, the command line and skills for connecting an agent to Expo.
- Official server
- 1 server
- Sourced servers by others
- 6
- Command line
eas- Vendor skills
- 24
Official server
The MCP Registry does not list Expo's own server, but its owner names its address on a page of its own, at a domain we curate for Expo: on those two proofs it is the system's official server here. Beyond that we only ask it each night, with no credential, what it answers.
https://mcp.expo.dev/mcpnamed on the owner's page, read . Asked with no credential on , it asked the client to sign in (OAuth).
Command line
eas is a command-line tool for Expo. For an agent that runs on your machine and has a shell, a command-line tool can be the simpler choice: there is no server to connect, and no tool definitions take room in the context window. See its documentation.
Skills from Expo
Agent Skills published by the vendor in expo/skills.
A skill that ships scripts carries code an agent may run: read it first. The Scripts column says whether a fixed pattern for network calls was run over them and matched; a pattern is not a review. Fetched from the vendor's repository on GitHub on , most recently changed first. Weight is the skill's SKILL.md counted with OpenAI's o200k_base tokenizer: what loading it puts in a context window. Other makers' tokenizers count differently, so it compares skills with each other and is not a bill. Where a count is missing, the file's size in bytes stands in.
"A model read it as" is a model's reading of the file, not a fact about the skill. "Picked" is two counts from a trigger eval on one model: of the requests the skill should be picked for, how many times its description got it picked, then the same of the requests it should not be picked for. Neither says the skill is good, and neither is used for the order. A skill's own page names the model and the date of each.
| Skill | What it is for | A model read it as | Picked: should · should not | Weight when loaded | Scripts | Last changed |
|---|---|---|---|---|---|---|
eas-app-stores | Build and submit iOS and Android apps with EAS to TestFlight, the App Store, or Google Play. Supports Expo and other React Native projects, plus existing native apps. Use for eas.json setup, release pipelines, signing, app versions and build numbers, store submissions, and listing metadata. For Exp… | not read | not run | about 1,706 tokens | none | not since |
eas-hosting | Deploy Expo websites and Expo Router API routes to EAS Hosting - export the web bundle, run eas deploy for production and PR preview URLs, manage environment secrets and custom domains, and work within the Cloudflare Workers runtime. Also covers authoring API routes (+api.ts handlers, HTTP methods,… | not read | not run | about 2,774 tokens | none | not since |
eas-observe | Use for anything related to EAS Observe - adding `expo-observe` to an Expo project (AppMetricsRoot/ObserveRoot HOC, markInteractive and ObserveInteractiveMarker, the useObserve hook, the Expo Router / React Navigation integrations for per-route metrics, the expo-image and Reanimated integrations, u… | not read | not run | about 1,338 tokens | none | not since |
eas-simulator | Run and control a user's app on a remote iOS/Android simulator with Expo Simulators (also called EAS Simulator). Read before running any `eas simulator:*` commands - it has the current syntax and workflow. Use whenever the user needs a simulator they can't run locally - 'run my app on a cloud simul… | not read | not run | about 8,531 tokens | none | not since |
eas-update | Configure and use EAS Update for over-the-air JavaScript and asset updates with expo-updates and EAS CLI. Use when setting up OTA updates, running eas update:configure or eas update, publishing to preview/staging/production channels, explaining branches/channels/runtime versions, testing updates, o… | not read | not run | about 2,046 tokens | none | not since |
eas-update-insights | Check the health of published EAS Update: crash rates, install/launch counts, unique users, payload size, and the split between embedded and OTA users per channel. Use when the user asks how an update is performing, whether a rollout is healthy, how many users are on the embedded build vs OTA, or w… | not read | not run | about 3,059 tokens | none | not since |
eas-workflows | Helps understand and write EAS workflow YAML files for Expo projects. Use this skill when the user asks about CI/CD or workflows in an Expo or EAS context, mentions .eas/workflows/, or wants help with EAS build pipelines or deployment automation. | not read | not run | about 1,089 tokens | ships scriptsnot checked | not since |
expo-animation | Build animations in React Native and Expo, making the decisions in the order that determines whether they feel right — should it animate, which thread it runs on, which properties, spring or timing, how the gesture hands off, how it degrades. Writes the implementation with Reanimated, Gesture Handl… | not read | not run | about 4,634 tokens | none | not since |
expo-app-clip | Add an iOS App Clip target to an Expo app. Use when the user mentions App Clip, AASA, apple-app-site-association, appclips, smart app banner, or wants to ship a lightweight iOS Clip invoked from a URL alongside their parent app. | not read | not run | about 2,533 tokens | none | not since |
expo-brownfield | Integrate Expo and React Native into an existing native iOS or Android app. Use for brownfield, embedding a React Native screen in SwiftUI/UIKit or Kotlin, or AAR/XCFramework packaging. Covers isolated and integrated approaches. For building or distributing a purely native app with EAS, use eas-app… | not read | not run | about 1,199 tokens | none | not since |
expo-data-fetching | Use when implementing or debugging ANY network request, API call, or data fetching. Covers fetch API, React Query, SWR, error handling, caching, offline support, loading/empty/error screen states, and Expo Router data loaders (`useLoaderData`). | not read | not run | about 3,314 tokens | none | not since |
expo-design-system | Build and maintain a design system inside an Expo app - a reusable theme of design tokens (color, spacing, typography, radius, shadow, motion), reusable component structure with variant/size/state prop conventions, and rules for when to extract a repeated view into a shared component. Use when crea… | not read | not run | about 4,573 tokens | none | not since |
expo-dev-client | Build and distribute Expo development clients locally or via TestFlight for internal testing. For production TestFlight releases and store submission, use the eas-app-stores skill. | not read | not run | about 1,312 tokens | none | not since |
expo-dom | Use Expo DOM components to run web code in a webview on native and as-is on web. Migrate web code to native incrementally. For the end-to-end migration of a whole web app, use the expo-web-to-native skill. | not read | not run | about 2,551 tokens | none | not since |
expo-examples | Expo's official example projects - the expo/examples repo of ~70 `with-*` integrations (Stripe, Clerk, Supabase, OpenAI, maps, Reanimated, SQLite, Skia, NativeWind, and more). Use when integrating a third-party library or service into an existing Expo app and you want the canonical, version-matched… | not read | not run | about 1,647 tokens | none | not since |
expo-migrate-module | Migrate an existing Apple/Swift Expo native module from the Expo Modules API 1.0 definition DSL to the 2.0 macro API (sometimes called v2) while preserving its JavaScript and TypeScript contract. Use when converting or incrementally adopting @ExpoModule, @JS, @Event, @SharedObject, or @Record in an… | not read | not run | about 2,960 tokens | none | not since |
expo-module | Guide for creating and writing Expo native modules and views using the Expo Modules API (Swift, Kotlin, TypeScript). Covers module definition DSL, native views, shared objects, config plugins, lifecycle hooks, autolinking, and type system. Use when building or modifying native modules for Expo. Not… | not read | not run | about 1,459 tokens | none | not since |
expo-native-ui | Build beautiful, native-feeling Expo screens. Covers Apple HIG styling, semantic colors, native controls, SF Symbols, media, visual effects, gradients, storage, and responsive layout. For routing and navigation, use the expo-router skill; for motion and animation, use the expo-animation skill. | not read | not run | about 2,909 tokens | none | not since |
expo-overview | Entry point and router for every Expo or EAS task. Load this skill first — before writing code and before choosing another expo-* / eas-* skill — when the request, PRD, or spec mentions Expo, EAS, Expo Go, or an expo-* package, or the project has an `expo` dependency in `package.json`. Within that… | not read | not run | about 2,733 tokens | none | not since |
expo-project-structure | Folder structure for a new Expo app. Use when scaffolding or laying out a new Expo project with Expo Router, or deciding where a file should live in one. For new projects only — never restructure an existing app to match. | not read | not run | about 1,595 tokens | none | not since |
expo-router | Navigation and routing for Expo Router. Covers file-based routes, groups and dynamic routes, folder organization, Link with previews and context menus, native Stack, page titles, modals and form sheets, NativeTabs, headers and toolbars, and header search bars. | not read | not run | about 1,697 tokens | none | not since |
expo-ui | Build native UI with the @expo/ui package: real SwiftUI on iOS and Jetpack Compose on Android. Default to @expo/ui for sheets (BottomSheet), pickers, sliders, toggles, menus, and grouped-form sections — do NOT reach for Reanimated, @gorhom/bottom-sheet, or RN built-in Picker/Switch; use @expo/ui in… | not read | not run | about 1,734 tokens | ships scriptsnot checked | not since |
expo-upgrade | Guidelines for upgrading Expo SDK versions and fixing dependency issues | not read | not run | about 1,789 tokens | none | not since |
expo-web-to-native | Migrate an existing web React app to a native iOS/Android app with Expo. Use when the user wants to turn a website into a mobile app, port a Next.js/Vite/CRA React codebase to React Native, reuse web code on native incrementally, or asks how web idioms (the DOM, CSS, React Router, localStorage, win… | not read | not run | about 2,550 tokens | none | not since |
Servers by other publishers
6 servers for Expo that name a public repository or a package, or whose tools we could read. Anyone can publish one, and we have not read their code: check the publisher and the source before giving one a credential.
In this order: live servers before deprecated ones, first-party first, a known vulnerability last, then more downloads, then a more recent push, then by name. There is no score, and the number of tools is not part of the order: fewer is not better. Tools are what a server listed to a client with no credential, or what its package listed when run with no network, downloads are from npm and pypistats, the last push from GitHub and vulnerabilities from OSV; a server's own page has the day each was read, and "not read" means we have no figure, not that there is none. See how this directory is made.
| Server | Publisher | Reach | Tools | Downloads a week | Last push | Vulnerabilities |
|---|---|---|---|---|---|---|
Expo Application Servicescom.foreverworks/eas | Sourced | npm | not read | 310 | not read | none known |
Expo Agent Bridgeio.github.Rudrasamadhiya/expo-mcp-bridge | Sourced | npm | not read | 90 | not read | none known |
| io.github.Abubakr-Sanginov/expo-headless-mcp | Sourced | npm | not read | 73 | not read | none known |
Expo Launch Videoio.github.Rudrasamadhiya/expo-launch-video | Sourced | npm | not read | 65 | not read | none known |
Expo Android MCPio.github.frndchagas/expo-android | Sourced | npm | not read | 65 | not read | none known |
Expoio.github.mcp-dir/expo-mcp | Inspected | remote | 25 | not read | not read | not checked |
Changes for Expo
None in the last 30 days. The log began on , and nothing older was recorded.
A change is a difference between two readings of public records, not a review. Expo in the log · How the log is made · Expo's Atom feed
A server is listed for Expo when we have named it as the system's official server, when its registry title or the last part of its registry name names Expo as whole words, or when it is published at Expo's own domain. See how this directory is made.
Built from agent catalog version 2026-11-18.1 of , from the MCP Registry as read on . A listing here is not an endorsement: anyone can publish a server, and we have not read its code. Names, descriptions and addresses are the publisher's own. See how this directory is made, and tell us about a wrong entry through the contact page.