MCP server for Rime
MCP server for Rime. The rime mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 7 defined tools rather than through you.
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.
The server ships on npm as @smithery/cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Everything the assistant can do here goes through one of these:
macOS — Uses afplayWindows — Built-in Media.SoundPlayer (PowerShell)Linux — mpg123, mplayer, aplay, or ffplayRIME_GUIDANCE — The main description of when and how to use the speak toolRIME_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")You will need 3 environment variables: RIME_WHEN_TO_SPEAK, RIME_GUIDANCE, RIME_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
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 ffplayAmong the AI and media services options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Rime MCP's toolset — macOS, Windows, Linux and 4 more — is a fair guide to whether it matches your workflow. It is maintained by MatthewDailey; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Rime MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| macOS | Uses afplay |
| Windows | Built-in Media.SoundPlayer (PowerShell) |
| Linux | mpg123, mplayer, aplay, or ffplay |
| 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") |
{
"mcpServers": {
"rime": {
"command": "npx",
"args": ["-y", "@smithery/cli"],
"env": {
"RIME_WHEN_TO_SPEAK": "your-value",
"RIME_GUIDANCE": "your-value",
"RIME_API_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
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| Variable | Description | Required |
|---|---|---|
| RIME_WHEN_TO_SPEAK | Configuration value read at startup. | Optional |
| RIME_GUIDANCE | Configuration value read at startup. | Optional |
| RIME_API_KEY | Credential the server authenticates with. | Yes |
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Search built for AI, not humans — semantic web search that returns model-ready content, plus code context.
Answers, not links — delegate questions to Perplexity's search-grounded models and get cited responses back.
Give your assistant a voice — text-to-speech, voice cloning and audio tools from the ElevenLabs API.
Give your assistant a real code sandbox — isolated cloud VMs for actually running the code it writes.
The ML hub in your context window — search models, datasets, papers and run Spaces from the official server.