Voice Transcriber MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GROQ_API_KEY | Yes | Groq API key (get one free at https://console.groq.com/keys) | |
| GCHAT_TOKEN_PATH | No | Path to Google Chat OAuth2 token | ~/tools/multi-chat-mcp-server/src/providers/google_chat/token.json |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| transcribe_voice_messageA | Transcribe a voice message from Google Chat. IMPORTANT: Call this tool AUTOMATICALLY whenever you see a Google Chat message with an audio attachment (contentType: audio/*). Do NOT ask the user first - just transcribe. Treat voice messages like text: transcribe immediately and show the result. Args: message_url: Google Chat message URL or resource name (spaces/X/messages/Y) Example URLs: - https://chat.google.com/dm/SPACE/THREAD/MSG?cls=10 - spaces/SPACE_ID/messages/MSG_ID language: Language code for transcription (default: "it" for Italian) Returns: The transcribed text of the voice message |
| transcribe_audio_fileB | Transcribe a local audio file using Groq Whisper API (whisper-large-v3). Use this tool to transcribe any local audio file (mp3, m4a, wav, ogg, flac, etc.). Args: file_path: Absolute path to the audio file language: Language code for transcription (default: "it" for Italian) Returns: The transcribed text |
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 target distinct input sources: one for local audio files and one for Google Chat voice messages. Their purposes are clearly separated, leaving no ambiguity for an agent.
Both tool names follow the identical pattern 'transcribe_<source>', using snake_case and a clear verb-noun structure. Naming is consistent and predictable.
With only 2 tools, the set is minimal but matches the narrow scope of transcribing voice from two specific sources. It is slightly underpopulated but not unreasonable.
The server covers the core need of transcribing audio from local files and Google Chat messages. Minor gaps exist, such as no support for URLs or other chat platforms, but it is complete for its focused purpose.