audio-transcription-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MODEL | No | OpenAI Whisper model (default: whisper-1). | whisper-1 |
| CHANNELS | No | Number of audio channels (default: 1). | 1 |
| OUTFILE_DIR | No | Output directory for transcripts (default: current working directory). | |
| SAMPLE_RATE | No | Audio sample rate in Hz (default: 16000). | 16000 |
| CHUNK_SECONDS | No | Seconds of audio per chunk (default: 8). | 8 |
| OPENAI_API_KEY | Yes | Your OpenAI API key for Whisper transcription. | |
| INPUT_DEVICE_NAME | No | Audio input device name (default: BlackHole). | BlackHole |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_transcriptionA | Start capturing and transcribing system audio in real-time using OpenAI Whisper. Audio is captured in chunks and transcribed continuously. IMPORTANT: After starting, periodically check get_status (every 30-60 seconds) to monitor for issues. SAFETY FEATURES: The system will auto-pause in two scenarios: 1) After 32 seconds of silence, 2) After 30 minutes of NO user interaction (prevents forgotten recordings). User interaction = calling get_status, pause_transcription, resume_transcription, get_transcript, or clear_transcript. When paused, you'll see isPaused: true in status. User must explicitly call resume_transcription to continue. |
| pause_transcriptionA | Pause the current transcription session. Audio capture continues but transcription is paused. Use resume_transcription to continue. |
| resume_transcriptionA | Resume transcription after it has been paused (either manually or due to silence detection). |
| stop_transcriptionA | Stop the current transcription session completely and return statistics. This ends the session and stops audio capture. |
| get_statusA | Get the current status of the transcription session including whether it's running, number of chunks processed, errors, and session duration. CRITICAL: AI assistants should check this regularly (every 30-60 seconds) during active transcription to: 1) Catch audio routing issues or silence detection, 2) Monitor session duration and alert user if running 30+ minutes (prevents forgotten recordings and excessive API costs), 3) Detect paused states and warnings. The status.warning field will contain important alerts that should be shown to the user immediately. |
| get_transcriptA | Retrieve the current transcript content. Optionally get only the last N lines. |
| clear_transcriptA | Clear the transcript file and reinitialize it with a fresh header. |
| cleanup_transcriptA | Delete the transcript file completely. Use this to remove the transcript file when you're done. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Current Transcript | The current audio transcription in real-time. IMPORTANT: If transcription is paused, a warning banner will appear at the top. Check this resource periodically to monitor transcription health and catch issues early. |
TDQS
Scored across 8 tools
Each tool targets a distinct action in the transcription lifecycle: start, pause, resume, stop, status check, transcript retrieval, clearing, and deleting. No two tools overlap in purpose, even pause vs. stop and clear vs. cleanup are clearly differentiated by their descriptions.
All tool names follow a consistent verb_noun pattern using snake_case: start_transcription, pause_transcription, get_status, etc. The naming is uniform and predictable, making it easy to infer the function of each tool.
With 8 tools, the set is well-scoped for an audio transcription server. Each tool covers a necessary part of the session lifecycle without redundancy or bloat, fitting comfortably within the ideal range.
The tool set provides full lifecycle coverage: start, manage (pause/resume), monitor (status), retrieve output, and clean up (clear/delete). There are no obvious dead ends or missing operations for the stated purpose.