agent-recorder-mcp
Related Servers
Alternatives to agent-recorder-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables browser automation for LLMs on Linux display servers, supporting web interaction, screenshots, and JavaScript execution in a real browser.714 npm7MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to see and control an existing Linux X11 desktop over SSH by taking screenshots and performing mouse, scroll, typing, and keyboard-shortcut actions across browsers, terminals, file managers, and other apps.MIT
- AlicenseAqualityBmaintenanceEnables an agent to see and operate a GNOME Wayland desktop like a human, including screenshots, mouse/keyboard control, accessibility tree access, OCR, clipboard, and audio listening.13MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to capture screen and voice recordings, extract timestamped frames, and receive structured Markdown reports with context for bug fixing and UI feedback.22 npm18MIT
- AlicenseAqualityDmaintenanceEnables AI agents to start and stop full-screen recordings on macOS using FFmpeg, with control over quality, FPS, and audio.5MIT
- AlicenseAqualityCmaintenanceEnables LLMs to capture desktop screenshots and control the mouse and keyboard on Linux, including Wayland, through MCP.11MIT
TDQS
Scored across 6 tools
Each tool maps to a distinct lifecycle stage (start, status, finish, abort, cleanup, confirmUpload), so boundaries are mostly clear. Minor overlap exists between cleanupRecording, abortRecording(deletePartial), and finishRecording(cleanup) since all three can delete the local file, which could cause some hesitation.
Five of six tools use a consistent verb+Recording/Upload camelCase pattern (startRecording, finishRecording, abortRecording, cleanupRecording, confirmUpload). recordingStatus breaks the verb-first convention by being noun-first, a minor deviation.
Six tools is well-scoped for a capture-and-share recorder, with each tool earning its place across the start/stop/abort/share/cleanup lifecycle. No redundant or bloated entries.
The surface covers the full recording lifecycle from start through sharing and cleanup, including the Google Drive handoff path. It lacks discoverability operations like listing past recordings or retrieving an existing file, but core workflows are complete.