Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
VOICEVOX_URLNoVOICEVOX Engine URLhttp://localhost:50021
MCP_HTTP_HOSTNoHTTP host0.0.0.0
MCP_HTTP_MODENoEnable HTTP modefalse
MCP_HTTP_PORTNoHTTP port3000
MCP_ALLOWED_HOSTSNoAllowed hosts (comma-separated)localhost,127.0.0.1,[::1]
MCP_ALLOWED_ORIGINSNoAllowed origins (comma-separated)http://localhost,http://127.0.0.1
VOICEVOX_USE_STREAMINGNoStreaming playback (requires ffplay)false
VOICEVOX_DISABLED_TOOLSNoComma-separated list of tools to disable (e.g., generate_query,synthesize_file)
VOICEVOX_DEFAULT_SPEAKERNoDefault speaker ID1
VOICEVOX_DEFAULT_IMMEDIATENoImmediate playback default settingtrue
VOICEVOX_RESTRICT_IMMEDIATENoRestrict AI from specifying the immediate option
VOICEVOX_DEFAULT_SPEED_SCALENoDefault playback speed1.0
VOICEVOX_DEFAULT_WAIT_FOR_ENDNoWait for playback end default settingfalse
VOICEVOX_RESTRICT_WAIT_FOR_ENDNoRestrict AI from specifying the waitForEnd option
VOICEVOX_DEFAULT_WAIT_FOR_STARTNoWait for playback start default settingfalse
VOICEVOX_RESTRICT_WAIT_FOR_STARTNoRestrict AI from specifying the waitForStart option

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
ping_voicevoxB

Check if VOICEVOX Engine is running and reachable

speakA

Convert text to speech and play it. Text is split by line breaks (\n) into separate speech units. Each line is processed as an independent audio segment.

generate_queryC

Generate a query for voice synthesis

synthesize_fileC

Generate an audio file and return its absolute path

stop_speakerA

Stop current audio playback

get_speakersC

Get a list of available speakers

get_speaker_detailC

Get detail of a speaker by id

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 7 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: generate_query creates synthesis queries, get_speaker_detail and get_speakers handle speaker metadata, ping_voicevox checks engine status, speak plays audio, stop_speaker stops playback, and synthesize_file creates files. The descriptions make it easy to distinguish between query generation, metadata retrieval, status checking, real-time playback control, and file synthesis.

Naming Consistency4/5

The naming is mostly consistent with a verb_noun pattern (e.g., get_speakers, stop_speaker, synthesize_file), but there are minor deviations: generate_query uses 'generate' instead of a more specific verb like 'create', and ping_voicevox uses 'ping' as a verb which is less conventional but still understandable. All tools use snake_case consistently.

Tool Count5/5

With 7 tools, this server is well-scoped for a TTS system. It covers essential operations like checking engine status, retrieving speaker information, generating queries, real-time speech playback with control, and file synthesis. Each tool earns its place without feeling excessive or insufficient for the domain.

Completeness5/5

The tool set provides complete coverage for a TTS domain: it includes status checking (ping_voicevox), metadata retrieval (get_speakers, get_speaker_detail), query preparation (generate_query), real-time audio handling (speak, stop_speaker), and file output (synthesize_file). There are no obvious gaps—agents can perform the full lifecycle from setup to synthesis and playback control.

Maintenance

ActivityMaintained
ResponsivenessNo issues