all you need is love, and to let Claude handle your e2e tests with the open source Maestro MCP.

We hear ya. Stay tuned... 😉

The beauty of mobile UI testing when the agent does the tapping.

Android 17 (API 37) is here! 🚀 Maestro CLI 2.11.0 runs it locally and on Maestro Cloud, and finds the right system image for you. Also in 2.11.0: Cloud video scrubbing now lines up with your commands. Everything else: maestro.dev/blog/maestro-cli…

do you remember when we used to test mobile UIs by hand? Me neither.

Claude wrote its own QA test plan in Simplenote, then pinned it. Every tap through Maestro MCP. Open source.

The full recording of the latest Office Hours session is here: piped.video/watch?v=AsCDQGZN…

Building a Wikipedia test in this Office Hours clip, Claude Code noticed the first-run tooltips and dismissed each one on its own. Nobody told it they would appear or how to handle them. It wrote the test and reran it, all through the Maestro MCP.

Watch Claude control your app and run a full E2E test through Maestro MCP. Open source.

Give your coding agent eyes and hands to test your app. Maestro MCP, open source.

Let Maestro MCP handle the QA for you.

One command. Five test runs across different iPhones and iOS versions, all at once. Simon types a single line and Maestro runs the same flow across iPhone 11 on iOS 26, 18, 17 and 16 in parallel on Maestro Cloud, launched through the Maestro MCP. The results come back together. Join us for the next Maestro Office Hours session tomorrow: luma.com/j3xwqlj4

Automate your UI tests with Maestro MCP. open source

It's so much better when your own coding agent opens the app and checks that what it built works. That's what Maestro MCP is for: eyes and hands for @claudeai, @cursor_ai or Codex.

Your coding agent has a better work-life balance than you. Journal: "finished work early, got a workout in, read a few chapters..." Give your coding agent eyes and hands to control your app. Maestro MCP.

This is what automated UI testing looks like in 2026. An agent taps through every settings screen in Sleep Cycle, handles a permission dialog and a failed download, and Maestro records it all as a rerunnable test.

You can automate UI testing with the help of @claudeai or any other coding agent.

@claudeai code caught its own flaky test step, added a wait for the results to settle, and stabilized the test itself. All driven through the Maestro MCP.

Watch @claudeai CONTROL a phone. Testing @Freeletics on Android, on its own. Maestro MCP.

Automate your UI tests any way you want: with your coding agent, tap by tap in Maestro Studio's visual IDE, or in your own editor and run from the CLI. All 3 in Maestro. OPEN SOURCE.