LuvVoice Text-to-Speech

io.github.franzsy5Published by GitHub account franzsy5v1.0.2Updated Oct 24, 2026

Text-to-speech with 200+ voices in 70+ languages. Requires a LuvVoice API token.

VerifiedSTDIODesktop onlyMedia & Design

Overview

AI-generated overview

A local MCP server that gives an assistant text-to-speech in 200+ voices across 70+ languages through the LuvVoice service.

What you can do
Convert text into spoken audio using LuvVoice voices, choosing from more than 200 voices in over 70 languages. The manifest lists no individual tools, so the exact operations are not documented; the server's stated purpose is text-to-speech synthesis. It runs as a local process started on the user's machine and talks to the LuvVoice service using an API token.
When to use it
Useful when you want an assistant to turn written text into audio, such as narration, voiceovers, or spoken versions of content, and you already use or are willing to sign up for LuvVoice.
Requirements
Runs as a local stdio process, installed from the npm package luvvoice-mcp, so Node.js is needed. Requires a LuvVoice API token supplied in the LUVVOICE_API_TOKEN environment variable, and an API-enabled LuvVoice plan. Network access to the LuvVoice service is implied.
Before you install
The server needs a LuvVoice API token, a secret that should be kept private and scoped to this use. An API-enabled paid plan is required, so usage may incur costs. Text you send is passed to the LuvVoice service for synthesis, so avoid submitting sensitive content. The manifest lists no tools, so review what it can do before installing.

Installation

In SourceWeft

  1. Open LuvVoice Text-to-Speech in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.2LatestOct 15, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.