Skip to main content
Glama

voicevox-mcp

This project is an MCP (Model Context Protocol) server that can synthesize speech and obtain speaker information in cooperation with the VOICEVOX engine. It is implemented in TypeScript and uses the MCP SDK.

function

  • Get speaker information for the VOICEVOX engine (/speakers)

  • Synthesize text to speech on a specified speaker and play it locally (/speak)

    • Mac only

set up

docker compose up -d

This will start the VOICEVOX engine on localhost:50021.

Related MCP server: AivisSpeech MCP Server

Install and build dependencies

npm install
npm run build 

How to use

Cursor setting example

{
  "mcpServers": {
    "voicevox-mcp": {
      "command": "node",
      "args": ["${Path to Repository}/dist/index.js"],
      "env": {
        "SPEAKER_ID": 8,
        "SPEED_SCALE": 1.2,
        "VOICEVOX_API_URL": "http://localhost:50021" 
      }
    }
  }
}

Set VOICEVOX_API_URL as needed.

  • You can get a list of speakers from your MCP client using the speakers tool.

  • The speak tool can synthesize text to speech and play it back locally (Mac is recommended as it uses the afplay command).

Main Dependencies

  • @modelcontextprotocol/sdk

  • zod

  • typescript

Precautions

  • Future improvements

    • Speech synthesis will not be available unless the VOICEVOX engine is running on localhost:50021.

    • If you are using an environment other than Mac, please change the afplay part accordingly.

license

MIT License

Available Tools

2 tools
speakD

Inputs: text (required).

speakersD

Inputs: no named parameters.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    D1.8/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: 'speak' implies text-to-speech synthesis, while 'speakers' likely lists available voice options. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    Both tools use simple, consistent naming: 'speak' and 'speakers' are both lowercase nouns, with 'speak' as a verb-like noun and 'speakers' as a plural noun. The pattern is uniform and predictable.

    Tool Count2/5

    With only two tools, the server feels thin for a VOICEVOX text-to-speech domain. Expected operations like adjusting voice parameters, controlling playback, or managing audio output are missing, making the set under-scoped.

    Completeness2/5

    The tool surface is severely incomplete for a VOICEVOX server. Core functionalities such as voice customization, audio format settings, playback control, or synthesis status checks are absent, leaving significant gaps that will hinder agent workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    Appeared in Searches