Whisper 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
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 |
|---|---|
| transcribe_audioA | Transcribe an audio file using Whisper. Supports various audio formats (wav, mp3, m4a, etc.). Returns the transcribed text. |
| list_whisper_modelsA | List available Whisper models and their download status. Shows which models are downloaded locally. |
| download_whisper_modelA | Download a Whisper model for local transcription. Models are stored in ~/.whisper/ |
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 distinct purpose: downloading models, listing models, and transcribing audio. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern in snake_case (download_whisper_model, list_whisper_models, transcribe_audio).
With 3 tools, the server is well-scoped for its purpose—managing models and transcribing audio. The count is appropriate and avoids being too thin or heavy.
The tool set covers the core workflow (model download, listing, transcription) but lacks model deletion or advanced configuration. Still, it is sufficient for basic tasks.