MCP tools for EAS Build and Workflows
FEB 6, 2026 | By Mustafa Abban
Expo MCP Server now includes tools that allow your AI assistants to interact directly with your EAS Builds and Workflows. These tools enable you to manage builds, trigger workflows, and automate debugging issues, all through interacting with your favorite AI-assisted development tools like Claude Code, Cursor, and VS Code.
What's New
Build Management Tools
You can now ask your AI assistant to:
build_infoCheck build status: "Get the status of my latest iOS build"build_listList builds: "What are my recent builds"build_logsView build logs: "Show me the logs for the failed build"build_runTrigger new builds: "Run a production build for iOS"build_cancelCancel running builds: "Cancel the build that is currently in progress"build_submitSubmit to app stores: "Submit the latest build to the App Store"
Workflow Automation Tools
Manage your entire workflow pipeline through conversational prompts:
workflow_createCreate workflows: "Create a workflow for building and deploying"workflow_infoMonitor runs: "Get the status of the latest workflow run"workflow_listList workflows: "What are my recent workflows"workflow_logsView logs: "Show me the logs for the build job in the workflow"workflow_runTrigger runs: "Run the build-and-deploy workflow"workflow_validateValidate configurations: "Validate my workflow file"workflow_cancelCancel workflows: "Cancel the running workflow"
Examples
Retrieve recent workflow runs and investigate the root cause behind their failures:
> what are my recent workflows
Here are your recent EAS workflows:
| Date | Workflow | Status | Branch | Commit |
|--------------|----------------------|-------------|--------|----------------|
| Feb 4, 2026 | Android Build | ✅ SUCCESS | main | 186dbaa - "ex" |
| Jan 30, 2026 | iOS Build and Submit | ❌ FAILURE | main | 186dbaa - "ex" |
| Jan 28, 2026 | iOS Build and Submit | ❌ FAILURE | main | 186dbaa - "ex" |
| Jan 28, 2026 | Android Build | ⚪ CANCELED | main | 186dbaa - "ex" |
Example scenario with interacting with build tools to inspect and rerun a build:
> what are the logs of my recent build
Here's a summary of the logs for your most recent Android build:
Build Summary
- Build ID: 60e2fdf1-fc7a-4b08-89c3-fe53bb2ea311
- Status: ✅ SUCCESS
Build Environment
- Machine: AMD, 4 vCPUs, 16 GB RAM
- Image: ubuntu-22.04-jdk-17-ndk-r26b
- Node.js: 20.19.2
- Java: 17
- Bun: 1.2.4
- NDK: 26.1.10909125
Build Phases
| Phase | Result |
|----------------------------|-----------------------|
| QUEUE | ✅ success |
| SPIN_UP_BUILDER | ✅ success |
| RUN_GRADLEW | ✅ success (14m 55s) |
| UPLOAD_APPLICATION_ARCHIVE | ✅ success |
| SAVE_CACHE | ✅ success |
Output
- APK Size: 81.1 MB
- Location: app-release.apk
- Gradle Tasks: 862 executed, 1 up-to-date (863 total)
Cache Stats
- Cache Hit Rate: 25% (216/864 hits)
- Cache Size: 0.04 GB / 5.00 GB
Getting Started
To use these tools, you'll need:
- An EAS paid plan
- The Expo MCP Server configured in your AI-assisted tool
- An authenticated connection to your Expo account
Learn more in the MCP documentation.
Fetched April 8, 2026



