EarSay MCP
Related Servers
Alternatives to EarSay MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to submit and manage durable long-form audio transcription jobs, and read or export structured transcripts via MCP tools.1MIT
- FlicenseNot gradedqualityCmaintenanceEnables MCP-aware agents to queue and run faster-whisper transcription jobs on a shared GPU, with tools to submit audio, poll job status, cancel jobs, and inspect queue status.-
- AlicenseNot gradedqualityBmaintenanceEnables voice-first interactions with AI agents and MCP tools, supporting speech input/output, STT/TTS, and a provider-independent agent core.1MIT
- AlicenseAqualityDmaintenanceProvides browser automation, audio transcription, and LLM chat as MCP tools for any agent.7MIT
- AlicenseNot gradedqualityAmaintenanceGive your AI agents the ability to listen. Microphone capture and speech-to-text tools for MCP-compatible agents.51 npm10Apache 2.0
- AlicenseAqualityFmaintenanceEnables AI agents to interact with the ParrotScribe transcription service on macOS, providing tools to start/stop transcription, retrieve real-time and historical transcripts, and search across sessions.80MIT
TDQS
Scored across 8 tools
Each tool targets a distinct action on the transcription service: lifecycle (start/stop/pause/resume), retrieval (full vs. incremental), checkpointing, and status. The only potential overlap between voice_get_new and voice_get_text is clearly resolved by their descriptions (incremental since checkpoint vs. all text). No two tools perform the same operation.
All tool names follow the voice_<action> pattern using snake_case consistently. Actions are clear verbs or verb-noun combinations (get_new, set_checkpoint, start, stop, pause, resume). This uniformity makes the set predictable and easy to navigate.
With 8 tools, the set is well-scoped for a transcription server. Each tool fulfills a necessary role in the lifecycle, from initialization to text retrieval and checkpoint management. No tool is redundant or extraneous.
The tool surface covers the full lifecycle: start/stop, pause/resume, full and incremental text retrieval, checkpoint setting, and status monitoring. This provides all essential operations for interacting with the EarSay transcription server, with no obvious gaps that would hinder typical workflows.