Ascript MCP

What ascript-mcp MCP server does

The ascript-mcp MCP server connects AI coding tools with the AScript automation platform. It provides reference material for AScript APIs, access to the online plugin catalog, device inspection functions, and project lifecycle operations. The repository documents use with Claude Desktop, Cursor, and Trae; the supplied Cursor configuration runs the service locally through Python.

Documentation tools return platform overviews, module-level API references, keyword search results, code examples, and setup guidance. Plugin tools query the online AScript plugin library and retrieve individual plugin documentation. This gives an agent a way to look up supported APIs and extensions instead of relying only on generated code.

How it works

The local service communicates with the AI client through MCP. After a device is discovered or connected, the client can capture the screen, retrieve the control hierarchy, test selectors, recognize text with OCR, and perform multi-point color searches or comparisons. Device discovery includes local-network and ADB scanning, while automatic connection can use project configuration.

Project tools create projects on a device, upload files, execute or stop projects, and retrieve run logs. Android devices also support a debug execution mode that uses ADB, forwards port 5678, and returns an attach configuration for VS Code. The eval_python tool provides an interactive Python execution path on Android and iOS for testing code and compound automation logic. On iOS, the documented evaluation behavior translates ascript.android.* references to the corresponding iOS namespace and preloads computer-vision-related modules.

Setup and configuration

Install the package with pip install ascript-mcp. For Cursor, add an MCP entry in .cursor/mcp.json that invokes python -m ascript_mcp.local. The repository also provides agent-rule templates for Cursor, Claude Code, and other IDEs. Those instructions recommend checking device status and installed Python packages, validating important snippets with eval_python, and only then uploading and running a project.

For a network deployment, run the documented Uvicorn command for ascript_mcp.server:app on port 8000. The README specifies this SSE mode for API documentation queries only, so it should not be treated as an alternative interface for the full device-control workflow.

Tools and capabilities

The ascript-mcp MCP server groups its tools into five practical areas:

• API documentation and online plugin lookup.
• Device scanning, connection, status, and package inspection.
• Screen capture, UI-tree inspection, selector testing, OCR, and color analysis.
• Project creation, file upload, execution, debugging, stopping, and log retrieval.
• Project and file listing on connected devices.

The README identifies device status as Android-only, while installed-package listing and Python evaluation support Android and iOS. The project description also identifies Android, iOS, and Windows device control, but the detailed tool notes do not define equal feature coverage for every platform.

Limitations and notes

A connected or reachable device is required for device interaction and deployment operations. Some capabilities depend on platform-specific mechanisms such as ADB, and debug execution is documented for Android with ADB. The public SSE configuration is limited to documentation queries. No API key or paid service credential is specified in the provided material. The project is released under the MIT License.