About Maestro
Maestro is an open-source framework for UI and end-to-end testing of Android, iOS, and web apps. It uses YAML flows and includes an MCP server in its CLI for coding agents to operate live devices.
Key features
- 01Write readable tests as YAML flows
- 02Cover Android, iOS, and web
- 03Run flows on emulators and devices
- 04Wait for dynamic interfaces automatically
- 05MCP server included in the CLI
Use cases
- 01Create end-to-end tests for mobile apps
- 02Verify UI flows in web browsers
- 03Let coding agents operate and inspect devices
- 04Use YAML test flows in CI
MCP support
Maestro MCP ships with the Maestro CLI and exposes live-device inspection, tapping, scrolling, and assertions to MCP clients. Agents can also create and run YAML end-to-end test flows.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMETip
Great things happen when testers connect — Join the Maestro Community
Maestro is an open-source framework that makes UI and end-to-end testing for Android, iOS, and web apps simple and fast.
Hand-write your first YAML flow with the CLI in under 5 minutes, build flows visually in Maestro Studio, or add Maestro MCP to your coding agent for agentic UI testing.
Flows run on any emulator, simulator, browser, or physical Android device. Physical iOS devices are not yet supported.
Table of Contents
- Why Maestro?
- Getting Started
- Maestro MCP – Agentic UI Testing
- Maestro Studio – Test IDE
- Maestro Cloud – Parallel Execution & Scalability
- Resources & Community
- Contributing
Why Maestro?
Maestro is built on learnings from its predecessors (Appium, Espresso, UIAutomator, XCTest, Selenium, Playwright), plus 3 decisions made early: drive the app through the platform's accessibility layer, install as a single binary with no drivers or SDK, and keep every test a flat list of YAML commands.
- Human-readable YAML flows – express interactions as commands like
launchApp,tapOn, andassertVisible. - Built for coding agents – the Maestro MCP server ships inside the Maestro CLI (
maestro mcp, nothing else to install). Claude Code, Cursor, Codex, Grok Build, or any MCP client can control your app on a live device: inspect the screen, tap, scroll, assert, and check its own work while it builds. Ask for a flow when you want a repeatable test — that's agentic UI testing. - Framework agnostic – React Native, Flutter, native iOS and Android, Ionic, and hybrid apps all use the same commands. Meta uses Maestro to test React Native itself, and Expo supports Maestro as its preferred E2E testing platform.
- Cross-platform coverage – one flow syntax for Android, iOS, and web, on emulators, simulators, browsers, and physical Android devices.
- Resilience & smart waiting – built-in flakiness tolerance and automatic waiting handle dynamic UIs without manual
sleep()calls. - Fast iteration & simple install – one install line, no drivers, no SDK, no dependencies; flows are interpreted, so there's no compilation step. First test in 5 minutes.
Simple Example:
# flow_contacts_android.yaml
appId: com.android.contacts
---
- launchApp
- tapOn: "Create new contact"
- tapOn: "First Name"
- inputText: "John"
- tapOn: "Last Name"
- inputText: "Snow"
- tapOn: "Save"
Getting Started
Maestro requires Java 17 or higher to be installed on your system. You can verify your Java version by running:
java -version
Installing the CLI:
Run the following command to install Maestro on macOS, Linux or Windows (WSL):
curl -fsSL "https://get.maestro.mobile.dev" | bash
The links below will guide you through the next steps.
- Installing Maestro (includes regular Windows installation)
- Add Maestro MCP to your coding agent
- Run your first test with the Maestro CLI (or just ask your agent to do it for you)
Maestro MCP – Agentic UI Testing
Maestro MCP ships inside the Maestro CLI and works with Claude Code, Cursor, Codex, Gemini CLI, Copilot, Grok Build, or any MCP client. It gives your agent a live device (an emulator, simulator, or physical Android device), and Maestro Viewer embeds that device inside your coding agent, showing every MCP command as it runs.
With Maestro MCP, your agent can control the app directly: inspect the screen, tap, scroll, and assert. While it builds or changes a feature, it checks its own work on the device.
Your agent can also write tests. Ask for an end-to-end flow and it writes plain YAML, runs it until it passes, and the flow stays in your repo as a deterministic test for CI.
Setup for each coding agent is in the Maestro MCP docs.
Maestro Studio – Test IDE
Maestro Studio Desktop is a lightweight IDE that lets you design and execute tests visually — no terminal needed. It is also free, even though Studio is not an open-source project. So you won't find the Maestro Studio code here.
- Simple setup – just download the native app for macOS, Windows, or Linux.
- Visual flow builder & inspector – record interactions, inspect elements, and build flows visually.
Maestro Cloud – Parallel Execution & Scalability
When your test suite grows, run hundreds of tests in parallel on dedicated infrastructure, cutting execution times by up to 90%. Includes built-in notifications, deterministic environments, and complete debugging tools.
Pricing for Maestro Cloud is completely transparent and can be found on the pricing page.
Resources & Community
Contributing
Maestro is open-source under the Apache 2.0 license — contributions are welcome!
- Check good first issues
- Read the Contribution Guide
- Found a bug or want a feature? See how to open a good issue
- Fork, create a branch, and open a Pull Request.
If you find Maestro useful, ⭐ star the repository to support the project.
Built with ❤️ by Maestro.dev
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.