Skip to main content
Glama
gcamara

screen-recorder-mcp

by gcamara
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to screen-recorder-mcp

No user-submitted related servers found.

    Related Servers

    • Toru

      alifoo
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to record product demos, changelog GIFs, help-center guides, and bug repros by driving a signed-in browser or Mac window, then rendering branded MP4 and GIF outputs with delivery checks.
      1 npm
      1
      MIT

    • layershot

      Kishore180994
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to list open Windows app windows and screenshot any of them — covered, minimized, or in the background — without stealing focus or disrupting the user's work.
      MIT

    • screencast

      JHamidun
      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

    • Screencast MCP

      TMHSDigital
      A
      license
      B
      quality
      A
      maintenance
      Lets an agent capture the Windows desktop, a monitor, window, or region, then sample the footage into frames it can actually view so it can verify what happened on screen. It also exposes typed ffmpeg tools for trimming, cropping, scaling, redacting, annotating, zooming, and exporting recordings.
      57
      4,159 npm
      1
      Creative Commons Attribution Non Commercial No Derivatives 4.0 International
    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.5/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool targets a distinct lifecycle step or resource: discovery (list_targets, list_recordings), setup (pick_region), capture control (start/pause/resume/stop/cancel), and post-processing (trim_recording, export_gif). The only near-pair is stop_recording vs cancel_recording, and their descriptions make the keep-vs-delete difference explicit. An agent can select the right tool reliably.

    Naming Consistency4/5

    Names are uniformly snake_case with clear verb-led phrasing (list_targets, start_recording, pause_recording, trim_recording, export_gif). The lone deviation is recording_status, which is noun-first rather than verb_noun, though it is still readable and unambiguous. Overall predictable.

    Tool Count5/5

    11 tools is well within the sweet spot and each one maps to a concrete step of the recording workflow. There are no filler or redundant tools; pause/resume/cancel each earn their place as separate operations. The set is nicely scoped to the domain.

    Completeness4/5

    The surface covers the full capture lifecycle: target discovery, region selection, start, status, pause/resume, stop, cancel, history, trim, and GIF export. Minor gaps exist — there is no tool to delete a saved recording or inspect its duration/metadata, and no still-frame capture — but agents can work around these. Core workflows are fully supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources