exia-scenario-generator MCP Server
Related Servers
Alternatives to exia-scenario-generator MCP Server
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityBmaintenanceEnables AI assistants to generate complete Yukkuri-style commentary MP4 videos from a script, including synthesized speech, subtitles, illustrations, photos, BGM, and sound effects.MIT- AlicenseCqualityBmaintenanceEnables AI agents to play visual novels and galgames line by line, make reasoned choices, save/load/rewind, replay for hidden routes, and inspect scene visuals and CGs while keeping independent progress per agent.16847 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude to turn a topic into a narrated, animated explainer video by generating scenes, recording them frame by frame, synthesizing speech, and returning the finished MP4. It runs on an ordinary CPU-only computer without a graphics card, paid API, or other AI service.MIT
- AlicenseNot gradedqualityDmaintenanceA Unity C# plugin that enables AI assistants to write, edit, and test visual novel scripts via the Model Context Protocol, with tools for script CRUD, playback control, input simulation, and visual verification.2MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables comprehensive management of TyranoStudio visual novel projects including project creation, scenario editing with syntax validation, resource management, and TyranoScript development assistance. Supports project analysis, template generation, and Git integration for visual novel game development.2-
- AlicenseNot gradedqualityCmaintenanceIt enables agents to inspect dialogue workspaces, read and write .ezd scripts, generate character portraits, render previews, and export projects to Godot, PixiJS, JSON, or voice manifests over stdio or HTTP.MIT
TDQS
Scored across 4 tools
The tools appear to target distinct steps in a scenario generation workflow (setup, generate, save, explain), but the lack of descriptions makes it impossible to verify if there's overlap or ambiguity in their purposes. Without descriptions, an agent might guess incorrectly about boundaries, especially between generateScenario and exiaVoiceroidExplain.
Naming is inconsistent: generateScenario and saveScenario use camelCase, while exiaVoiceroidExplain and setupExia mix camelCase with unclear verb styles (e.g., 'exiaVoiceroidExplain' is a compound noun-verb hybrid). There's no predictable pattern across all tools, making them harder to parse as a set.
With 4 tools, the count is reasonable for a scenario generator server, suggesting a focused scope. It's not too thin or heavy, though the lack of descriptions makes it hard to assess if more tools might be needed for completeness.
Inferring from tool names, the domain is scenario generation with Exia/Voiceroid integration. The surface covers setup, generation, saving, and explanation, but without descriptions, it's unclear if there are gaps (e.g., listing, editing, or deleting scenarios). The absence of descriptions severely limits the ability to assess coverage, suggesting potential dead ends.