Skip to main content
Glama
YuvrajSinghBhadoria2

OpenCode Voice MCP Server

by YuvrajSinghBhadoria2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to OpenCode Voice MCP Server

No user-submitted related servers found.

    Related Servers

    • livechat-mcp

      brunocramos
      A
      license
      A
      quality
      D
      maintenance
      Enables continuous voice conversation with AI coding assistants by locally transcribing speech with Whisper and delivering utterances as text prompts.
      4
      1
      MIT

    • vibevoice-asr

      tjameswilliams
      A
      license
      A
      quality
      D
      maintenance
      Local speech-to-text transcription using Microsoft's VibeVoice-ASR model with speaker diarization, enabling audio transcription directly in AI tools like Claude Code, Cursor, and OpenCode.
      3
      3
      MIT

    • Claude Voice Commands

      JWitcoff
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables natural voice interaction with Claude Code through speech-to-text, supporting wake word activation and multiple backends like Whisper and Google. It allows users to execute commands and control their coding environment hands-free via their microphone.
      2
      -

    • voice-bridge

      Tomorrow-You
      A
      license
      Not graded
      quality
      D
      maintenance
      Multi-engine text-to-speech for AI coding assistants. Speaks responses aloud from Claude Code, Cursor, or VS Code via a Claude Code plugin, MCP server, or CLI pipe.
      35 PyPI
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 3 tools

    Disambiguation3/5

    voice_transcribe and voice_type both perform recording and transcription, differing only in whether the result is typed into the active window. This creates some overlap, though voice_status is clearly distinct. Descriptions clarify the intended use.

    Naming Consistency4/5

    The voice_ prefix is consistent across all tools, but the suffix alternates between a verb (transcribe, type) and a noun (status), slightly breaking the uniform verb pattern. Overall, the naming is predictable and readable.

    Tool Count5/5

    With only three tools, the server is tightly scoped to the core voice capture and transcription workflows. Each tool serves a clear purpose, and the count feels appropriate for the narrow domain.

    Completeness4/5

    The server covers the primary actions of transcribing and typing, plus a status check. Missing optional features like language selection or audio device configuration, but these are not essential to the main workflow.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources