MCP.Market

Quash — Mobile App Automation MCP server

by Abhinav-Sai-Quash·io.github.Abhinav-Sai-Quash/quash-mcp·v1.1.0

Drive Android & iOS mobile-app automation from your AI agent on locally connected devices.

C60/100grade C
What users say
No reviews yet
Be the first
Safety scan
C60/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Quash — Mobile App Automation yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Quash — Mobile App Automation tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings
  • –Code scanpackage could not be scannedn/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 58 days ago12/15
  • Maintainer identitynamespace and repository owner differ; GitHub account older than a year6/10
Overall 60/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Quash — Mobile App Automation compares

Against every graded Productivity MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
60/100
higher than 12% of 1,299 Productivity servers

Install Quash — Mobile App Automation in Claude Code, Cursor or VS Code

The registry entry has no remote endpoint or installable package.

What the publisher says

From the Quash — Mobile App Automation repository's README, as published. We do not edit it. Read it on GitHub

Quash MCP

The Quash MCP server lets an AI agent (Claude Code, Claude Desktop, Cursor, …) drive real mobile-app automation on a connected device: run natural-language test tasks, generate test cases from prompts/docs/repos, manage apps & builds, and pull back streamed runs and reports — all powered by the Quash (mahoraga) automation engine.

This guide covers installing it on macOS or Windows, wiring it into your agent, generating an API token, preparing a device, and using every tool.

Platform support

iOS automation needs Xcode / WebDriverAgent / devicectl / iproxy, which exist

only on macOS — so the iOS tools (setupsimulator, setupdevice) appear in

the macOS build only. Windows is Android-only. Linux x86_64 can be built from

source but isn't published as a release binary.

1. Prerequisites

Windows the installer also detects %LOCALAPPDATA%\Android\Sdk.

  • macOS 13+ (Apple Silicon) or Windows 10/11 (x64).
  • adb on your PATH (Android platform-tools) for Android automation. On

iOS simulator or a physical iPhone (Developer Mode on, trusted, USB).

  • A device: an Android device/emulator (USB debugging on), or — on macOS — an
  • A Quash account to authenticate (step 3 for a token, or browser sign-in in step 5).
  • For iOS on macOS: Xcode installed (for the WebDriverAgent build).

The installer also downloads the automation engine, a bundled test-generation

component, and the on-device Android Portal APK.

2. Install

One command installs everything and auto-registers the server in every supported agent config it finds (Claude Code, Claude Desktop, Cursor). Pick your platform:

macOS

curl -fsSL https://raw.githubusercontent.com/Oscorp-HQ/quash-mcp-releases/main/install.sh | sh

Windows (PowerShell)

irm https://raw.githubusercontent.com/Oscorp-HQ/quash-mcp-releases/main/install.ps1 | iex

This installs the latest release into ~/.quash (macOS) / %USERPROFILE%\.quash (Windows) and connects to Quash production automatically — no backend URL to configure.

Cursor users: after running the installer above (needed for the engine), you can

one-click add the MCP server to Cursor:

(The installer already auto-registers Cursor, so this is only needed if you skipped that or removed the entry.)

Options (env vars)

macOS gotcha: environment variables must go on the piped sh, not on

curl — a prefix on curl is ignored. On Windows, set $env:… before the irm.

macOS — wire your token in / pin a version:

# Token at install time (recommended — see step 3):
curl -fsSL https://raw.githubusercontent.com/Oscorp-HQ/quash-mcp-releases/main/install.sh | QUASH_API_TOKEN=qsh_xxxxxxxx sh

# Pin a specific version:
curl -fsSL https://raw.githubusercontent.com/Oscorp-HQ/quash-mcp-releases/main/install.sh | QUASH_VERSION=v1.1.0 sh

Windows — same, via $env::

$env:QUASH_API_TOKEN = "qsh_xxxxxxxx"
irm https://raw.githubusercontent.com/Oscorp-HQ/quash-mcp-releases/main/install.ps1 | iex

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Quash — Mobile App Automation: common questions

Is Quash — Mobile App Automation MCP server safe?
With care: it is graded C, so read the findings first (60/100). Read the Quash — Mobile App Automation safety report
Does Quash — Mobile App Automation need an API key?
Yes. The registry entry asks for QUASH_API_TOKEN.
Is Quash — Mobile App Automation maintained?
The last commit was 97 days ago (2026-07-30). The latest release is v1.1.0.
What can I use instead of Quash — Mobile App Automation?
Servers from other publishers that do the same job: Argent MCP server, Sceneview MCP server and SceneView MCP server.

Alternatives to Quash — Mobile App Automation

Same job from other publishers: the closest match first, then the best rated.

  • Argent
    Drive iOS Simulators, Android emulators, TVs and Electron/web apps from your coding agent
    A
  • Sceneview
    3D & AR SDK for Android, iOS, Web — API docs, samples, validation, and code generation.
    A
  • SceneView
    3D & AR SDK for Android, iOS, Web — API docs, samples, validation, and code generation.
    A
  • Sceneview
    3D & AR SDK for Android, iOS, Web — API docs, samples, validation, and code generation.
    A
  • gflow-cli
    Drive Google Flow from an agent: Veo video and Imagen image generation
    A