Skip to main content
Glama

Related Servers

Alternatives to voicesmith

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to generate narration in a single fixed, pre-approved voice, returning audio with per-line timing, hashes, and automatic quality checks on content, speaker identity, and pace, all locally and reproducibly.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to manage voices and generate speech, multi-character dubbing, and batch audio through a local TTS service, including health checks and job polling.
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to convert any-length text to speech in saved or cloned voices, generate SRT/VTT captions from local media, and produce per-scene narration with exact durations and frame timings for video timelines.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to access local voice synthesis, zero-shot cloning, and voice catalog tools through native MCP tool calls for applications like Claude and Cursor.
      37 npm
      AGPL 3.0

    TDQS

    B3.2/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct resource+action: list_voices (enumeration) vs voice_info (single-voice detail), speak (start render) vs job_status (poll a render), plus consent guidance, output verification, and a health check. No two tools could plausibly be swapped for the same task.

    Naming Consistency3/5

    The set mixes patterns: verb_noun (list_voices, verify_audio), noun_noun (voice_info, consent_steps, job_status), and bare words (speak, doctor). Names remain readable and self-explanatory, but there is no single predictable convention an agent can rely on.

    Tool Count5/5

    Seven tools is tightly scoped for a voice-rendering server: discovery, consent, render, async polling, verification, and diagnostics each earn their place with no filler or redundancy.

    Completeness4/5

    The lifecycle is well covered end-to-end: find a voice, learn consent requirements, render, poll, and verify output provenance, plus a setup doctor. Minor gaps exist — no tool to cancel a running job, list active jobs, or adjust the voice tuning that voice_info exposes — but these are workaroundable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues