Tool	Description	Example Prompt	Availability
`add_library`	Add an Expo library to the project using expo install and attach usage instructions when available.	"add sqlite and basic CRUD to the app"	Server
`search_documentation`	Search the official Expo documentation and return page URLs ranked by relevance for a user query. Use read_documentation to fetch the full content of specific pages, starting from the top.	"search documentation for CNG"	Server
`read_documentation`	Fetch a single Expo documentation page and return its content as markdown. Returns up to ~5000 tokens per call. Use offset to paginate through long pages.	"read the Expo Router docs page"	Server
`learn`	Learn Expo how-to for a specific topic and remember it for future conversations. Use this to teach the assistant about specific Expo features or workflows.	"learn how to use expo-router"	Server
`workflow_create`	Creates a new EAS workflow YAML file for Expo projects or fetches workflow syntax documentation. Use this when users want to create CI/CD workflows in .eas/workflows/ or need to learn EAS workflow syntax. After creating, use workflow_validate to validate the file.	"create a CI/CD workflow for building and deploying"	Server
`workflow_info`	Fetches detailed information about a specific EAS workflow run by ID. Use this to check the status, job results, errors, and artifacts of a workflow run. If workflow has multiple jobs, draw them in a diagram to show the dependencies between jobs.	"get the status of the latest workflow run"	Server
`workflow_list`	Lists recent EAS workflow runs for a project. Provide either appId (from app.json "extra.eas.projectId") OR appFullName (e.g., "@owner/my-app").	"list the recent workflow runs"	Server
`workflow_logs`	Fetches logs for a specific job in an EAS workflow run. Call without sectionIndex or phase to get a summary of log sections (phase names and line ranges); then call again with sectionIndex or phase to fetch that section.	"show me the logs for the build job in the workflow"	Server
`workflow_run`	Triggers an EAS workflow run from a git reference. Provide either appId (from app.json "extra.eas.projectId") OR appFullName (e.g., "@owner/my-app"). The workflow file must exist at the specified git reference.	"run the build-and-deploy workflow"	Server
`workflow_cancel`	Cancels a running EAS workflow. Use workflow_info to get the workflow run ID.	"cancel the running workflow"	Server
`workflow_validate`	Validates EAS workflow YAML syntax and configuration. Use this after creating a workflow to ensure it is valid. Provide either appId (from app.json "extra.eas.projectId") OR appFullName (e.g., "@owner/my-app").	"validate my workflow file"	Server
`build_list`	Lists EAS builds for a project. Provide either appId (from app.json "extra.eas.projectId") OR appFullName (e.g., "@owner/my-app"). Use this to see recent builds, their status, and available artifacts.	"list the recent builds for this project"	Server
`build_info`	Fetches the status and detailed information about a specific EAS build by ID. Use this to check build status, errors, artifacts, and other details.	"get the status of my latest iOS build"	Server
`build_logs`	Fetches the logs for a specific EAS build. The build must be completed (finished or errored) to have logs available.	"show me the logs for the failed build"	Server
`build_submit`	Submits an EAS build to the app store (Google Play Store for Android, App Store for iOS). The build must be a finished build with the appropriate distribution type. Provide either appId (from app.json "extra.eas.projectId") OR appFullName (e.g., "@owner/my-app").	"submit the latest build to the App Store"	Server
`build_run`	Triggers a new EAS build using a build profile from eas.json. Requires a GitHub repository to be connected to the project. Provide either appId (from app.json "extra.eas.projectId") OR appFullName (e.g., "@owner/my-app").	"run a production build for iOS"	Server
`build_cancel`	Cancels an EAS build that is queued or in progress. Use build_info to check the current status first.	"cancel the build that is currently in progress"	Server
`testflight_crashes`	Fetch TestFlight crash data. Without crashId, lists recent crashes. With crashId, returns the full crash log with stack trace.	"show me recent TestFlight crashes"	Server
`testflight_feedback`	Fetch screenshot feedback from TestFlight. Returns feedback metadata including device info, user comments, and screenshot URLs.	"show TestFlight feedback for my app"	Server
`expo_router_sitemap`	Query the all routes of the current expo-router project. This is useful if you were using expo-router and want to know all the routes of the app.	"check the expo-router-sitemap output"	Local (requires `expo-router` library)
`open_devtools`	Open the React Native DevTools.	"open devtools"	Local
`collect_app_logs`	Collect logs from native device (logcat/syslog) or JavaScript console.	"collect app logs from the iOS simulator"	Local
`automation_tap`	Tap on the device at the given coordinates (x, y) or by react-native testID. Provide either (x AND y) or testID.	"tap the screen at x=12, y=22"	Local
`automation_take_screenshot`	Take screenshot of the full app or a specific view by react-native testID. Optionally provide testID to screenshot a specific view.	"take a screenshot and verify the blue circle view"	Local
`automation_find_view`	Find view and dump its properties. This is useful to verify the view is rendered correctly.	"dump properties for testID 'button-123'"	Local

Using Model Context Protocol (MCP) with Expo

What does Expo MCP Server do?

Prerequisites

Installation and setup

Install Expo MCP Server

Authenticate with Expo

Access token (recommended)

Credentials

Set up local capabilities (Recommended)

Server capabilities versus local capabilities

Server capabilities

Local capabilities

Available MCP capabilities

Tools

Prompts

Limitations

Additional resources