Skip to main content
Glama
deenesjakoruzh
Yuki10Kobayashi

VOICEVOX MCP Server

by Yuki10Kobayashi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

voicevox-mcp

该项目是一个MCP（模型上下文协议）服务器，与VOICEVOX引擎配合，合成语音并获取说话人信息。它是用 TypeScript 实现的，并使用 MCP SDK。

功能

  • 获取 VOICEVOX 引擎的扬声器信息 (/speakers)

  • 在指定的扬声器上将文本合成为语音并在本地播放（/speak）

    • 仅限 Mac

设置

启动 VOICEVOX 引擎（推荐使用 Docker）

docker compose up -d

这将在 localhost:50021 上启动 VOICEVOX 引擎。

Related MCP server: AivisSpeech MCP Server

安装并构建依赖项

npm install
npm run build

如何使用

光标设置示例

{
  "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" 
      }
    }
  }
}

根据需要设置VOICEVOX_API_URL。

  • 您可以使用发言者工具从 MCP 客户端获取发言者列表。

  • 语音工具可以将文本合成为语音并在本地播放（建议使用 Mac，因为它使用 afplay 命令）。

主要依赖项

  • @modelcontextprotocol/sdk

  • zod

  • typescript

防范措施

  • 未来的改进

    • 除非 VOICEVOX 引擎在 localhost:50021 上运行，否则语音合成将不可用。

    • 如果您使用Mac以外的环境，请相应地更改afplay部分。

执照

MIT 许可证

Available Tools

2 tools
speakD
ParametersJSON Schema
NameRequiredDescriptionDefault
textYes

TDQS

D1/5.0
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

speakersD
ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

D1/5.0
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Tool Schema Changelog

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

  1. 2 tool updatesv1.0.0
    • First observedspeak
    • First observedspeakers
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

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 issues

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches