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 |
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 |
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 (requires an EAS paid plan) |
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 |
appstore_reviews | Fetch public App Store customer reviews for an app (rating, title, body, reviewer, territory). For TestFlight beta feedback use testflight_feedback instead. | "" | Server |
appstore_reply_review | Post or edit the public developer response to an App Store customer review. This is a write action: the response is visible to everyone on the App Store, and Apple publishes it after a short review. App Store Connect allows a single response per review, so any existing response is replaced. | "" | Server |
appstore_delete_review_response | Delete the public developer response on an App Store customer review. This is a write action: it removes the response from the App Store. No-op-safe — if the review has no response, it reports that nothing was deleted. | "" | Server |
playstore_crashes | Fetch crash and ANR data from Google Play (Android Vitals). Without issueId, lists recent crash/ANR issues. With issueId, returns the full error report with stack trace. | "" | Server |
playstore_reviews | Fetch user reviews from Google Play. Returns review metadata including author, star rating, device info, and comment text. Note: Google Play only exposes production reviews with text from approximately the last week. | "" | Server |
playstore_reply_review | Post a public developer reply to a Google Play user review, or edit the existing reply. This is a write action: the reply is visible to users on the store listing. Each review has a single developer reply, so replying again replaces it. Reply text is limited to 350 characters. | "" | Server |
expo_router_sitemap | List all routes (the sitemap) of the current Expo Router project. Use this when you are working with Expo Router and need to know which routes or screens exist in the app. | "check the expo-router-sitemap output" | Local (requires expo-router library) |
open_devtools | Open React Native DevTools for the running app to debug JavaScript, inspect the component tree, and view console output. Requires a running dev server (Metro) for the project. | "open devtools" | Local |
collect_app_logs | Collect logs over a short time window from the native device (Android logcat / iOS syslog) and/or the JavaScript console. Use this to debug runtime errors, crashes, or unexpected behavior in a running app. | "collect app logs from the iOS simulator" | Local |
automation_tap | Tap on the running app at the given screen coordinates (x, y) or on the view with the given React Native testID. Provide either both x and y, or testID. Prefer testID when available, as it is resilient to layout changes. | "tap the screen at x=12, y=22" | Local |
automation_take_screenshot | Take a screenshot of the running app — the full screen, or a specific view if a React Native testID is provided. Use this to visually verify the current UI state. | "take a screenshot and verify the blue circle view" | Local |
automation_find_view | Find a view by its React Native testID and return its properties (position, size, and visibility). Use this to verify a view rendered correctly, or to obtain coordinates before calling automation_tap. | "dump properties for testID 'button-123'" | Local |
