MCP.so
ログイン

TTS MCP Server

@leo9iota

基本情報

カテゴリ

その他

ライセンス

MIT

トランスポート

stdio

作者

leo9iota

投稿者

leo9iota

TTS MCP Server について

Text-to-Speech MCP Server for IDEs

TTS MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "tts-mcp": {
      "command": "/absolute/path/to/extracted/tts-mcp",
      "args": [],
      "env": {
        "FISH_AUDIO_API_KEY": "<OPTIONAL_KEY>",
        "ELEVENLABS_API_KEY": "<OPTIONAL_KEY>"
      }
    }
  }
}

TTS MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is TTS MCP?

TTS MCP is an MCP server that provides Text-to-Speech capabilities. It accepts text output from LLMs, synthesizes it using remote or local audio providers, and plays it directly through the host system's native speakers.

How to use TTS MCP?

Download the pre-compiled binary for your OS from the Releases page, or build from source with Go 1.22+ via just init. Configure API keys in a .env file located in your standard OS configuration directory (e.g., ~/.config/tts-mcp/.env on Linux) using either the tts-mcp-config CLI or manual editing. Then attach the server as a command-line MCP tool in your preferred AI editor, such as Claude Desktop, Cursor, or Antigravity.

Key features of TTS MCP

  • Direct playback of synthesized audio through host system speakers.
  • Aggregates multiple TTS providers into individual command tools.
  • Persona routing maps voices and providers to semantic names.
  • Caches generated audio artifacts locally to an XDG cache directory.

Use cases of TTS MCP

  • Giving spoken voice output to LLM responses in AI editors.
  • Routing text output to specific TTS voices and providers using semantic personas.
  • Offline replay of generated audio through local cache.

よくある質問

1

Which TTS providers are supported?

FishAudio, ElevenLabs, Neets AI, PlayHT, Cartesia, OpenAI, Azure, and Local APIs.

2

What are the runtime or build dependencies?

Building from source requires Go 1.22+. Pre-compiled binaries are available for Windows, Linux, and macOS.

3

Where is the configuration file stored?

The `.env` file is placed in the standard OS configuration directory: `%APPDATA%\tts-mcp` (Windows), `~/.config/tts-mcp` (Linux), or `~/Library/Application Support/tts-mcp` (macOS).

4

How are cached audio files stored?

Cached audio artifacts are saved locally to an XDG cache directory.

5

Is there a CLI tool to set up configuration?

Yes, the `tts-mcp-config` CLI tool can safely initialize the `.env` file.

コメント

「その他」の他のコンテンツ