Skip to main content
Glama
Corvus400

video-capture-mcp

by Corvus400
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to video-capture-mcp

No user-submitted related servers found.

    Related Servers

    • recit

      codedbytahir
      A
      license
      Not graded
      quality
      B
      maintenance
      Free, open-source screen recording MCP server for AI agents. Enables screen capture, screenshots, and frame extraction locally without cloud dependencies.
      8 npm
      1
      Apache 2.0

    • Mobile Device MCP

      srmorete
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that lets AI agents control iOS and Android devices (tap, scroll, type, take screenshots, read UI trees, and run code). Works with multiple devices at the same time.
      73 npm
      46
      MIT

    • scrcpy-mcp

      JuanCF
      A
      license
      A
      quality
      A
      maintenance
      MCP server that gives AI agents full vision and control over Android devices via ADB and scrcpy. Supports screenshots, input, apps, UI automation, shell, files, and clipboard.
      38
      302 npm
      96
      MIT

    • OpenEyes

      yangpeng366
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server providing AI-friendly computer-use primitives (capture, detect, click) to let LLM agents drive desktop GUI applications on Windows, macOS, and Linux.
      1
      MIT

    • phone-harness

      ZachDreamZ
      A
      license
      Not graded
      quality
      A
      maintenance
      Controls Android and iOS devices from AI agents through a token-efficient MCP server, enabling observation, tapping, typing, gestures, navigation, assertions, and safety-gated actions.
      MIT
    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

    A4.4/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool has a distinct purpose: permissions check, cleanup, frame extraction, window region detection, pointer movement, session management, and various recording start/stop variants. Even similar tools like start_recording and start_app_window_recording are clearly differentiated by target and use case.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., check_macos_permissions, list_active_sessions, stop_recording). No mixing of camelCase or inconsistent verb styles.

    Tool Count5/5

    With 12 tools, the server covers setup, recording, extraction, pointer control, and session management without being bloated. Each tool serves a clear function, and the count is appropriate for the domain.

    Completeness4/5

    Core workflows (record, stop, extract, cleanup, permissions) are covered. Minor gaps exist, such as no explicit tool to list available iOS simulators or Android devices, but the overall surface is comprehensive.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources