kinoscripter
Related Servers
Alternatives to kinoscripter
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables agents to drive a local explanatory-video lab over stdio: inspecting and patching declarative scenes and a multilayer timeline (clips, titles, captions, voice, music), querying media and frames, rendering previews, running recoverable jobs, and exporting bundles. It also handles Kdenlive round-trip sync plus checkpoints, undo and restore, all offline with JSON responses.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to open, edit, check, run, emit, and save source programs through structured, revision-checked tools over stdio, confining paths to the launch root and returning diagnostics with fixes for rejected edits.6 npm2Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables Claude and other AI agents to work directly in a local-first planning vault stored as plain JSON files, so they can read and edit kanban boards, plans, notes and decisions alongside the user. Every change made by an agent is recorded in history and can be undone.1MIT
- AlicenseAqualityAmaintenanceEnables AI clients to inspect and carefully edit a bounded local workspace via stdio, with a read-only default, conflict-safe updates, and no network listener or telemetry.102Apache 2.0
- AlicenseNot gradedqualityCmaintenanceGives MCP-capable agents read and write access to a SilverBullet space, letting them list, read, create, overwrite, append to, delete, and substring-search markdown pages. It forwards tool calls to SilverBullet's built-in /.fs HTTP API over either stdio or token-gated streamable HTTP, with no changes needed inside SilverBullet itself.18 npmMIT
- AlicenseCqualityBmaintenanceEnables AI agents to list, read, inspect, write, and precisely edit files and to regex-search a workspace, with every path confined to a sandboxed root directory. Token-saving output such as line-range reads and match locations without line content keeps context use low while guarded writes and ambiguous edits prevent accidental data loss.6MIT
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: listing/reading/creating scripts, inserting beats/scenes/acts, editing beats, and validating structure. The insert versus edit distinction is clear, and hierarchical inserts are separated by structural level.
All tool names follow a consistent snake_case verb_noun pattern: list_scripts, read_script, create_script, insert_beat, edit_beat, insert_scene, insert_act, validate_script. There are no mixed conventions or vague standalone verbs.
Eight tools is well-scoped for a script-editing server with acts, scenes, and beats. Each tool maps to a meaningful operation without obvious redundancy or unnecessary surface area.
The core workflow of creating, reading, inserting, editing beats, and validating is covered, but there are no delete/remove operations for scripts, acts, scenes, or beats. Scene/act editing and reordering/moving are also absent, leaving notable lifecycle gaps.