Skip to main content
Glama

Related Servers

Alternatives to ClipQA MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Gives MCP-capable AI tools running on Windows sight of the user's desktop: it captures the window being looked at, any monitor, window or region, and offers OCR, text finding, full-resolution zooming, snips, hotkey marks, visual baseline comparison and waiting for screen changes. Sensitive apps and windows are blacked out before any image reaches the AI client.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables an AI agent to operate Windows applications through vision-driven UI Automation and record polished demo videos with pre-click camera zoom, narration, and cinematic effects.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to launch, inspect, and operate WPF, WinForms, and WinUI desktop applications through UI Automation, with compact snapshots, background actions, state verification, and export to regression tests.
      17
      MIT

    TDQS

    B3.3/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool maps to a distinct stage of the recording workflow—discover, start/stop, annotate, list, inspect frames—so selection is generally clear. The only mild overlap is between inspect_clip and get_frames, which both retrieve visual data from a completed recording, but their descriptions clarify the different output forms.

    Naming Consistency5/5

    All tool names use a consistent snake_case verb_noun pattern (list_windows, start_recording, stop_recording, mark_event, list_sessions, inspect_clip, get_frames). There are no irregular verbs, abbreviations, or mixed casing to confuse an agent.

    Tool Count5/5

    Seven tools is right-sized for this server's purpose: a focused QA clip recording and inspection workflow. Each tool represents a necessary operation with no redundant helpers or bloat.

    Completeness4/5

    The core lifecycle is covered: discover windows, start/stop recording, mark events, list completed sessions, and inspect clips via contact sheets or exact frames. The main gaps are housekeeping and retrieval—there is no delete/cleanup session tool and no way to fetch the raw clip file itself, though these may be outside the server's designed scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues