demo-director
Related Servers
Alternatives to demo-director
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceMCP server that turns any running web app into demo videos, interactive walkthroughs, and marketing captures via one command. Enables AI agents to show their work with regenerated demos on every PR.7 npm4MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for recording and validating Chrome extension demo videos from YAML beat sheets, enabling agents to script and generate pixel-perfect videos.33 npmMIT
- FlicenseAqualityBmaintenanceAn MCP server that auto-generates presentations from a topic using AI, supporting slide editing, visual QA, and export to HTML/PPTX.307-
- AlicenseNot gradedqualityCmaintenanceAn MCP server that gives AI agents real browser capabilities including screenshotting, action execution, data extraction, and multi-persona auditing for frontend validation.75 npm6MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server and CLI that lets AI agents generate native PowerPoint decks with slides, tables, and speaker notes.MIT
- FlicenseNot gradedqualityCmaintenanceAn MCP server that gives AI agents mouse-and-keyboard control over a live Chrome session, enabling navigation, clicking, typing, screenshots, and DOM inspection.11 npm-
TDQS
Scored across 26 tools
Each tool targets a distinct action within the demo workflow. Chrome tools are prefixed, input tools are clear, and narration/recording tools are separated. Even similar tools like chrome_scroll vs scroll and narrate vs render_narration have explicit descriptions distinguishing their use cases, so there is no real ambiguity.
The server mostly uses snake_case with verb_noun structure, and several prefixes (chrome_, mouse_) improve organization. However, some tools are bare verbs (pause, scroll, narrate) and others are nouns without verbs (recording_status, screen_info, voicebox_status, chrome_page_text), which breaks the otherwise consistent pattern.
The 26 tools cover a wide scope: browser automation, input simulation, screen recording, narration, and video composition. Many tools are essential for distinct steps, but the count feels heavy; a few utility tools (e.g., chrome_clear_highlight, recording_status) could be parameters of other calls, making the set marginally over-scoped.
The tool set provides a full workflow from environment setup (check_setup) through interaction (Chrome and input tools), recording (start/stop), narration (render/mux), and final cut (compose_final_video). There are no obvious dead ends; each stage has the necessary operations.