FlowSpeech MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FLOWSPEECH_OUTPUT_DIR | No | Directory to save generated audio files | ~/.flowspeech-mcp/audio |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| flowspeech_ttsA | Convert text to speech using FlowSpeech — a context-aware TTS engine with emotion control and 30+ voices. Returns the file path of the generated audio. |
| flowspeech_tts_multiA | Convert a two-speaker dialogue to speech using FlowSpeech. Assign Speaker1: and Speaker2: prefixes in the text. |
| flowspeech_list_voicesA | List all available FlowSpeech voices with their descriptions and gender. |
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 3 tools
Each tool has a clearly distinct purpose: listing voices, single-speaker TTS, and two-speaker TTS. No overlap or ambiguity.
All tool names follow a consistent flowspeech_verb_noun pattern using snake_case, with clear and predictable naming.
Three tools is slightly minimal but appropriate for a focused TTS server. The set covers the core functionality without feeling overly sparse.
The tool surface covers the essential operations: voice discovery, single-speaker TTS, and dialogue TTS. Minor gaps exist (e.g., no explicit voice selection or emotion control parameters documented), but the core workflow is complete.