Quash — Mobile App Automation MCP Server

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

Local serverstdio

What is the Quash — Mobile App Automation MCP Server?

Quash — Mobile App Automation is an MCP integration. Drive Android & iOS mobile-app automation from your AI agent on locally connected devices.

Packages and local setup

The published mcpb package is https://github.com/Oscorp-HQ/quash-mcp-releases/releases/download/v1.1.0/quash-mcp.mcpb. Its declared MCP transport is stdio.

The package declares QUASH_SIDECAR_CMD (required): Path to the Quash automation engine (sidecar) installed by the Quash installer.; QUASH_API_TOKEN: Quash API token (qsh_…). Optional if you sign in with Google via the auth tool.; QUASH_TEST_GEN_AGENT_CMD: Command for the test-case generator installed by the Quash installer..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 1.1.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
QUASH_SIDECAR_CMDPath to the Quash automation engine (sidecar) installed by the Quash installer.Yes
QUASH_API_TOKENQuash API token (qsh_…). Optional if you sign in with Google via the auth tool.Optional
QUASH_TEST_GEN_AGENT_CMDCommand for the test-case generator installed by the Quash installer.Optional