faster-whisper-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_API_KEY | No | OpenAI API key, required only when using the translation function. |
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 |
|---|---|
| get_supported_languagesB | サポートされている言語の一覧を取得します。 翻訳可能な言語コードと言語名のリストを返します。 |
| transcribe_from_fileA | ローカルの動画/音声ファイルから字幕を生成します。 |
| transcribe_from_urlA | URLから動画をダウンロードして字幕を生成します。 |
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
The three tools have clearly distinct purposes: get_supported_languages retrieves language metadata, transcribe_from_file processes local files, and transcribe_from_url handles remote content. There is no overlap in functionality, and each tool's name and description make its specific role unambiguous.
All tool names follow a consistent verb_noun pattern with snake_case: get_supported_languages, transcribe_from_file, and transcribe_from_url. The naming is predictable and uniform throughout the set, making it easy to understand the action and target.
Three tools are reasonable for a transcription server, covering language support and transcription from both local and remote sources. However, the count feels slightly thin as it lacks utilities like managing transcriptions or adjusting parameters post-transcription, though the core functionality is well-represented.
The server provides essential operations for transcription: language lookup and transcription from file/URL, covering the main workflows. A minor gap exists in not offering tools to edit or delete generated transcripts, but agents can work around this by handling files externally.