@speechweave/mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPEECHWEAVE_API_KEY | Yes | Your SpeechWeave API key (starts with sk_live_) |
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 |
|---|---|
| transcribe_fileA | Upload a local audio/video file and wait until transcription finishes. Prefer for short/medium clips when you need the transcript in this turn. Pass an absolute filesystem path (never raw binary). On wait timeout, returns job_id — then call get_job_status. For long audio you plan to poll yourself, use start_job_file instead. |
| transcribe_urlA | Start transcription from a public HTTPS URL and wait until it finishes. Prefer for short/medium media when you need the transcript in this turn. On wait timeout, returns job_id — then call get_job_status. For long audio you plan to poll yourself, use start_job_url instead. |
| start_job_fileA | Upload a local audio/video file and return a job id immediately without waiting. Use for long recordings or when you will poll later with get_job_status. Pass an absolute filesystem path. |
| start_job_urlA | Create a transcription job from a public HTTPS URL and return a job id immediately. Use for long media or deferred workflows; poll with get_job_status until completed, failed, or cancelled. |
| get_job_statusA | Fetch the current status of a transcription job (and transcript when completed). Poll until status is completed, failed, or cancelled. |
| cancel_jobA | Cancel a queued or processing transcription job. Fails if the job is already terminal. |
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 6 tools
Each tool has a clear, distinct role: synchronous vs. asynchronous, file vs. URL, status polling, and cancellation. No ambiguity between any pair.
All tools follow a consistent verb_noun pattern with underscores (e.g., transcribe_file, start_job_url, get_job_status). No mixing of conventions.
With 6 tools covering synchronous and asynchronous transcription from both files and URLs, plus status and cancellation, the count is well-scoped for the domain without redundancy.
Covers all essential operations: create jobs (sync/async, file/URL), check status, cancel. Missing a list-all-jobs endpoint, but core transcription workflow is complete.