autojs-pro-mcp

Standalone MCP server for pushing Auto.js Pro 9.3+ projects. It does not depend on VS Code.

Supported workflow

MCP client
  -> LAN discovery through _autojsprodebug._tcp (with ADB fallback)
  -> Auto.js Pro ws-rpc authorization
  -> incremental project synchronization

Legacy TCP 9317 devices are detected but intentionally not connected.

Install from npm

Install the published package globally or let an MCP client run it through npx:

npm install -g autojs-pro-mcp

For MCP clients, use this configuration:

{
  "mcpServers": {
    "autojs": {
      "command": "npx",
      "args": ["-y", "autojs-pro-mcp"],
      "env": {
        "AUTOJS_PROJECT_DIR": "/absolute/path/to/project",
        "AUTOJS_PROJECT_NAME": "my-project"
      }
    }
  }
}

The MCP process must run on the host computer with local-network permission; containerized stdio processes may not be able to access Bonjour or LAN devices.

Development

pnpm install
pnpm check
pnpm start
pnpm start:http

MCP configuration

{
  "mcpServers": {
    "autojs": {
      "command": "node",
      "args": ["/absolute/path/to/autojs-pro-mcp/dist/index.js"],
      "env": {
        "AUTOJS_ADB_PATH": "/absolute/path/to/platform-tools/adb",
        "AUTOJS_PROJECT_DIR": "/absolute/path/to/default/project",
        "AUTOJS_PROJECT_NAME": "remote-project-name"
      }
    }
  }
}

Optional environment variables:

• AUTOJS_ADB_PATH: ADB executable
• AUTOJS_PROJECT_DIR: default project directory
• AUTOJS_PROJECT_NAME: remote project directory name
• AUTOJS_MCP_STATE_DIR: persistent client UUID directory
• AUTOJS_REQUEST_TIMEOUT_MS: JSON-RPC timeout
• AUTOJS_SYNC_TIMEOUT_MS: project synchronization timeout
• AUTOJS_SCAN_TIMEOUT_MS: LAN device scan window, default 3000 ms
• AUTOJS_MCP_HOST: standalone HTTP bind address, default 127.0.0.1
• AUTOJS_MCP_PORT: standalone HTTP port, default 32129

MCP tools

• autojs_status
• autojs_scan_devices
• autojs_connect
• autojs_disconnect
• autojs_push_project
• autojs_run_project
• autojs_push_file
• autojs_run_file
• autojs_list_executions
• autojs_stop_execution
• autojs_rerun
• autojs_get_logs
• autojs_clear_logs
• autojs_vfs_info
• autojs_list_files
• autojs_stat_file
• autojs_watch_directory
• autojs_read_file
• autojs_write_file
• autojs_create_directory
• autojs_move_file
• autojs_delete_file
• autojs_download_file
• autojs_download_directory
• autojs_upload_directory
• autojs_stop_all

Multiple devices may remain connected at the same time. Pass deviceId to bind an operation to a specific device. autojs_get_logs supports long polling with afterSequence and waitMs; autojs_watch_directory uses a returned snapshot token for VFS change polling. VFS paths are confined to the root reported by the device.

The tool scans the LAN automatically, then only pushes the directory supplied through projectDir (or AUTOJS_PROJECT_DIR). Build and obfuscation remain the caller's responsibility; for an already-built client, pass its artifact directory such as dist-obf.

/{script-dir} is an Auto.js Pro built-in device path and maps to /storage/emulated/0/脚本. If remoteDir is omitted, project pushes use /{script-dir}/{projectName} by default.

Standalone HTTP service

Start the service from iTerm so its Node process inherits iTerm's local-network permission:

AUTOJS_PROJECT_DIR=/absolute/path/to/project AUTOJS_PROJECT_NAME=my-project pnpm start:http

The MCP endpoint is http://127.0.0.1:32129/mcp; health status is available at http://127.0.0.1:32129/health. Override the bind address and port with AUTOJS_MCP_HOST and AUTOJS_MCP_PORT.