A
licenseA
qualityB
maintenanceEnables MCP clients to access a local computer through a controlled, permission-based tool surface for read-only or developer-mode file, process, and terminal operations.
6
MIT
VRCH MCP
by VrchStudio
Related Servers
Alternatives to VRCH MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to inspect and control connected iPhones, iPads, and iOS simulators through local Mac tools, including device previews, UI and OCR inspection, builds, and session-bound approvals.GPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables compatible AI apps to observe and control a locally connected iPhone through stdio MCP tools for screenshots, taps, swipes, long presses, text entry, key and button presses, app listing, and app launching, all reusing the console's device session.GPL 3.0
- AlicenseAqualityBmaintenanceA local, stdio-only Model Context Protocol server that lets coding agents inspect, control, and test Apple iOS Simulators and Google Android Emulators. It exposes 29 typed tools for device lifecycle, app management, UI automation, screenshots, logs, permissions, location, and platform-specific test conditions.29MIT
- AlicenseNot gradedqualityBmaintenanceEnables cloud AI agents to securely connect to a local Windows machine and execute tools such as system info, file operations, browser automation, and coding tasks through the Model Context Protocol.MIT
- AlicenseDqualityBmaintenanceEnables controlled local developer operations including file and process management, shell execution, SSH, WSL, Docker, Git, browser and desktop automation, media processing, and asynchronous jobs through MCP.146MIT
TDQS
B3.3/5.0
Scored across 33 tools
Disambiguation3/5
Many tools have clear individual purposes, but the app lifecycle and input surfaces contain close variants: apps_save vs apps_publish, apps_control vs apps_interface_input vs apps_host_input, and apps_import_commit vs apps_file_commit. The verbose descriptions clarify boundaries, but agents must read carefully to avoid misselection.
Naming Consistency3/5
All names are snake_case and mostly domain-prefixed with apps_, file_, terminal_, or ai_, which is readable. However verb/noun style is mixed: many tools are verb-led (apps_create, file_upload) while others are state/noun-led (apps_state, apps_operation_status, apps_input_targets), and take_screenshot is unprefixed.
Tool Count2/5
33 tools is heavy for one server and exceeds a well-scoped surface. Although the domain is broad, many tools are narrow lifecycle or transfer-phase variants, increasing selection burden and redundancy risk.
Completeness4/5
The surface covers connection, terminal interaction, screenshots, app lifecycle, package/file transfer, input control, and capability reporting. Some gaps remain, such as app deletion/rename and file listing, but core workflows are substantially covered.
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues