Skip to main content
Glama
tvtdev94

clvoice-mcp

by tvtdev94
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to clvoice-mcp

No user-submitted related servers found.

    Related Servers

    • OpenCode Voice MCP Server

      YuvrajSinghBhadoria2
      A
      license
      A
      quality
      B
      maintenance
      Enables voice input for AI coding assistants by recording audio, transcribing it locally with Whisper, and optionally typing the text at the cursor position. Supports multiple languages and works with MCP-compatible tools like OpenCode, Claude Code, and Cursor.
      3
      1 npm
      1
      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
      -

    • Raz

      Mateob6
      A
      license
      Not graded
      quality
      C
      maintenance
      Voice interface for Claude Code enabling hands-free, conversational interaction entirely on-device for Apple Silicon Macs. It provides push-to-talk transcription and automatic spoken responses via local AI models.
      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
    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

    A4.3/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one for dictation and transcription, the other for listing audio devices. No overlap in functionality.

    Naming Consistency5/5

    Both tool names follow a consistent verb_noun pattern: 'voice_listen' and 'list_audio_devices', with snake_case and clear action prefixes.

    Tool Count5/5

    Two tools is appropriate for the narrow scope of voice input: one to configure the device and one to capture input. The tool count matches the domain well.

    Completeness4/5

    The server covers the core needs (capture input, list devices). A minor gap is the lack of a tool to set the microphone device directly, but this is handled via environment variable.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources