Skip to main content
Glama
enesjakozh
Dosugamea

Voicevox MCP Server

by Dosugamea
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

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を使用して音声を合成し、ホストコンピュータで再生します

ParametersJSON Schema
NameRequiredDescriptionDefault
textNo合成する文章

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It mentions synthesis and playback but lacks details on behavioral traits like error handling, performance characteristics (e.g., latency), or system requirements (e.g., VOICEVOX installation). This leaves significant gaps for an AI agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's function. It is appropriately sized and front-loaded, with no unnecessary words, though it could be slightly more structured (e.g., separating synthesis and playback aspects).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It covers the basic purpose but omits critical context such as what the tool returns (e.g., success/failure, audio data), error conditions, or usage limitations, which are essential for a synthesis/playback tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description does not mention the 'text' parameter at all. However, schema description coverage is 100%, with the parameter documented as '合成する文章' (text to synthesize). Since the schema fully covers the parameter, the baseline score of 3 is appropriate, as the description adds no additional semantic value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'VOICEVOXを使用して音声を合成し、ホストコンピュータで再生します' (Uses VOICEVOX to synthesize speech and play it on the host computer). It specifies the action (synthesize and play speech) and resource (VOICEVOX), but since there are no sibling tools, it doesn't need to distinguish from alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives or any contextual prerequisites. It simply states what the tool does without indicating appropriate scenarios or constraints.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.1/5.0
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
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • TTS-MCP

    nakamurau1
    A
    license
    Not graded
    quality
    C
    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.
    17
    1
    MIT

  • Bouyomi-chan MCP Server

    uraoz
    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

Appeared in Searches

Latest Blog Posts

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