leemysw/yovoice
Related Servers
Alternatives to leemysw/yovoice
No user-submitted related servers found.
Related Servers
- AlicenseCqualityAmaintenanceOpen-source local-first AI media workbench with Canvas, video editor, Assets, and MCP control.38326Apache 2.0
- AlicenseNot gradedqualityDmaintenanceLocal AI generation for images, audio, speech, and 3D models using open source models.3GPL 3.0
- AlicenseNot gradedqualityAmaintenanceGives Claude Code, Claude Desktop, Cursor and any other MCP client a local sound studio that turns plain-language requests into background music, instrument loops and sound effects, then re-styles, regenerates or extends them and exports seamless loops, fades and loudness-normalized WAV, OGG or FLAC files. Everything runs on Apple Silicon with no cloud service and no API key.548MIT
- AlicenseAqualityAmaintenanceAudio perception for AI agents. Measure loudness, clipping, noise and pitch; view spectrograms; split audio into events; transcribe speech; compare before/after; and clean up, edit or synthesize sound. Runs locally, no API keys.14130 PyPIMIT

postward-creative-mcpofficial
AlicenseBqualityBmaintenanceEnables AI assistants to generate images, videos, music, and voiceovers with your own provider keys, and edit video locally with ffmpeg — all on your machine with no account, watermark, or telemetry.3540 npmMIT- AlicenseNot gradedqualityCmaintenanceEnables AI agents to speak and listen in real-time with interruption handling, using local ML models and hot-swappable adapters.6 npm1MIT
TDQS
Scored across 9 tools
Most tools target clearly different resources or actions (upload_voice, list_voices, list_models, render_score, cancel_generation are all distinct). The only real overlap is generate vs submit_generation (sync vs async) and status vs get_generation, but the descriptions explicitly explain the difference and which to prefer, so an agent can choose correctly.
Seven of nine names follow a clean verb_noun pattern (list_voices, list_models, get_generation, submit_generation, cancel_generation, upload_voice, render_score). The bare noun 'status' and bare verb 'generate' are the only deviations, and both remain readable.
Nine tools is well within a comfortable range and every tool maps to a distinct need: voice import/listing, model discovery, engine status, sync/async generation, polling, cancel, and score rendering. Nothing feels padded or missing at the count level.
The voice lifecycle (upload → list → generate → poll → cancel) plus model discovery and score rendering is covered end to end. Minor gaps exist: no delete/replace voice, and no way to list past generations without knowing a requestId, but agents can work around these.