{
  "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クライアントから speakers ツールでスピーカー一覧を取得できます。
speak ツールでテキストを音声合成し、ローカルで再生できます（afplayコマンドを使用しているため、Mac環境推奨）。

主な依存パッケージ

@modelcontextprotocol/sdk
zod
typescript

注意事項

今後改善
- VOICEVOXエンジンが localhost:50021 で動作していないと音声合成は利用できません。
- Mac以外の環境では afplay の部分を適宜変更してください。

ライセンス

MIT License

Available Tools

2 tools

speakD

ParametersJSON Schema

Name	Required	Description	Default
`text`	Yes

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

Name	Required	Description	Default
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.

2 tool updatesv1.0.0Aug 15, 2025
- 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 2026-04-18 10:05 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

Need Help?

Reddit Discussion

Related Servers

Related MCP Connectors

hithereiamaliff-mcp-nextcloudOAuth
ai.smithery
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Cloud Storage File Systems Workplace & Productivity
238
Texttospeech Mcp C
io.github.varvararatta
MCP server for Text-to-Speech
Text-to-Speech Speech Processing Audio Processing
2
mcp-fishOAuth
io.github.AceDataCloud
MCP server exposing the AceDataCloud Fish Audio API (text-to-speech with voice conditioning)
Text-to-Speech Speech Processing
21
EasyVoice text to speech
ae.easyvoice
Hosted text-to-speech MCP server: 66 voices in 9 languages, long-form narration, podcasts.
Text-to-Speech Audio Processing Speech Processing
71

Related MCP Servers

Speech MCP Server
Text-to-Speech Audio Processing Multimedia Processing
hammeiam
A
license
B
quality
D
maintenance
A Model Context Protocol server that provides text-to-speech capabilities using the Kokoro TTS model, offering multiple voice options and customizable speech parameters.
Updated 2 years ago (2025-03-28 21:29 UTC)
4
21 npm
2
MIT
AivisSpeech MCP Server
Speech Processing Autonomous Agents
kentaro
F
license
D
quality
D
maintenance
A Model Context Protocol server that enables AI assistants to utilize AivisSpeech Engine's high-quality voice synthesis capabilities through a standardized API interface.
Updated 2 years ago (2025-03-15 17:05 UTC)
1
1
-
Voicevox MCP Server
Speech Processing Autonomous Agents
Dosugamea
A
license
B
quality
F
maintenance
A server that enables Claude 3.7 and other AI agents to access VOICEVOX-compatible speech synthesis engines (AivisSpeech, VOICEVOX, COEIROINK) through the Model Context Protocol.
Updated 2 years ago (2025-03-23 19:53 UTC)
1
12
MIT
Edge-TTS MCP Server
Text-to-Speech Speech Processing
yuiseki
A
license
B
quality
D
maintenance
A Model Context Protocol server that provides text-to-speech functionality for AI agents using Microsoft Edge's text-to-speech technology, supporting multiple voices, languages, and voice customization.
Updated a year ago (2025-04-22 00:05 UTC)
2
8
MIT

Appeared in Searches

A guide to creating voiceovers

voicevox-mcp

機能

セットアップ

VOICEVOXエンジンの起動（Docker推奨）

依存パッケージのインストール & ビルド

使い方

Cursorの設定例

注意事項

ライセンス

Available Tools

TDQS

TDQS

Tool Schema Changelog

TDQS

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Speech MCP Server

AivisSpeech MCP Server

Voicevox MCP Server

Edge-TTS MCP Server

Appeared in Searches