mcp-voice-hooks
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_VOICE_HOOKS_PORT | No | The port for the voice hooks server | 5111 |
| MCP_VOICE_HOOKS_AUTO_OPEN_BROWSER | No | Whether to automatically open the browser if no frontend connects within 3 seconds | true |
| MCP_VOICE_HOOKS_AUTO_DELIVER_VOICE_INPUT | No | Whether to automatically deliver voice input to Claude after tool use, before speaking, and before stopping | true |
| MCP_VOICE_HOOKS_AUTO_DELIVER_VOICE_INPUT_BEFORE_TOOLS | No | Whether to automatically deliver voice input before tool execution | false |
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 |
|---|---|
| speakC | Speak text using text-to-speech and mark delivered utterances as responded |
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, as there are no other tools to compare it to. The tool's purpose is clearly defined and stands alone without confusion.
A single tool inherently has perfect naming consistency, as there are no other tool names to compare it against for patterns or conventions. The name 'speak' is straightforward and appropriate for its function.
A single tool is too few for most server purposes, as it limits functionality and flexibility. While it might suffice for a very narrow scope, it feels thin and incomplete for broader use cases, indicating a potential mismatch.
The server's domain appears to be voice or text-to-speech interactions, but with only a 'speak' tool, there are significant gaps. Missing operations like controlling speech parameters, managing utterances, or handling input make the surface severely incomplete for typical voice-related workflows.