Recordful MCP
Related Servers
Alternatives to Recordful MCP
No user-submitted related servers found.
Related Servers
AlicenseAqualityBmaintenanceTurns your AI host into a product videographer — scripted screen recordings of your own web app with a gliding cursor, camera zooms, highlight callouts, captions, and branded transitions, plus marketing-grade screenshots. Automatic dark-frame cleanup and MP4/GIF export. Free, MIT, 100% local — no account, no API keys.1466 npm3MIT- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to drive the user's real, already-logged-in Chrome browser locally, so they can read and navigate pages, click, type, fill forms, take screenshots, and inspect cookies, tabs, console, and network traffic without headless browsers or remote-debugging ports.3 npmISC
- AlicenseNot gradedqualityBmaintenanceEnables an AI agent to operate a web app, record a deterministic session, and compile an editable project into a polished MP4 with zooms, cuts, captions, callouts, and reproducible renders.MIT
- AlicenseNot gradedqualityNot gradedmaintenanceLets local AI agents drive the Chrome browser a user already has open, including signed-in sessions, by listing tabs, reading page text and actionable elements, then clicking, filling, selecting, scrolling, navigating, and capturing viewport screenshots without exporting cookies. Runs as a dependency-free local stdio process over Native Messaging, with per-tab leases, automatic reconnection, and pause/write-action controls.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to create polished product demo videos by controlling a real Chromium browser, recording actions, and rendering 1080p MP4s with narration, captions, and styled overlays.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to browse, click, and debug real websites in the user's own signed-in browser or a dedicated Chrome instance, with only explicitly shared tabs reachable and revocable at any time. Exposes the full developer toolbox — console, network, sources, debugger, elements, performance and CPU/memory profiling, storage, service workers, coverage, emulation, accessibility, security, Lighthouse, and Playwright-test recording — as first-class tools callable in one step.249 npm1MIT
TDQS
Scored across 14 tools
Each tool maps to a distinct action within its domain: recording lifecycle (start/stop/pause/resume), browser control (navigate/click/type/press/scroll/snapshot/wait_for), and diagnostics. The only mild overlap is get_status vs probe_capture, which both report connection and permission state, but their descriptions distinguish state reporting from a pre-capture diagnostic check.
All names are lowercase snake_case, which is consistent, and the recording tools follow a clean verb_noun pattern (start_recording, stop_recording, pause_recording, resume_recording). However, browser tools mix single verbs (click, type, press, scroll, snapshot) with verb_noun forms (get_status, probe_capture, wait_for), a minor deviation from a single predictable pattern.
14 tools is well within the ideal range and each earns its place: a full recording lifecycle, a coherent browser-automation set, and two diagnostics. Nothing feels redundant or padded for the server's stated scope.
The surface covers recording control and the core automation primitives (navigate, snapshot, click, type, press, scroll, wait_for) with file editing via navigate. Minor gaps exist, such as no dedicated hover or select-option helper, but these are largely workable via click/type/press.