A
licenseNot graded
qualityB
maintenanceEnables MCP-capable chat clients to synthesize speech from text, convert it with a local RVC voice model, and render the result in an inline audio player.
MIT
Dot RVC Bridge
by EllaZhangCA
Related Servers
Alternatives to Dot RVC Bridge
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables MCP-compatible AI assistants to control Audacity 4 locally for audio editing, effects, VST3 plugins, and cleanup pipelines via a TCP JSON-RPC bridge, with no cloud or API keys.15625 PyPI4Apache 2.0
- AlicenseAqualityBmaintenanceEnables any MCP-compatible client to perform local voice cloning and text-to-speech using OmniVoice, including voice profile management, voice design, and an optional ASMR post-processing DSP pipeline.6AGPL 3.0
- AlicenseBqualityDmaintenanceMCP server for Synthesizer V AI Vocal Studio, which allows LLMs to create/edit vocal tracks e.g. adding lyrics to the melody.616Apache 2.0
- AlicenseCqualityBmaintenanceEnables AI assistants to control REAPER DAW via the Model Context Protocol, including track, FX, MIDI, and audio operations.4746 PyPI87MIT
- FlicenseNot gradedqualityBmaintenanceEnables MCP clients to control Neural DSP Quad Cortex devices, including preset recall, block parameter editing, and device diagnostics through conversational commands.-
TDQS
A3.9/5.0
Scored across 9 tools
Disambiguation4/5
Most tools target distinct actions (select, set pitch/index/bypass, start/pause, status). The only potential confusion is between list_local_models (disk files) and list_voice_models (imported engine slots), but the descriptions explicitly clarify the difference.
Naming Consistency5/5
Every tool follows a clean verb_noun snake_case pattern (list_*, select_voice_model, set_voice_*, start/pause_voice_audio, get_voice_status) with the 'voice' domain term applied consistently.
Tool Count5/5
Nine tools is well-scoped for an RVC voice-bridge controller, covering listing, model selection, parameter configuration, audio start/pause, and status without redundancy.
Completeness4/5
The core lifecycle (list → select → configure → start/pause → status) is covered. Minor gaps exist: there is no explicit resume-from-pause or model import operation, though the bypass+start workaround mitigates these.
Maintenance
ActivityMaintained
ResponsivenessNo issues