Skip to main content
Glama
tsushanth

realtime-tts-mcp

by tsushanth
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

realtime-tts-mcp

An MCP server wrapping a real-time, streaming text-to-speech gateway (Kokoro-82M, GPU-capable) as a single synthesize_speech tool. Returns a playable WAV file.

Tool

  • synthesize_speech(text, voice?, speed?) — converts text to spoken audio. voice defaults to af_heart (a Kokoro voice id); speed defaults to 1.0.

Related MCP server: Kokoro MCP Server

Install

git clone https://github.com/tsushanth/realtime-tts-mcp.git
cd realtime-tts-mcp
npm install
npm run build

Add to your MCP client config:

{
  "mcpServers": {
    "realtime-tts": {
      "command": "node",
      "args": ["/absolute/path/to/realtime-tts-mcp/dist/index.js"],
      "env": {
        "REALTIME_TTS_API_KEY": "rtts_your_key_here"
      }
    }
  }
}

Getting an API key

Key issuance is manual right now — there's no self-serve signup yet. Reach out and one will be issued. Without a key, calls will fail with invalid or missing API key.

What actually happens on a call

The gateway auto-provisions a GPU worker on your first request if none is warm, which can take up to a few minutes — the default 60s timeout (REALTIME_TTS_TIMEOUT_MS env var) may need to be raised for a genuinely cold start. The worker tears itself down after 15 minutes of inactivity, so infrequent use means occasional slow first-calls rather than a constantly-billed idle server.

Environment variables

Variable

Default

Purpose

REALTIME_TTS_ENDPOINT

wss://realtime-tts-gateway.fly.dev/tts

Gateway WebSocket URL

REALTIME_TTS_API_KEY

(none)

Required for gated access

REALTIME_TTS_TIMEOUT_MS

60000

Per-synthesis timeout, raise for cold starts

License

MIT

Available Tools

1 tool
synthesize_speechA

Convert text to spoken audio using a real-time, streaming Kokoro-82M TTS gateway. Returns a playable WAV file. The gateway currently runs on an unauthenticated CPU fallback (multi-second latency) — no API key required, but expect a few seconds per call.

ParametersJSON Schema
NameRequiredDescriptionDefault
textYesText to synthesize
speedNoPlayback speed multiplier (default 1.0)
voiceNoKokoro voice id (default "af_heart")

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full behavioral disclosure burden. It proactively discloses the unauthenticated CPU fallback, latency expectations, and output format. It does not mention rate limits or text-length constraints, but the core runtime behavior and authentication requirements are transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences with no filler. The primary action is front-loaded, and the latency/auth caveat is delivered concisely. Every sentence adds either functional or operational value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter TTS tool with no output schema, the description covers the essential context: what it does, what it returns, and current performance constraints. It could mention voice-id availability or input size limits, but the schema provides the parameter structure and the description provides sufficient operational context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description does not add any parameter-specific meaning beyond the schema; it focuses on overall tool behavior. Since the schema already documents text, speed, and voice, the lack of additional detail is acceptable.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Convert text to spoken audio using a real-time, streaming Kokoro-82M TTS gateway.' It also states the concrete output ('Returns a playable WAV file'), making the tool's function unmistakable even without sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear operational context: it is unauthenticated, requires no API key, and has multi-second latency. This implicitly tells an agent when use is acceptable (when latency is tolerable and no auth is available), though it does not explicitly discuss alternatives or exclusions since no siblings exist.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.1/5.0
Disambiguation5/5

With only one tool, there is no possibility of overlap or confusion. synthesize_speech clearly indicates its single purpose of converting text to audio.

Naming Consistency5/5

The tool name follows a clear verb_noun pattern and directly matches the server's TTS purpose. There are no conflicting naming conventions to assess.

Tool Count3/5

A single tool is reasonable for a narrowly scoped TTS server, but the surface feels thin because related capabilities like voice selection or streaming control are absent.

Completeness3/5

The core text-to-speech operation is covered, but the toolset lacks visible voice, format, or streaming options that would be expected in a realtime TTS service. It works for basic synthesis but leaves notable gaps.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tsushanth/realtime-tts-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server