Skip to main content
Glama
VrchStudio

VRCH MCP

by VrchStudio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to VRCH MCP

No user-submitted related servers found.

    Related Servers

    • mobile-simulator-emulator-mcp

      gitsoufiane
      A
      license
      A
      quality
      C
      maintenance
      A 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.
      29
      MIT

    • Codex Local Ops

      hattimon
      A
      license
      D
      quality
      B
      maintenance
      Enables 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.
      146
      MIT

    • DesktopBridge

      jameymcelveen
      A
      license
      A
      quality
      B
      maintenance
      Enables local macOS automation via the Model Context Protocol, allowing file operations, system monitoring, shell commands, clipboard access, and screenshots with configurable security restrictions.
      14
      MIT

    • AutoBot MCP

      yz0903
      F
      license
      B
      quality
      D
      maintenance
      Enables remote control and automation of Android devices through the Model Context Protocol, supporting UI interactions, app management, ADB commands, screenshots, and device information retrieval via AutoBot API.
      53
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 30 tools

    Disambiguation3/5

    Descriptions work hard to distinguish tools (device App vs preview vs shell), but three input tools—apps_control, apps_interface_input, apps_preview_input—overlap heavily in purpose, and apps_save/apps_publish both describe publishing a draft. An agent could realistically misselect among these.

    Naming Consistency4/5

    Nearly all tools use snake_case with clear domain prefixes (terminal_, apps_, file_, ai_), giving a predictable namespace. take_screenshot breaks the prefix convention slightly, but overall it's consistent and readable.

    Tool Count2/5

    30 tools exceeds the 25+ threshold that signals an over-stuffed surface for a single server. While the domain (terminal + Apps + file transfer) is broad, several tools could plausibly be merged, making this heavy relative to scope.

    Completeness4/5

    Coverage is strong: Apps lifecycle (create/open/save/publish/launch/exit), file transfer with pause/resume/cancel, input, import/export, and status/recovery tools are all present. Minor gaps around some session lifecycle edges, but no dead ends for core workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources