saidwire-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SAIDWIRE_API_KEY | Yes | Your Saidwire API key from saidwire.com/dev. Required. | |
| SAIDWIRE_API_URL | No | Saidwire API base URL. | https://api.saidwire.com |
| SAIDWIRE_MAX_DOWNLOAD_MB | No | Size limit in MB for transcribe_url downloads (max 100). | 100 |
| SAIDWIRE_ALLOW_PRIVATE_URLS | No | Set to 1 to let transcribe_url fetch from local or private network addresses. | off |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| transcribe_fileA | Transcribe a local audio file (WAV, MP3, FLAC, Ogg/Opus, WebM, M4A/MP4, AAC) to text. Args: path: Absolute path to the audio file on this computer (up to 100 MB / 60 minutes). format: "text" (plain transcript), "json" (transcript, utterances and word timestamps), "srt" or "vtt" (subtitles with timestamps). include_words: Add per-word start/end times (for "text" and "json"). output_path: Optional absolute path to also save the result to, e.g. /path/talk.srt. |
| transcribe_urlA | Download a public audio file from an http(s) URL and transcribe it to text. The file is downloaded by this server (default limit 100 MB, set SAIDWIRE_MAX_DOWNLOAD_MB to change it) and sent to Saidwire. Use a direct link to the audio, not a web page. Args: url: Direct http(s) link to an audio file. format: "text", "json" (with word timestamps), "srt" or "vtt". include_words: Add per-word start/end times (for "text" and "json"). output_path: Optional absolute path to also save the result to. |
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 are cleanly separated by input source: transcribe_file takes a local absolute path, transcribe_url takes a public http(s) link. An agent can pick unambiguously based on whether it has a file or a URL, and the descriptions reinforce this with explicit download/size notes.
Both tools follow the same verb_noun pattern (transcribe_file, transcribe_url) with identical argument sets. The naming is fully predictable and the shared prefix makes the pairing obvious.
Only two tools is thin for a server surface, though the domain (speech-to-text) is narrow enough that it doesn't feel bloated or arbitrary. It sits at the borderline where a single additional capability would round it out.
The core lifecycle—local file and remote URL ingestion, plus text/json/srt/vtt output and optional file saving—is well covered, with no dead ends for the primary use case. Minor gaps exist around async job status for long files, batch processing, and explicit language/model selection.