What it does
Drive Android & iOS mobile-app automation from your AI agent on locally connected devices.
- Connects 在你的电脑上运行
- Account or key No key needed · 1 setting to fill in (QUASH_SIDECAR_CMD)
- Category 开发者工具
可搭配使用
教 AI 做这类工作的 Skill,可与本项一起使用
andrej-karpathy-skills
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
graphify
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
为什么排在这里
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 3/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 3/100 |
质量: 基础检查通过 1/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
安装
选择你使用的 AI 应用,然后复制设置。
通过 1/3 项检查 · 在你的电脑上运行
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
双击文件,然后在电脑版 Claude 应用中点击 Install
试一试
用 Quash — Mobile App Automation 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Quash — Mobile App Automation,或回答中出现 Quash — Mobile App Automation 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Quash — Mobile App Automation
Quash — Mobile App Automation 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
你可以改用这些方式
A · 使用能连接 Quash — Mobile App Automation 的应用
- 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
B · 开发者工具 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
- Sentry✓ ChatGPT
- Compiler Explorer✓ ChatGPT
- GitDiagram✓ ChatGPT
Claude Code 暂时无法连接 Quash — Mobile App Automation
开发者只提供了电脑版 Claude 应用的安装文件
你可以改用这些方式
A · 使用能连接 Quash — Mobile App Automation 的应用
- 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
Cursor 暂时无法连接 Quash — Mobile App Automation
开发者只提供了电脑版 Claude 应用的安装文件
你可以改用这些方式
A · 使用能连接 Quash — Mobile App Automation 的应用
- 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
VS Code 暂时无法连接 Quash — Mobile App Automation
开发者只提供了电脑版 Claude 应用的安装文件
你可以改用这些方式
A · 使用能连接 Quash — Mobile App Automation 的应用
- 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
开发者专用:终端命令和 JSON 设置
需要你填写的值
QUASH_SIDECAR_CMD必填 env由 Quash 安装程序安装的 Quash 自动化引擎(sidecar)路径。查看英文原文
Path to the Quash automation engine (sidecar) installed by the Quash installer.QUASH_API_TOKEN机密 envQUASH_TEST_GEN_AGENT_CMDenvQuash 安装程序所安装的测试用例生成器的命令。查看英文原文
Command for the test-case generator installed by the Quash installer.
说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
一览
哪些应用可以使用它
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它能做什么
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
- ! 注意
作者与仓库一致
发布者(Abhinav-Sai-Quash)不是仓库所有者(Oscorp-HQ);可能是其他人代为上架的
- ✓ 通过
仍在维护
代码最后更新于4个月前
- ✕ 未通过
有许可证
仓库中没有找到许可证文件
- – 不适用
端点有响应
它在你的电脑上运行,没有互联网端点
- – 不适用
使用 OAuth 登录
在你的电脑上运行,改用本地设置
- … 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行;我们只能读取互联网端点的工具列表
作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/abhinav-sai-quash-quash-mcp)讨论
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
用户评价
还没有评价
与“开发者工具”中的其他服务器比较i
- 星标数多于此分类中其他 6182 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 6182 个服务器的 16% 更新
- 基础检查结果等于或优于此分类中其他 6182 个服务器的 7%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
Quash — Mobile App Automation 安全吗?
它在 3 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在我的电脑上运行还是在云端?
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
它还在维护吗?
GitHub 仓库最后更新于4个月前,最新版本(1.1.0)于5个月前进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 MCPB。
有什么可以替代它?
同一分类中有:GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
功能相近的其他选择
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
GitDiagram
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Appllama
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Omnara
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Repowise
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| 本项 Quash — Mobile App Automation | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 是 | 否 | 否 |
| 基础检查 | 1/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| 许可证 | – | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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
| Platform | Android | iOS (simulator + physical) | Installer | |
|---|---|---|---|---|
| macOS (Apple Silicon) | ✅ | ✅ | install.sh (`curl … \ | sh`) |
| Windows (x64) | ✅ | ❌ *(Apple toolchain is macOS-only)* | install.ps1 (`irm … \ | iex`) |
iOS automation needs Xcode / WebDriverAgent /
devicectl/iproxy, which exist
only on macOS — so the iOS tools (
setup_simulator,setup_device) 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
- macOS 13+ (Apple Silicon) or Windows 10/11 (x64).
- `adb` on your
PATH(Android platform-tools) for Android automation. On Windows the installer also detects%LOCALAPPDATA%\Android\Sdk. - A device: an Android device/emulator (USB debugging on), or — on macOS — an iOS simulator or a physical iPhone (Developer Mode on, trusted, USB).
- 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 oncurlis ignored. On Windows, set$env:…before theirm.
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
| Env var | Default | Purpose |
|---|---|---|
QUASH_API_TOKEN | _(unset)_ | API token; if set, the MCP signs in automatically on startup |
QUASH_VERSION | latest | Release tag to install |
QUASH_BACKEND_URL | production | Override the backend (staging/local) |
QUASH_FORCE | 0 | 1 forces a full reinstall even if the version matches |
Re-running the installer is safe: it refreshes config and, with QUASH_FORCE=1, reinstalls the binaries. Reconnecting the agent does not update the server — only re-running the installer does.
3. Generate an API token from the Quash app
The token lets the MCP authenticate without a browser. (Prefer not to manage a token? Skip to step 5 and use Google sign-in instead.)
- Open the Quash desktop app and sign in.
- Go to Settings → Integrations.
- Click Generate token (or regenerate to replace an existing one).
- Copy the token — it starts with
qsh_. It's shown once; store it safely.
Generating a new token invalidates the previous one, so update it everywhere you use it. The token is scoped to the organization you're signed into and is stored only in your agent's MCP config env block — never passed through the chat.
4. Add it to your agent
The installer auto-registers the quash server, so usually there's nothing to do. To verify or add it manually, the entry looks like this — use the paths for your platform:
macOS
{
"mcpServers": { "quash": { "type": "stdio", "command": "/Users/ /.quash/bin/quash-mcp", "env": { "QUASH_SIDECAR_CMD": "/Users/ /.quash/sidecar/quash-sidecar/quash-sidecar", "QUASH_TEST_GEN_AGENT_CMD": "/Users/ /.quash/test-gen-venv/bin/python -m test_gen_agent", "QUASH_API_TOKEN": "qsh_xxxxxxxx" } } } }
Windows
{
"mcpServers": { "quash": { "type": "stdio", "command": "C:\\Users\\ \\.quash\\bin\\quash-mcp\\quash-mcp.exe", "env": { "QUASH_SIDECAR_CMD": "C:\\Users\\ \\.quash\\sidecar\\quash-sidecar\\quash-sidecar.exe", "QUASH_API_TOKEN": "qsh_xxxxxxxx", "ANDROID_HOME": "C:\\Users\\ \\AppData\\Local\\Android\\Sdk" } } } }
Config file locations: Claude Code → ~/.claude.json (macOS) / %USERPROFILE%\.claude.json (Windows); Claude Desktop → ~/Library/Application Support/Claude/claude_desktop_config.json / %APPDATA%\Claude\claude_desktop_config.json; Cursor → ~/.cursor/mcp.json / %USERPROFILE%\.cursor\mcp.json.
After editing config, restart the agent (or /mcp → reconnect in Claude Code).
JetBrains IDEs (IntelliJ IDEA, PyCharm)
JetBrains AI Assistant supports MCP over stdio. After running the installer (step 2):
- Open Settings → Tools → AI Assistant → Model Context Protocol (MCP).
- Easiest: click Import from Claude — since the installer already registered Quash in Claude Desktop, the
quashserver is pulled in automatically. - Or add manually: click Add, then paste this JSON (JetBrains does *not* expand environment variables, so use absolute paths — replace
with your username):
macOS
{
"mcpServers": { "quash": { "command": "/Users/ /.quash/bin/quash-mcp", "env": { "QUASH_SIDECAR_CMD": "/Users/ /.quash/sidecar/quash-sidecar/quash-sidecar", "QUASH_TEST_GEN_AGENT_CMD": "/Users/ /.quash/test-gen-venv/bin/python -m test_gen_agent" } } } }
**Windows**
{
"mcpServers": { "quash": { "command": "C:\\Users\\ \\.quash\\bin\\quash-mcp\\quash-mcp.exe", "env": { "QUASH_SIDECAR_CMD": "C:\\Users\\ \\.quash\\sidecar\\quash-sidecar\\quash-sidecar.exe", "QUASH_TEST_GEN_AGENT_CMD": "C:\\Users\\ \\.quash\\test-gen-venv\\Scripts\\python.exe -m test_gen_agent" } } } }
4. Click **OK → Apply** to start the server.
Android Studio: its agent (Gemini Agent Mode) currently supports MCP over **HTTP/Streamable
only**, not stdio, so the config above does not apply there yet.
5. Authenticate
- If you set `QUASH_API_TOKEN`, the server signs in automatically on startup.
- Otherwise, ask the agent to authenticate:
- Google (browser): "Use Quash, run
authwith modegoogle." - Token: "Use Quash, run
authwith my tokenqsh_…."
Check status anytime with the about / configure tools.
6. Prepare the device
- Connect — "Use Quash,
connect." It detects the device (or lists them if several), warms the engine, and runs a setup health check. - Finish setup for that device type:
- Android — if
connectreports *"Portal not ready"*, run `setup_portal`: it installs the on-device Quash Portal app and enables its accessibility service (idempotent). If the device blocks it, it returnsmanual_requiredwith the steps for Settings → Accessibility. - iOS simulator (macOS) — run `setup_simulator`: builds + launches WebDriverAgent for the booted simulator (no signing needed).
- iOS physical iPhone (macOS) — run `setup_device`: resolves your Apple Developer signing team (set it with
configure signing_team=, or it's auto-detected from your keychain), builds + signs WebDriverAgent, starts the USB tunnel, and launches it. Requires Xcode, Developer Mode on, and the iPhone trusted over USB.
7. Using the tools
Ask the agent in plain language; it calls these tools:
| Tool | What it does | Platform |
|---|---|---|
about | Server name, running version, latest release, update command | all |
auth | Sign in (google browser flow, or token) | all |
connect | Detect/select a device; health-check adb, Portal, engine, auth | all |
configure | View/change execution + test-gen settings (model, temperature, max steps, vision, signing_team) | all |
setup_portal | Install the Android Portal app + enable accessibility (idempotent) | all |
setup_simulator | Build + launch WebDriverAgent for a booted iOS simulator | macOS |
setup_device | Sign + launch WebDriverAgent on a physical iPhone over USB | macOS |
execute | Run a natural-language test task on the device (streams progress) | all |
generate_test_cases | Generate test cases from a prompt, local files, or a git repo | all |
usage | Current plan, remaining minutes, feature limits | all |
list_apps | List apps in your org | all |
builds | List builds for an app (version, tag, installable) | all |
install_build | Download a build's APK and install it on the device | all |
runs | Browse recent runs, or fetch one run's full report + share link | all |
test_cases / suites | Browse test cases and suites | all |
Typical first session:
"Use Quash: connect, then setup_portal if needed." # Android
"Use Quash: connect, then setup_simulator." # iOS simulator (macOS) "Run this on the device: open Settings and turn on Airplane mode." "Show me the report for that run." "Generate test cases for https://github.com/acme/my-app."
8. Updating
Re-run the installer for your platform (macOS curl … | sh, Windows irm … | iex), then restart the agent. Confirm with the about tool — it reports the running version and whether a newer release exists.
9. Troubleshooting
- "Portal not ready" (Android) → run
setup_portal. If it returnsmanual_required, enable *Mahoraga Portal* under Settings → Accessibility. - adb / device not found → install Android platform-tools, ensure
adbis onPATH(Windows: setANDROID_HOME), and that the device shows underadb devices. - iOS `setup_device` signing fails (macOS) → set your team with
configure signing_team=, ensure your Apple ID is signed into Xcode → Settings → Accounts (with an *Apple Development* certificate in the keychain), and the iPhone is in Developer Mode + trusted. - Session expired / not authenticated → r