Quash MCP

The Quash MCP server connects Quash mobile-app automation to the AI agent you already work in. With it installed, Claude Code, Claude Desktop, or Cursor can drive real automation on a connected device. You describe what you want in plain language, and the agent runs it.

What you can do

Once it's connected, the agent can reach the full Quash workflow:

• Run tests.

  Run a natural-language test task on the device and stream the result back live.

• Generate test cases.

  Build test cases from a prompt, from files, or straight from a git repo.

• Manage apps and builds.

  List your org's apps, list builds, and install a build's APK on the device.

• Review results.

  Browse recent runs, pull a run's report and share link, and check your plan usage and limits.

You don't memorize any commands. You ask the agent in plain language and it picks the right tool.

Get the Mobile Testing Playbook Used by 800+ QA Teams

Discover 50+ battle-tested strategies to catch critical bugs before production and ship 5-star apps faster.

Email addressGet Instant Access

100% Free. No spam. Unsubscribe anytime.

The MCP tools

For reference, here's the full set of tools the agent has access to:

about

auth

connect

configure

setup_portal

setup_simulator

setup_device

execute

generate_test_cases

usage

list_apps

builds

install_build

runs

test_cases / suites

Platform support

On macOS (Apple Silicon) you get both Android and iOS automation. On Windows (x64) the server is Android only, because iOS automation depends on Apple's macOS-only toolchain.

It works across emulators and physical devices: Android physical devices and emulators on both platforms, plus iOS simulators and physical iPhones on macOS.

Install

One command installs the server and auto-registers Quash in every supported agent it finds.

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

You'll need adb on your PATH, a connected device or emulator with USB debugging on, and a Quash account. To authenticate, generate an API token in the desktop app under Settings → Integrations (it starts with qsh_). Set it as QUASH_API_TOKEN and the server signs in automatically on startup. Prefer no token? The agent can run a Google browser sign-in instead.

Getting started

"Use Quash: connect, then run setup_portal if needed."        (Android)"Use Quash: connect, then setup_simulator."                   (iOS simulator on 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."

Full setup steps and troubleshooting live in the setup guide.

The Quash MCP server is available today. Install it, connect a device, and run your first test without leaving your agent.

Frequently Asked Questions

What is the Quash MCP server? It's a server that connects Quash mobile-app automation to an AI agent (Claude Code, Claude Desktop, or Cursor), so the agent can run tests, generate test cases, manage builds, and pull reports on a connected device using plain language.

Which platforms does it support? macOS (Apple Silicon) supports both Android and iOS, including simulators and physical iPhones. Windows (x64) is Android only.

Can I run iOS tests on Windows? No. iOS automation requires Apple's macOS-only toolchain, so iOS coverage needs a Mac.

How do I authenticate? Generate an API token in the desktop app under Settings → Integrations and set it as QUASH_API_TOKEN for automatic sign-in, or have the agent run a Google browser sign-in.