Dot RVC Bridge
The MCP server lets a compatible local MCP host inspect and control the local RVC voice bridge after devices are configured.
Check engine, model, audio configuration, and blocking reasons without starting recording or proving live call audio.
List local
.pthand candidate.indexpaths without deserializing or importing them.List imported RVC model slots and select an imported model slot while audio is paused.
Set pitch offset from −24 to +24 semitones and set retrieval index ratio subject to index-file limits; the README notes the protected MCP service keeps index ratio at zero.
Toggle original-voice bypass without changing Windows audio routing.
Start or pause voice audio when model and routing are configured; start only confirms configuration, and pause silences Dot audio still routed to the virtual cable.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Dot RVC Bridge what RVC voice models do I have installed?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Dot RVC Bridge
Give Dot a different voice with your own RVC model, locally on Windows.
English · 简体中文 · Download Windows Easy Edition
A desktop controller, installer, and optional MCP server for routing Dot's playback through a local RVC engine. Includes model import, playback selection, pitch control, original-voice bypass, and start/pause.
This independent community project converts audio played on your PC; it is not an official OpenAI plugin or a native Dot voice API. The supported installation path targets Windows x64 with an NVIDIA GPU; compatibility across GPU generations is not established.
Warning: existing virtual audio setups
Use with caution if you already use virtual audio cables, Voicemeeter, VAC, Sonar, other voice changers, or recording/streaming software with audio routing. Sharing the same cable, conflicting device access, or changing audio routes can cause mixed audio, silence, double playback, or feedback. Compatibility with your existing setup is not guaranteed. Do not make your first test during a live stream, meeting, or recording.
Before installing or starting:
Save/export your existing audio-software configuration and record Windows' default playback/recording devices, default communications devices, and per-app routes.
This release specifically uses CABLE Input / CABLE Output (VB-Audio Virtual Cable). CABLE-A/B, Voicemeeter virtual devices, and other virtual cables are not interchangeable inputs in the current launcher. If another workflow already needs this cable, stop that workflow for the test; if both must run together, postpone using this release.
Setup skips driver installation when it detects the expected CABLE Output device. Detection does not mean the cable is unused. If you already have VB-CABLE but setup still proposes installing it, cancel the driver installer and check the installed device/driver first. Do not uninstall or reinstall a working shared driver just to try this app.
Start with headphones at low volume. Route only the app hosting Dot to CABLE Input, and keep RVC playback on physical headphones/speakers. Never feed RVC output back into the same cable or Dot's microphone. VB-CABLE forwards audio sent to its input to its output, so other apps using that input will also enter this route. VB-CABLE documentation.
If sound stops, echoes, or another app is affected:
Stop the RVC engine. In Windows Settings → System → Sound → Volume mixer, restore the Dot app's output to its previous device; use physical headphones/speakers temporarily to check normal playback. Check the app is unmuted. Microsoft's app-audio troubleshooting.
Restore your saved default devices, communications devices, and mixer/streaming-software routes. Restore Dot's usual microphone. Stop only the duplicate monitoring path introduced for this test, including Windows “Listen to this device” if you enabled it.
If a device is busy or unavailable, close the apps using it and reopen them after selecting the intended devices. After a VB-CABLE driver installation, reboot as the vendor instructs, then recheck defaults and device selections. VB-CABLE installation instructions.
Confirm your original audio workflow works before trying again. Avoid a global audio reset or driver removal as the first fix: other apps may rely on those settings or drivers. Closing this app does not automatically restore Windows routing or your other software's configuration.
Related MCP server: reaper-reapy-mcp
Quick start
Download dot-rvc-bridge-0.3.2-windows-easy.zip from Releases. Extract to a permanent, writable folder. Choose this asset, not GitHub's automatic “Source code” ZIP.
Double-click Setup.cmd. It installs private Python environments, CUDA-enabled PyTorch, the pinned engine, and base inference assets. The first install needs internet access, several GB of downloads, and about 15 GB of free disk space. No manual Python, Node.js, or C++ compiler installation is needed.
If VB-CABLE is missing, setup opens its signed installer. Accept the Windows administrator prompt for BUREL VINCENT, click Install Driver, and restart if requested. Keep your usual microphone and speakers as Windows defaults.
Double-click Start.cmd. Click Import .pth, select your model, choose playback headphones/speakers, then click Start.
In Windows Settings → System → Sound → Volume mixer, set the app hosting Dot to output to CABLE Input (VB-Audio Virtual Cable). Keep Dot's microphone set to your normal microphone. Start a conversation and listen.
If the app is absent from the mixer, play audio in it first. App-level routing can include its other sounds. The launcher does not change Windows defaults or per-app routing.
Dot app → CABLE Input → CABLE Output → RVC → headphones / speakers
Your microphone ─────────────────────────→ DotRestore normal sound: enable Original voice while the engine runs, or change the app's Windows output back to your headphones/speakers. Pausing or closing the engine silences audio still routed to the cable.
Support and limits
v0.3.2 supports | Details |
RVC inference checkpoints | Standard v2, f0=1, 18-item configuration, 32/40/48 kHz |
Pitch extraction | RMVPE; NVIDIA GPU 0 |
Pitch control | −24 to +24 semitones |
Audio | Windows WASAPI; 48 kHz cable/output route |
Model selection | One active profile; import another model to switch |
Find and download your own RVC character .pth on Hugging Face. This project does not choose, host, bundle, or automatically download character weights. No local character weights, indexes, converted model bundles, recordings, or personal settings are included. Models undergo structural and size checks; not every checkpoint is compatible. Raw bundles are limited to 100 MB. RVC v1, no-f0 models, training checkpoints, .index retrieval, CPU-only use, and other operating systems are outside this release's supported path. The desktop uses speaker 0 for multi-speaker models.
RVC changes timbre; source rhythm, expression, and pronunciation still matter. Use models and demo audio you have permission to use and share.
The easy ZIP
Includes the bilingual controller, public source, README.md, README_CN.md, agent.md / AGENTS.md, official uv 0.13.2, prebuilt fairseq 0.12.2 and ANTLR wheels, manifests, and license notices. Local development profiles and personal data are excluded. This is an online installer. Engine source, PyTorch, base assets, and VB-CABLE are downloaded during setup.
Runtime files stay in .venv/ and runtime/. Moving the folder after installation can break environment paths; install again in a new folder instead. There is no automatic updater.
Troubleshooting
Symptom | Check |
Download failed | Retry Setup.cmd with access to GitHub, PyPI, PyTorch, and Hugging Face. Hash mismatches stop installation. |
No CABLE devices | Complete driver installation, restart if requested, and relaunch. |
Port 18888 occupied | Stop the other RVC instance first; the launcher will not terminate an unrelated process. |
No voice after Start | Check app output, CABLE installation, playback selection, and |
Device changed/unplugged | Pause, stop the engine, refresh devices, choose the output, and start again. |
Import rejected | Use a standard RVC v2 inference .pth with pitch guidance; see |
Double playback | Disable Windows “Listen to this device” on the cable and check other monitoring paths. |
The default buffer is 64 × 128 samples at 48 kHz: about 171 ms of input buffering, not measured total latency. See validation scope.
Optional MCP controls
Setup writes a machine-local mcp.json. Use its stdio entry with a compatible local MCP host after the desktop loads the engine. A cloud host's localhost is not your PC; direct Dot-to-MCP control has not been verified for this release.
Tools: get_voice_status, list_local_models, list_voice_models, select_voice_model, set_voice_pitch, set_voice_index_ratio, start_voice_audio, pause_voice_audio, and set_voice_bypass. Configure devices through the desktop or CLI first. The protected service has one active slot and keeps index ratio at zero.
Installing with an agent
Ask your agent to read AGENTS.md (also linked from agent.md). It covers installation, existing virtual-audio setups, verification and recovery. The agent can help you import your own weights, find candidates on Hugging Face when requested, or explain how to train an inference model using the official RVC project in a separate environment. Missing character weights do not prevent software-only setup; no character weights are bundled or selected automatically by the installer.
Development
uv run --no-project --python 3.13.5 scripts/bootstrap.py
.venv\Scripts\python.exe -m unittest discover -s tests -v
.venv\Scripts\python.exe scripts/package-source.pySource installation fetches pinned wheels from this repository's release. Desktop, CLI, and MCP share Engine; adapters implement read_state() and write_setting(). Model import and the legacy CUDA engine use separate environments joined by a validated raw tensor format.
See architecture, extensions, model handling, and release builds.
Original bridge code is MIT licensed. Third-party components, model assets, and VB-CABLE retain their own terms. Thanks to w-okada/voice-changer, RVC, and the underlying model and library authors.
Available Tools
9 toolsget_voice_statusARead-only
检查本机 RVC 引擎、模型、音频配置及阻塞原因;不启动录音,不证明实际通话音频已接通。
Inputs: no named parameters. Returns: object
list_local_modelsARead-only
列出配置目录里的 .pth 和候选 .index 路径;不反序列化权重,不自动导入或判断兼容性。
Inputs: no named parameters. Returns: object
list_voice_modelsARead-only
列出已导入兼容引擎的 RVC 模型槽位。请用返回的槽位选择角色。
Inputs: no named parameters. Returns: object
pause_voice_audioAIdempotent
请求暂停引擎音频,会使仍路由到虚拟线的 Dot 无声。恢复原声请使用旁路并启动,或手动改回耳机输出。
Inputs: no named parameters. Returns: object
select_voice_modelAIdempotent
在引擎音频暂停时选择已导入的 RVC 模型;回读选择状态,不启动音频或保证预热成功。
Inputs: slot (required). Returns: object
set_voice_bypassAIdempotent
开启原声旁路或关闭旁路使用 RVC;保留引擎启停状态,不改变 Windows 音频路由。
Inputs: enabled (required). Returns: object
set_voice_index_ratioAIdempotent
将当前角色检索比例设为 0–1;没有索引文件时只允许 0。
Inputs: ratio (required). Returns: object
set_voice_pitchAIdempotent
将当前 RVC 角色的音高偏移设置为 -24 至 24 个半音;是绝对设置,不是累加。
Inputs: semitones (required). Returns: object
start_voice_audioAIdempotent
请求引擎读取已配置的 CABLE Output 并播放到已配置输出。需要模型及完整路由配置;结果仅确认配置。
Inputs: no named parameters. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
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.
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.
Nine tools is well-scoped for an RVC voice-bridge controller, covering listing, model selection, parameter configuration, audio start/pause, and status without redundancy.
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
Related MCP Connectors
Remote MCP server for audio stem separation, denoise, reverb, and MIDI export.
MCP server for Producer/Riffusion AI music generation
MCP server exposing the AceDataCloud Fish Audio API (text-to-speech with voice conditioning)
AI voice generation: text-to-speech and voice cloning from any MCP client.
Related MCP Servers
- 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
- AlicenseCqualityCmaintenanceEnables AI assistants to control REAPER DAW via the Model Context Protocol, including track, FX, MIDI, and audio operations.4788MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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
- FlicenseNot gradedqualityBmaintenanceEnables MCP clients to control Neural DSP Quad Cortex devices, including preset recall, block parameter editing, and device diagnostics through conversational commands.-