Skip to main content
Glama
sorinqu-org

cvision-mcp

by sorinqu-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to cvision-mcp

No user-submitted related servers found.

    Related Servers

    • Clara Windows UI MCP

      BestCodeTools
      F
      license
      B
      quality
      C
      maintenance
      Enables local Windows UI automation and screen capture, targeting windows that are difficult to automate such as games and legacy apps, with tools for window management, mouse and keyboard input, and desktop capture.
      8
      -

    • macos-desktop-control

      d-wwei
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides native macOS desktop automation for AI agents, enabling screen capture, mouse/keyboard control, window management, and iOS/Android simulator control in both foreground and background modes without focus stealing.
      3
      MIT

    • Extra

      AIYantra
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to autonomously control Windows 11 and 10 desktops via sub-10ms screen capture, native UI Automation element inspection, and zero-lag keyboard and mouse input. Combines a visual plane with a semantic plane and stall detection so agents can operate real applications reliably without vision-only guessing.
      223 npm
      4
      MIT

    • tiance-gui

      LikeMirage
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI to operate Windows applications through recursive grid-based screenshot navigation and proportional coordinates, with UIAutomation, mouse/keyboard control, sequential batch actions, and input locking.
      Apache 2.0
    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

    A3.9/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct action: listing, capturing, clicking, typing text, sending special keys, or launching an isolated app. Even the two keyboard tools are clearly separated by text input versus key events.

    Naming Consistency3/5

    The naming is readable but mixes conventions: list_windows, capture_window, and launch_isolated_app start with verbs, while window_type, window_send_key, and window_click use a noun-first prefix. The window_ prefix is recognizable but not applied consistently across all window-targeting tools.

    Tool Count5/5

    Six tools is a well-scoped set for background desktop automation. Each tool serves a clear purpose without unnecessary bloat or redundancy.

    Completeness4/5

    The surface covers the core workflow of discovering windows, capturing them, sending input, and launching isolated apps. Minor gaps exist, such as window management actions like moving, resizing, or closing windows, but these are not essential for the primary automation use case.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources