Skip to main content
Glama
Sign In
MiMo TTS MCP Server

MiMo TTS MCP Server

by haibinwang9
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to MiMo TTS MCP Server

No user-submitted related servers found.

    Related Servers

    • SuperClonica MCP server

      SuperClonica MCP serverofficial

      superclonica-tts
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients such as Claude, Cursor and VS Code to synthesize speech locally in 31 languages, saving mp3, wav or ogg files, listing and installing catalog voices, and playing audio back through the system player — offline after the first run with no usage limits.
      Apache 2.0

    • 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.
      65 PyPI
      MIT

    • FreeTTS

      freetts
      A
      license
      A
      quality
      B
      maintenance
      Text to speech in 149 languages: MP3 links from any assistant. Free without an account. 2,253 voices; PRO adds HD voices, WAV, dialogue with a voice per speaker, Script mode timing and transcription.
      7
      56 npm
      MIT

    • MCP TTS Server

      kristofferv98
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides text-to-speech conversion through a unified MCP interface, supporting both local Kokoro and cloud OpenAI TTS engines with streaming audio, voice selection, and customization via natural language instructions.
      7
      -
    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.1/5.0

    Scored across 4 tools

    Disambiguation5/5

    The three synthesis tools are cleanly differentiated by voice source: preset built-in voice (text_to_speech), invented voice from a description (design_voice_to_speech), and replicated voice from an audio sample (clone_voice_to_speech). list_voices is clearly read-only and metadata-focused, so there is no realistic misselection.

    Naming Consistency5/5

    All three synthesis tools follow a predictable '<source>_to_speech' pattern, and the read-only tool uses the conventional 'list_<noun>' form. The convention is consistent and self-explanatory across the whole set.

    Tool Count5/5

    Four tools is well-scoped for a TTS server: three synthesis modes plus one discovery/introspection tool. Each tool earns its place with no filler or redundancy.

    Completeness4/5

    The surface covers the key TTS lifecycle modes (preset, design, clone) plus model/voice discovery, which is strong for the domain. Minor gaps exist around managing generated output (e.g. listing or deleting written files), but agents can work around this via the returned file paths.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources