Skip to main content
Glama
Sign In
mcp-agent-chatterbox

mcp-agent-chatterbox

by ChristofMilius
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-agent-chatterbox

No user-submitted related servers found.

    Related Servers

    • SoundMagic

      JasondeWest
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to perform local audio tasks such as speech synthesis, voice cloning, music and sound effect generation, and audio editing through MCP, with GPU models loaded on demand and released after idle.
      6
      MIT

    • voix

      osmelmora
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to give spoken output by synthesizing text into speech with an on-device neural model and playing it through the user's speakers, entirely offline. Agents can queue spoken summaries and stop playback on demand.
      4 npm
      MIT

    • tts-mcp-server

      RTY2345RR
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to turn scripts into narration audio with matching SRT/VTT captions in one tool call, plus voice cloning from a reference clip and transcription of local audio or video into subtitles.
      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.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: tts_status reports readiness, tts_unload releases VRAM, speak synthesizes audio, list_voices enumerates reference clips, and stop_speech halts playback. There is no overlap or boundary confusion between any pair.

    Naming Consistency3/5

    Naming is mixed: two tools use a 'tts_' prefix (tts_status, tts_unload) while the others do not, and 'speak' is a bare verb while list_voices/stop_speech follow verb_noun. It is still readable snake_case, but the conventions are not predictable as a set.

    Tool Count5/5

    Five tools is well-scoped for a local TTS server: status, unload, speak, list_voices, and stop_speech each cover a necessary lifecycle operation without redundancy. Nothing feels thin or bloated.

    Completeness4/5

    The surface covers the core TTS lifecycle (preflight, synthesize/play, list voices, stop, unload) and the speak tool exposes rich model controls. Minor gaps exist, such as no explicit preload of a model or enumeration of previously generated output files, but agents can work around these.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Resources