Skip to main content
Glama
Sign In
deenesjakoruzh
Rime MCP

Rime MCP

by MatthewDailey
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Rime MCP

rime

A Model Context Protocol (MCP) server that provides text-to-speech capabilities using the Rime API. This server downloads audio and plays it using the system's native audio player.

Features

  • Exposes a speak tool that converts text to speech and plays it through system audio

  • Uses Rime's high-quality voice synthesis API

Related MCP server: AivisSpeech MCP Server

Requirements

  • Node.js 16.x or higher

  • A working audio output device

  • macOS: Uses afplay

There's sample code from Claude for the following that is not tested 🤙✨

  • Windows: Built-in Media.SoundPlayer (PowerShell)

  • Linux: mpg123, mplayer, aplay, or ffplay

MCP Configuration

"ref": {
  "command": "npx",
  "args": ["rime-mcp"],
  "env": {
      RIME_API_KEY=your_api_key_here

      # Optional configuration
      RIME_GUIDANCE="<guide how the agent speaks>"
      RIME_WHO_TO_ADDRESS="<your name>"
      RIME_WHEN_TO_SPEAK="<tell the agent when to speak>"
      RIME_VOICE="cove" 
  }
}

All of the optional env vars are part of the tool definition and are prompts to

All voice options are listed here.

You can get your API key from the Rime Dashboard.

The following environment variables can be used to customize the behavior:

  • RIME_GUIDANCE: The main description of when and how to use the speak tool

  • RIME_WHO_TO_ADDRESS: Who the speech should address (default: "user")

  • RIME_WHEN_TO_SPEAK: When the tool should be used (default: "when asked to speak or when finishing a command")

  • RIME_VOICE: The default voice to use (default: "cove")

Example use cases

Demo of Rime MCP in Cursor

Example 1: Coding agent announcements

"RIME_WHEN_TO_SPEAK": "Always conclude your answers by speaking.",
"RIME_GUIDANCE": "Give a brief overview of the answer. If any files were edited, list them."

Example 2: Learn how the kids talk these days

RIME_GUIDANCE="Use phrases and slang common among Gen Alpha."
RIME_WHO_TO_ADDRESS="Matt"
RIME_WHEN_TO_SPEAK="when asked to speak"

Example 3: Different languages based on context

RIME_VOICE="use 'cove' when talking about Typescript and 'antoine' when talking about Python"

Development

  1. Install dependencies:

npm install

  1. Build the server:

npm run build

  1. Run in development mode with hot reload:

npm run dev

License

MIT

Badges

Installing via Smithery

To install Rime Text-to-Speech Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @MatthewDailey/rime-mcp --client claude

Available Tools

1 tool
speakA

Speak text aloud using Rime's text-to-speech API. Should be used when user asks you to speak or to announce and explain when you finish a command

User configuration:

WHO_TO_ADDRESS: user

WHEN_TO_SPEAK: when asked to speak or when finishing a command

VOICE: cove

GUIDANCE: Use the speak tool to convert text to speech when the user requests audio output or when providing verbal responses

Inputs: text (required), speaker, speedAlpha, reduceLatency.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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

    A3.7/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The speak tool has a single, clearly defined purpose for text-to-speech conversion.

    Naming Consistency5/5

    A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'speak' follows a clear verb pattern appropriate for its function.

    Tool Count2/5

    A single tool is too few for most MCP server purposes, even for a text-to-speech service. This feels thin and limited, lacking complementary tools like volume control, voice selection, or speech status checks that would enhance functionality.

    Completeness2/5

    The tool surface is severely incomplete for a text-to-speech domain. While the speak tool covers the core output function, there are obvious gaps such as no tools for managing voices, adjusting speech parameters, stopping speech, or checking speech status, which limits agent capabilities.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers

    • TTS-MCP

      nakamurau1
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that integrates high-quality text-to-speech capabilities with Claude Desktop and other MCP-compatible clients, supporting multiple voice options and audio formats.
      30 npm
      1
      MIT

    • Edge-TTS MCP Server

      yuiseki
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that provides text-to-speech functionality for AI agents using Microsoft Edge's text-to-speech technology, supporting multiple voices, languages, and voice customization.
      2
      8
      MIT