QApilot MCP for Android

Android app testing inside your coding agent

Software Engineering

Artificial Intelligence

Development

Visit WebsiteSee on Product Hunt

testing straight from the coding agent is the right move 👏 ios comming too?

Seems like a valuable solution. We will definitely try it out. What’s the pricing like?

@charan_tej_kammara Congratulations. And happy product launch.

Great Launch Charan.. testing automation without third party walls that too through MCP saves developers times and cost.. good wishes for your success..

It is great to see am app dedicated to android apps. There are so many that focus on ios it is refreshing to see android getting attention. Although I am not a mobile app developer (yet) I am an android user so kobe seeing this.

I also like the ease of use being able to use plain language.

One question, does it work with other coding agents (in particular I use opencode so would be interested in an opencode config).

Good luck with the launch.

Really interesting approach. One thing I’m curious about: once QApilot learns the app’s UI and generates reusable tests, how well does it handle major UI changes between app versions?

Does it automatically adapt existing test cases, or would those need to be redefined?

This is a really smart use of MCP. Love that the tests run locally on the actual device instead of sending everything through the cloud. Congrats on the launch Charan!

Good luck, although I’m on iPhone it’s nice to see ppl building for Android first.

This is pretty interesting. The ability to let the coding agent actually run flows on a local Android device and get the test result back in the same session feels really useful.

especially like the local-first approach and agent-readable reports. Nice launch 👏

@charan_tej_kammara Congrats on the launch ! This looks like a useful tool for mobile app testing. Is iOS support on the roadmap?

Is there any mechanism that detects UI drift between various versions of applications in the element-caching?
Btw, Congratulations @charan_tej_kammara @aakash_balu & team @QApilot 🎊.

@QApilot This looks very useful, when will it be available for iOS?

i can't imagine writing a test in plain language and having it actually get the idea right. would prob be like my reddit replies, where i wing it and hope for the best. but if it nails it on the first try, then maybe i'd stop winging it so much.

curious about the "plain language" part. i sometimes mess up what to say when trying to get the right retro look for a site, so if this can interpret some nonsense and still spit out a working test, i'd give it a shot. but i might forget to open the emulator. 😂

The caching is the bit I'd worry about. If it remembers which elements it poked last run it stops looking, and a screen that quietly moved a button still passes because the cached path resolves fine. That's the failure I'd rather have loud and slow than fast and confident, and it's the same shape as every other agent problem, plausible output that nobody complains about. The Gherkin file falling out of each pass is the real feature, because it's the one artifact a human can read and disagree with.

Hey Product Hunt. I am Aakash, part of the team that built QApilot MCP.

Adding a bit more on what this actually does.

You describe an Android test in plain English inside Claude, Cursor or Codex. It runs on a device or emulator connected to your machine, and you watch it happen in a live browser preview. You get a verdict, plus YAML and Gherkin files on disk. Accept a passing run and it becomes a test case you can replay later.

Android only today, iOS next. Everything runs locally, so your app never leaves your machine.

Happy to answer anything in the thread.

Hey PH! Nihad here, one of the makers behind QApilot MCP.

We built QApilot because we wanted mobile testing to fit into the same workflow as AI-assisted development. Instead of switching between your editor, test tools, and a device, you can describe what you want to verify in plain English and let your agent run it on a real Android device or emulator.

There’s a lot we want to improve, but getting QApilot MCP out there and into developers’ hands is a big step for us. If you work with Android testing, I’d genuinely love to hear what you think, especially what still feels painful in your current workflow.

Thanks for checking us out and supporting the launch

Hey PH! Vidushee here. I am one of the makers of the QApilot MCP.

I wanted to add a few things that make this different from just pointing an agent at a phone, along with some honest caveats.

Your agent decides what to do; QApilot does the part that's hard on mobile - finding the real element behind "Checkout" in a live UI tree, and waiting for the screen to actually settle instead of guessing a sleep.

It caches what it learns per app from passing runs, so it gets faster the more you use it. And it all runs on your machine; your app is never uploaded.

Setup is the rough edge today. You need Node, Java, the Android SDK and Appium running before anything happens, and that's the next thing we're cutting down after iOS.

If there's something you'd want ahead of either, say so here - much easier to reorder this week than in three months.

Thanks!