Skip to main content
Glama
Voicevox MCP Server

Voicevox MCP Server

by Dosugamea

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

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 environment

  • Permission to access /mnt/wslg

Related MCP server: TTS-MCP

Installation and Configuration

  1. Clone the repository

git clone https://github.com/Dosugamea/voicevox-mcp-server.git
cd voicevox-mcp-server
  1. Installing dependencies

npm install
  1. Setting environment variables Create a .env file by copying .env_example and modifying the settings as needed:

VOICEVOX_API_URL=http://localhost:50021
VOICEVOX_SPEAKER_ID=1

How to do it

Execution in Windows environment

Please launch a server separately from the editor by following the steps below.

npm run build
npm start

Execution 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

Available Tools

1 tool
voicevoxC

VOICEVOXを使用して音声を合成し、ホストコンピュータで再生します

Inputs: text.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'voicevox' has a clear, distinct purpose for text-to-speech synthesis and playback.

    Naming Consistency5/5

    A single tool inherently exhibits perfect naming consistency, as there are no other tools to compare against. The tool name 'voicevox' is straightforward and matches the server's domain.

    Tool Count2/5

    A single tool is too few for a server's purpose, even for a focused domain like text-to-speech. This limits functionality, as agents cannot perform related operations like listing voices, adjusting parameters, or managing playback without additional tools.

    Completeness2/5

    The tool surface is severely incomplete for a text-to-speech domain. While the core synthesis and playback function is covered, there are obvious gaps such as fetching available voices, configuring speech parameters, pausing or stopping playback, or handling errors, which will likely cause agent failures.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A 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.
      30 npm
      1
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      A 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.
      1
      2
      MIT