Voicevox MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| voicevoxC | VOICEVOXを使用して音声を合成し、ホストコンピュータで再生します |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
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.
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.
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.
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.