Skip to main content
Glama
brunocramos

livechat-mcp

by brunocramos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to livechat-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
      8 npm
      1
      MIT

    • vibevoice-asr

      tjameswilliams
      A
      license
      A
      quality
      C
      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

    • Yak MCP

      thamaji
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents to speak aloud using text-to-speech functionality. Works with agents running inside devcontainers and provides configurable voice settings for creating chatty AI companions.
      4
      -

    • Voice MCP

      shreyaskarnik
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables bidirectional voice interaction for Claude Code using local speech-to-text and text-to-speech models optimized for Apple Silicon. It provides tools to listen to user speech via microphone and speak responses aloud through system speakers.
      16
      Apache 2.0

    • 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
      -
    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.9/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: retrieving input, ending the session, taking over a lock, and resetting state. No overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (e.g., get_voice_input, end_voice_session). The pattern is uniform and predictable.

    Tool Count5/5

    Four tools is well-scoped for a voice session lifecycle. Each tool serves a necessary function with no redundancy, fitting the server's narrow purpose.

    Completeness5/5

    The tool surface covers the full voice session lifecycle: starting clean, retrieving input, ending, and handling cross-process takeover. No obvious dead ends or missing operations for the intended use case.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources