Voicevox MCP Server
Enables running the VOICEVOX MCP server in a containerized environment, with specific configurations for audio output in WSL2.
Used for configuring environment variables like VOICEVOX API URL and speaker ID settings.
Used for cloning the repository during installation.
Platform for reporting bugs, requesting features, and contributing to the project through Issues and Pull Requests.
Supported platform for running the server in WSL2 with specific audio dependencies.
Required runtime environment for the VOICEVOX MCP server, version 18 or higher.
Package manager used for installing dependencies and running the server.
Click on "Install 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., "@Voicevox MCP Serversynthesize 'Hello, welcome to our meeting' with speaker ID 3"
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.
Voicevox MCP Server
This is a server for using VOICEVOX compatible speech synthesis servers (AivisSpeech / VOICEVOX / COEIROINK) via MCP (Model Context Protocol). It can be used for speech synthesis in agent mode using Claude 3.7 in Cursor, etc.
Prerequisites
Windows environment
Node.js 18 or higher
VOICEVOX ENGINE etc. ( run locally at http://localhost:50000 etc. )
VLC media player (path must be set)
Docker environment (WSL2)
Docker and Docker Compose
WSL2
VOICEVOX ENGINE etc. (run locally or in Docker)
sudo apt install libsdl2-dev pulseaudio-utils pulseaudio-enabled Linux environmentPermission to access
/mnt/wslg
Related MCP server: TTS-MCP
Installation and Configuration
Clone the repository
git clone https://github.com/Dosugamea/voicevox-mcp-server.git
cd voicevox-mcp-serverInstalling dependencies
npm installSetting environment variables Create a
.envfile by copying.env_exampleand modifying the settings as needed:
VOICEVOX_API_URL=http://localhost:50021
VOICEVOX_SPEAKER_ID=1How to do it
Execution in Windows environment
Please launch a server separately from the editor by following the steps below.
npm run build
npm startExecution in Docker environment
No need to use an editor or any other operations. It starts in stdio mode so it cannot be executed directly.
How to set it up
When running in a Windows environment
Please add the following to mcp.json. The connection is unstable, so please reconnect if it is disconnected.
"voicevox": {
"url": "http://localhost:10100/sse"
}When running in a Docker environment
Please add the following to mcp.json. (The author's environment has not been tested.)
{
"tools": {
"voicevox": {
"command": "cmd",
"args": [
"/c",
"docker",
"run",
"-i",
"--rm",
"-v",
"/mnt/wslg:/mnt/wslg",
"-e",
"PULSE_SERVER",
"-e",
"SDL_AUDIODRIVER",
"-e",
"VOICEVOX_API_URL",
"-e",
"VOICEVOX_SPEAKER_ID",
"your-local-docker-image-name"
],
"env": {
"PULSE_SERVER": "unix:/mnt/wslg/PulseServer",
"SDL_AUDIODRIVER": "pulseaudio",
"VOICEVOX_API_URL": "http://host.docker.internal:50031",
"VOICEVOX_SPEAKER_ID": "919692871"
}
}
}
}About Speaker ID
The speaker ID varies depending on the model of VOICEVOX you are using. By default, "1" (Shikoku Metan) is used. If you want to use another speaker ID, change the environment variable VOICEVOX_SPEAKER_ID .
You can check the list of speaker IDs at the /speakers endpoint of the VOICEVOX ENGINE API. Example: curl http://localhost:50021/speakers
troubleshooting
Connection error with VOICEVOX : Please make sure that VOICEVOX ENGINE is running and that the API URL is set correctly.
No sound playing : Make sure VLC is properly installed and in your path.
Audio output problem in Docker environment : Please check that pulseaudio is configured correctly.
Developer Information
To contribute to the source code, please create an issue or submit a pull request.
To report bugs or request features, please use the Issues feature on GitHub.
license
MIT License
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Tools
Related MCP Servers
- FlicenseDqualityCmaintenanceA Model Context Protocol server that enables AI assistants to utilize AivisSpeech Engine's high-quality voice synthesis capabilities through a standardized API interface.11
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol server that integrates high-quality text-to-speech capabilities with Claude Desktop and other MCP-compatible clients, supporting multiple voice options and audio formats.171MIT
- AlicenseBqualityDmaintenanceA Node.js server that enables AI assistants to interact with Bouyomi-chan's text-to-speech functionality through Model Context Protocol (MCP), allowing for voice reading of text with adjustable parameters.12MIT
- AlicenseDqualityDmaintenanceA Model Context Protocol server that integrates with VOICEVOX engine to provide text-to-speech synthesis and speaker information retrieval, allowing users to generate and play voice audio from text.2143MIT
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
MCP server exposing the AceDataCloud Fish Audio API (text-to-speech with voice conditioning)
MCP server for AI dialogue using various LLM models via AceDataCloud
Appeared in Searches
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Dosugamea/voicevox-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server