TextToSpeech-MCP Server

Created By
SmartLittleAppsa year ago
Local text-to-speech MCP server with dual engines (macOS Say + Kokoro TTS) for Claude Desktop
Overview

what is TextToSpeech-MCP Server?

TextToSpeech-MCP Server is a local text-to-speech (TTS) server that provides high-quality, privacy-first TTS synthesis using dual engines: macOS Say and Kokoro TTS, designed for use with Claude Desktop and other MCP-compatible clients.

how to use TextToSpeech-MCP Server?

To use the server, install the necessary dependencies, build the project, and start the server. Configure it in Claude Desktop by adding the appropriate MCP server settings.

key features of TextToSpeech-MCP Server?

  • Local processing with no data sent to external services.
  • Multiple TTS engines: macOS Say (23 voices, multiple languages) and Kokoro TTS (21 voices, high-quality neural synthesis).
  • Multi-language support for 43 languages including English, Spanish, French, Japanese, and Chinese.

use cases of TextToSpeech-MCP Server?

  1. Generating speech for applications that require voice output.
  2. Assisting visually impaired users by converting text to speech.
  3. Enhancing user experience in interactive applications with voice feedback.

FAQ from TextToSpeech-MCP Server?

  • Is the TTS synthesis done locally?

Yes! All processing is done locally, ensuring privacy.

  • What platforms does it support?

Currently, it supports macOS for the macOS Say engine.

  • Can I customize the voice and speed of the speech?

Yes! You can choose from various voices and adjust the speed of the speech synthesis.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
SmartLittleApps
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago