screen-record-mcp
Related Servers
Alternatives to screen-record-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI agents to start and stop native GNOME Shell screen recordings via MCP tools, returning JSON with file path, size, and duration without depending on ffmpeg or wf-recorder.3MIT
- AlicenseAqualityDmaintenanceEnables AI agents to start and stop full-screen recordings on macOS using FFmpeg, with control over quality, FPS, and audio.5MIT
- AlicenseAqualityBmaintenanceEnables agents to record their Linux X11 display while doing browser or computer-use work, then return a replay link when the task finishes without sending the video itself to the model.6Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables an LLM agent to control a local OBS Studio instance via obs-websocket, launching it, arranging scenes and sources, and starting or stopping recordings so it can capture its own screen as raw footage without manual intervention.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to create and manage macOS screen recordings through a semantic demo plan, including permission checks, source listing, and durable recording jobs.4 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to control Linux desktops and compositors, including Hyprland/Wayland window management, PipeWire audio routing, systemd diagnostics and self-healing, notifications, screenshots, and optional agent memory.MIT
TDQS
Scored across 3 tools
Each tool maps to a distinct phase of the recording lifecycle: start begins capture, stop finalizes the file, and check_recording_status is a read-only query. There is no plausible confusion between starting, stopping, and inspecting a recording.
All three tools use snake_case with a verb_noun pattern (start_recording, stop_recording, check_recording_status). The convention is uniform and immediately readable.
Three tools exactly cover the lifecycle of a single-domain screen recorder, and each one earns its place with no filler. The surface is lean but appropriately scoped for a narrowly focused server.
Start, stop, and status form a complete lifecycle with no dead ends, and status even exposes the output path. Minor gaps exist: no pause/resume and no way to enumerate or manage prior recordings, though these are easily worked around.