dinoctor-mcp
Related Servers
Alternatives to dinoctor-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceEnables Claude, Cursor, or any MCP client to create consistent AI characters, generate Veo 3.1 and Omni videos, edit clips, build scenes, export MP4s, and chat with Google Flow's creative agent. Automates AI video production workflows such as reels, storyboards, and multi-shot stories through natural language, with credit guardrails and dry-run pricing.2316MIT
- AlicenseNot gradedqualityCmaintenanceTurns a plain-language request into a narrated vertical motion graphics video with natural voice, word-by-word synced animation, music and sound effects, rendered locally as an MP4 ready for Reels, TikTok and Shorts. Validates scripts and estimates OpenAI API cost before spending credits, and works inside MCP-capable assistants like Claude Code, Claude Desktop or Cursor.MIT
- AlicenseBqualityBmaintenanceEnables AI agents to take a raw script all the way to a finished, downloadable short-drama .mp4, covering AI rewrite, character consistency, storyboards, frames, video shots, TTS voiceover, and final cut with quote-before-spend billing from any MCP client.1324,605 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to generate professional storyboards and videos from scripts or creative descriptions via MCP-compatible clients.37 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI clients to generate animated videos from natural language prompts, handling scriptwriting, voiceover synthesis, and MP4 rendering.MIT
- FlicenseNot gradedqualityAmaintenanceEnables Claude to control a full-stack video editor by issuing commands to add clips, text, animations, and render MP4 videos, with changes reflected in real-time in the browser UI.-
TDQS
Scored across 69 tools
Most tools map to distinct resources or actions, and many descriptions explicitly redirect to the right alternative. However, several overlapping families create real ambiguity: use_style vs. set_style, generate_* vs. draw_* vs. upload vs. put_picture, speak vs. own_voice vs. assign_line/write_script, and multiple ways to open content (open_project, templates open, samples open, new_project). The detailed cross-references help, but the 69-tool surface is still hard to navigate.
All names use snake_case, so casing is consistent and readable. But the convention mixes noun-only tools (voices, music, cast, act, words, camera, light, place, keys, transition, library, samples, templates, status, look) with verb-based tools (get_project, add_shot, remove, generate_picture, cancel_render), so there is no predictable verb_noun pattern.
The domain is genuinely broad — project editing, style building, AI picture/voice generation, rendering, audio, scripts, samples and templates — so some breadth is justified. Still, 69 tools is far beyond a typical well-scoped set and likely overwhelms tool selection; it would benefit from grouping or splitting into narrower servers.
The surface covers nearly the full lifecycle: project open/save/list, scene/shot CRUD, casting, acting, text, camera, lighting, places, keyframes, transitions, script and voice handling, sound/music, rendering, style management, generation, uploads, samples and templates. Minor gaps remain, such as no explicit undo/redo tool, no project deletion, and limited deletion/management for media or generated pictures.