Edge-TTS 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 |
|---|---|
| list_voicesC | Get a list of available voices |
| text_to_speechC | Convert text to speech |
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 2 tools
The two tools have completely distinct purposes: one lists available voices, the other converts text to speech. There is no overlap or ambiguity between them, making it easy for an agent to select the correct tool for each task.
Both tools follow a consistent verb_noun naming pattern (list_voices, text_to_speech). The naming is clear, predictable, and adheres to a uniform style throughout the tool set.
With only 2 tools, the server feels thin for a text-to-speech domain. While the tools cover core functionality, typical TTS systems might include additional operations like voice configuration, audio format settings, or batch processing, suggesting the scope is under-served.
The tools cover basic TTS operations (listing voices and converting text), but there are notable gaps. For example, there is no tool for configuring voice parameters (e.g., pitch, rate) or managing audio output formats, which could limit agent capabilities in more complex scenarios.