Ascript Mcp
Drive real Android, iOS, and Windows devices from Claude or Cursor through MCP for UI automation and mobile QA without jailbreaking iOS.
Overview
AScript MCP is an MCP server for the Build phase that lets agents control Android, iOS, and Windows devices for automation and testing, including non-jailbroken iOS workflows.
What is this MCP server?
- Controls Android, iOS, and Windows devices from MCP-compatible AI tooling
- iOS automation path without jailbreak per project positioning
- PyPI package ascript-mcp v1.7.0 with uvx runtime hint and stdio transport
- Bridges mobile/manual QA into agent loops for indie app builders
- PyPI package ascript-mcp version 1.7.0 with uvx runtime hint
- stdio MCP transport; supports three host OS families per description
What problem does it solve?
Your agent can write mobile code but cannot press buttons on a real phone or PC, so mobile bugs reproduce slowly across three platforms.
Who is it for?
Solo builders shipping mobile or desktop companion apps who want one MCP bridge for tri-platform device control from their agent IDE.
Skip if: Web-only SaaS teams with no native clients, or shops that forbid device automation for compliance reasons.
What do I get? / Deliverables
After registration, the agent can execute device-level actions on Android, iOS, and Windows for faster multi-platform verification.
- Agent-executed UI flows on Android, iOS, and Windows
- Repeatable device smoke tests without manual tapping
- Faster reproduction of cross-platform mobile defects in agent sessions
Recommended MCP Servers
Journey fit
Cross-platform device control is a build-time capability when you wire agents into mobile clients, desktop companions, or multi-platform test flows. Agent-tooling fits because the server extends what your coding agent can touch beyond the repo—physical or emulated devices on three OS families.
How it compares
Tri-platform device-control MCP, not App Store Connect metadata tooling or a single-platform Android-only ADB cheat sheet.
Common Questions / FAQ
Who is AScript MCP for?
Indie and solo developers using MCP agents who test Android, iOS, and Windows apps and want hands-on device control from the same client as their code.
When should I use AScript MCP?
Use it when you need agent-driven UI walks, smoke tests, or debugging on real devices across mobile and Windows desktop targets.
How do I add AScript MCP to my agent?
Install or run ascript-mcp from PyPI (uvx ascript-mcp per schema hint), add it as a stdio MCP server in Claude Code or Cursor, connect devices per AScript docs, then invoke tools from a chat.