Voxloom MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VOXLOOM_API_KEY | Yes | Your API key | |
| VOXLOOM_WAIT_MS | No | How long transcribe waits before handing back a job id | 90000 |
| VOXLOOM_BASE_URL | No | Override for self-hosting | https://voxloom.ai |
| VOXLOOM_MAX_CHARS | No | Text budget for a transcript read | 12000 |
| VOXLOOM_MAX_CREDITS_PER_CALL | No | Spend ceiling per transcribe call | 3600 |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| estimateA | What a recording would cost and how long it would take, without transcribing it or charging anything. Call this first whenever the recording might be long, or the user has not already agreed to spend. Returns the media length, the price in minutes, whether the balance covers it, and an ETA that accounts for the queue. |
| transcribeA | Transcribes a recording and returns the transcript. This charges the user's account, by the length of the recording. Waits for the result and returns it if the job finishes in time. For a long recording it returns a job id instead; call Refuses anything costing more than 30m of minutes unless |
| get_transcriptA | Fetches a transcript by job id, or reports progress if it is still running. Free, and does not charge anything. Returns a budgeted excerpt rather than the whole transcript, and says so when it truncates. For a question about a specific moment, use |
| search_transcriptA | Searches a finished transcript and returns matching turns with their timestamps and speakers. Free. Prefer this over reading a whole transcript when the question is about a specific topic or moment. Note it is a literal text search, not a semantic one, so search for words that were actually spoken rather than a paraphrase. |
| get_summaryA | The abstract, key points, verbatim pull quotes with timestamps, and timestamped chapters for a finished transcript. Free. The cheapest way to find out what a long recording is about. Only present if the job was run with the |
| list_transcriptsA | The account's transcripts, newest first, with their job ids. Free. Use this to find the id of something transcribed earlier. |
| get_speakersA | Who is in a transcript, how long each one speaks, and their speaker ids for renaming. Free. Speaking time is usually the quickest way to tell an interviewer from an interviewee. |
| rename_speakerA | Replaces a speaker's label across the whole transcript in one operation, including in every export. Free. Get the speaker ids from |
| cancel_transcriptionA | Stops a running job. The unprocessed remainder is refunded; the part already transcribed stays charged, because that work was done. |
| list_languagesA | Every language that can be transcribed, and which of them can be translated into. Free. Check a target here before asking for a translation: more languages can be transcribed than translated into. |
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 10 tools
Each tool has a clearly distinct role: estimate (free pricing/preview), transcribe (charges), get_transcript (fetch by id), search_transcript (literal search), get_summary (abstract), plus account/list/speaker lifecycle tools. Descriptions even cross-reference each other to steer selection (e.g., search vs get vs summary). No meaningful overlap.
Most tools follow a verb_noun pattern (get_transcript, search_transcript, get_summary, list_transcripts, get_speakers, rename_speaker, cancel_transcription, list_languages). The two bare verbs 'estimate' and 'transcribe' deviate slightly, but the style remains readable and predictable.
Ten tools for a transcription service is well-scoped: pricing, execution, retrieval in several modes, speaker management, cancellation, and language listing each earn their place without redundancy.
Full lifecycle is covered: estimate → transcribe → retrieve/summarize/search → manage speakers → cancel, plus language discovery. Minor gap: list_languages references translations ('check a target before asking for a translation'), implying a translate operation that no tool exposes.