tourwright
Related Servers
Alternatives to tourwright
No user-submitted related servers found.
Related Servers
- 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.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to record narrated, zoom-animated product demo videos of websites entirely on-device, including outlining pages, scripting tours, recording MP4s, reviewing frames, and extracting embedded recipes to fork or rerender demos.15 npm4MIT
- 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 gradedqualityBmaintenanceEnables AI agents to film tabs, apps, or simulators while driving them, then render narrated demo videos with zoom effects, cursor and click visuals, captions, backgrounds, and share pages.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to film and edit polished screen recordings of any website or desktop app from a simple JSON scenario, complete with smooth cursor motion, automatic zooms, callouts, captions, title cards, and optional voice-over.391 npm3MIT
- AlicenseAqualityAmaintenanceYour coding agent makes the demo video — turns a storyboard.json into a narrated, captioned product-demo MP4; deterministic replay re-renders it in CI at ~$0.241,736 npm25MIT
TDQS
Scored across 8 tools
Each tool maps to a distinct resource or action, and the descriptions explicitly contrast the two closest pairs (validate vs check: offline structure vs live targets; render vs check: video output vs failure report). The only friction is the singular/plural pair tourwright_job vs tourwright_jobs, which relies on the reader noticing one letter.
All names share the tourwright_ prefix and snake_case, with verb-style tools (validate, check, render, delete_job) alongside plural-noun list/query tools (jobs, job, voices, guide). This is a readable REST-like pattern, but the mix of explicit verbs and bare nouns (no list_ prefix) is not a single uniform convention.
Eight tools is well within the sweet spot and each one earns its place: two-step validation, dry-run checking, rendering, job inspection, cleanup, documentation, and voice discovery. Nothing looks like filler or a duplicated capability.
The authoring-to-render lifecycle is largely covered (guide, voices, validate, check with auto-fix, render, list/get/delete jobs). However, delete_job explicitly refuses queued or rendering jobs and there is no cancel/stop tool, so a running render is a dead end the agent cannot recover from; there is also no re-render or script retrieval operation.