QApilot MCP automates tests on real Android devices and emulators by talking to Claude, Cursor or Codex. Describe a test flow in plain English, no Appium code required. Your agent lays out the steps. QApilot runs the steps. It finds the elements, waits for the screen to settle, retries when something moves, and caches what it learns so repeat runs are faster. Every pass saves a Gherkin feature file and becomes a replayable test case. Needs Node, Java and the Android SDK.
Android app testing inside your AI client. You describe what needs to hold in plain English, and it runs on a device or emulator connected to your machine.
The specifics:
Android only. iOS is next.
Native Android apps. Hybrid and WebView aren't supported yet.
Local device or emulator.
Tested configs for Claude Desktop, Cursor and Codex.
You'll need Node, Java, the Android SDK, and Appium running locally.
Why an MCP?
Coding agents made mobile code cheap to write. They did nothing for verifying it, so the bottleneck just moved. A mobile lead put it well: "by the time your report reaches me, I've merged three more PRs." Our testing wasn't wrong. It was happening too late, in a tool he never opened. MCP is how we moved it into his editor.
What it does
You tell your agent what needs to hold: "verify checkout still works after this refactor." It lays out the steps; QApilot finds the actual element behind "Checkout" on a real Android screen, waits for it to settle, retries when something moves, and says so honestly when it can't.
You get a verdict, a live browser preview, and files on disk: YAML, JSON steps, Gherkin on pass. Accept a run and it becomes a test case you can replay by ID, in batch, or from Excel. It caches what it learns per app, so it gets faster the more you use it.
The part we care most about
It runs on your machine. Your app, your screenshots and your runs don't get uploaded. Only your account and the test cases you explicitly save go to QApilot. Most tools here force every run through their cloud behind a tunnel, and for a lot of teams that's an immediate no. We didn't want to build that.
If you build Android apps with a coding agent, I'd like to know what you still check by hand before every merge. That's what shapes where this goes next.
Happy to answer anything in the comments.
About QApilot MCP for Android on Product Hunt
“Android app testing inside your coding agent”
QApilot MCP for Android launched on Product Hunt on September 12th, 2026 and earned 211 upvotes and 41 comments, earning #3 Product of the Day. QApilot MCP automates tests on real Android devices and emulators by talking to Claude, Cursor or Codex. Describe a test flow in plain English, no Appium code required. Your agent lays out the steps. QApilot runs the steps. It finds the elements, waits for the screen to settle, retries when something moves, and caches what it learns so repeat runs are faster. Every pass saves a Gherkin feature file and becomes a replayable test case. Needs Node, Java and the Android SDK.
On the analytics side, QApilot MCP for Android competes within Software Engineering, Artificial Intelligence and Development — topics that collectively have 529.3k followers on Product Hunt. The dashboard above tracks how QApilot MCP for Android performed against the three products that launched closest to it on the same day.
Who hunted QApilot MCP for Android?
QApilot MCP for Android was hunted by fmerian. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Reviews
QApilot MCP for Android has received 9 reviews on Product Hunt with an average rating of 4.89/5. Read all reviews on Product Hunt.
For a complete overview of QApilot MCP for Android including community comment highlights and product details, visit the product overview.
fmerian
Hey Product Hunt!
I am Charan. Thrilled to bring QApilot MCP to you. → https://qapilot.io/mcp/guide
Android app testing inside your AI client. You describe what needs to hold in plain English, and it runs on a device or emulator connected to your machine.
The specifics:
Android only. iOS is next.
Native Android apps. Hybrid and WebView aren't supported yet.
Local device or emulator.
Tested configs for Claude Desktop, Cursor and Codex.
You'll need Node, Java, the Android SDK, and Appium running locally.
Why an MCP?
Coding agents made mobile code cheap to write. They did nothing for verifying it, so the bottleneck just moved. A mobile lead put it well: "by the time your report reaches me, I've merged three more PRs." Our testing wasn't wrong. It was happening too late, in a tool he never opened. MCP is how we moved it into his editor.
What it does
You tell your agent what needs to hold: "verify checkout still works after this refactor." It lays out the steps; QApilot finds the actual element behind "Checkout" on a real Android screen, waits for it to settle, retries when something moves, and says so honestly when it can't.
You get a verdict, a live browser preview, and files on disk: YAML, JSON steps, Gherkin on pass. Accept a run and it becomes a test case you can replay by ID, in batch, or from Excel. It caches what it learns per app, so it gets faster the more you use it.
The part we care most about
It runs on your machine. Your app, your screenshots and your runs don't get uploaded. Only your account and the test cases you explicitly save go to QApilot. Most tools here force every run through their cloud behind a tunnel, and for a lot of teams that's an immediate no. We didn't want to build that.
If you build Android apps with a coding agent, I'd like to know what you still check by hand before every merge. That's what shapes where this goes next.
Happy to answer anything in the comments.