Speechmatics MCP Server
Related Servers
Alternatives to Speechmatics MCP Server
No user-submitted related servers found.
Related Servers
AlicenseAqualityCmaintenanceEnables transcription of audio and video files using mocoVoice API, allowing users to start transcription jobs and retrieve results directly from Claude Desktop.63MIT- AlicenseNot gradedqualityBmaintenanceEnables automated sound design spotting from Claude Code: analyze video, generate cue sheets, search or generate SFX, and export DAW-synchronized stems.2 npmMIT
- AlicenseAqualityDmaintenanceEnables text-to-speech synthesis and voice cloning using VoxCPM2 diffusion model from within Claude Code.4MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to transcribe audio and video from URLs or local files with high accuracy, speaker diarization, 119 languages, and word-level timestamps, while also supporting transcription management and caption export in SRT, WebVTT, or plain text.1493 npm13MIT
- AlicenseAqualityCmaintenanceEnables AI agents to transcribe audio and video with speaker labels, timestamps, and captions via Pepys API.933 npmMIT
- AlicenseBqualityDmaintenanceProvides intelligent transcript processing capabilities for Claude, featuring natural formatting, contextual repair, and smart summarization powered by Deep Thinking LLMs.420MIT
TDQS
Scored across 4 tools
Each tool has a distinct purpose: single-file transcription, batch transcription, reading a transcript, and viewing usage statistics. There is no overlap or ambiguity between the tools, even between transcribe_file and transcribe_directory, as their names clearly indicate the scope of operation.
All tool names follow a consistent verb_noun pattern: transcribe_file, transcribe_directory, get_transcript, get_usage. The verbs (transcribe, get) match the action performed, and the nouns clearly indicate the target. This makes the API predictable and easy to learn.
With just four tools, the server is tightly scoped to its purpose of transcription and transcript retrieval. Each tool is necessary and covers a distinct workflow step, leaving no feeling of bloat or missing essential functionality.
The core transcription workflow is fully covered: transcribing files (individually or in bulk), retrieving the resulting transcript, and checking account usage. There are no obvious gaps for the stated domain; optional operations like deleting or listing transcripts are not essential for the main use case.