SpeechLab MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CARTESIA_API_KEY | No | Cartesia API key for cloud TTS. Leave empty unless Cartesia cloud voices are needed. | |
| CARTESIA_VOICE_ID | No | Cartesia voice ID for cloud TTS. | |
| SPEECH_LAB_PIPER_URL | No | URL of the local Piper TTS server. | |
| SPEECH_LAB_OUTPUT_DIR | No | Directory where synthesized WAV files are written. | |
| SPEECH_LAB_POCKET_URL | No | URL of the local Pocket TTS server. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
SpeechLab synthesizes speech to WAV files on disk and returns absolute paths. Use list_providers / provider_status to see what is healthy, list_voices for voice ids, then synthesize(text, provider?, voice?). Copy the WAV into your game or video project as needed. Woof audio should credit 'Voice by Underdog Woof'.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_providersA | List configured TTS providers and whether each is currently healthy. |
| provider_statusB | Health-check one provider, or all configured providers when omitted. |
| list_voicesA | List voices for one provider, or all configured providers when omitted. |
| synthesizeA | Synthesize speech to a WAV file and return its absolute path plus metadata. Args: text: Spoken line to generate. provider: piper | pocket | woof | cartesia (default from env / first healthy local). voice: Provider-specific voice id or name (Pocket also accepts an audio prompt URL). filename_hint: Optional short label included in the output filename. |
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 4 tools
list_providers and provider_status overlap substantially since list_providers already reports health, making the dedicated health-check largely redundant and easy to misselect. list_voices and synthesize are clearly distinct, so the overlap is confined to two tools.
Three tools use verb_noun (list_providers, list_voices) or bare verb (synthesize), while provider_status uses a noun_noun form, breaking the pattern. Mixed conventions but still readable.
Four tools is on the lean side but appropriate for a focused TTS server: provider discovery, health, voices, and synthesis. The only inefficiency is the split between list_providers and provider_status, which could be consolidated.
The core TTS lifecycle (discover providers, list voices, synthesize to WAV) is well covered. Minor gaps exist around listing/managing generated audio files or configuring providers, but agents can work around these.