All Voice Lab MCP

Created By
allvoicelaba year ago
Official AllVoiceLab Model Context Protocol (MCP) server, supporting interaction with powerful text-to-speech and video translation APIs. Enables MCP clients like Claude Desktop, Cursor, Windsurf, OpenAI Agents to generate speech, translate videos, and perform intelligent voice conversion. Serves scenarios such as short drama localization for global markets, AI-Generated audiobooks, AI-Powered production of film/TV narration.
Overview

What is AllVoiceLab MCP?

AllVoiceLab MCP is a service that provides voice synthesis and voice conversion functionality. It is fully compatible with the MCP (Model Control Protocol), enabling seamless integration with intelligent assistants that support this protocol.

How to use AllVoiceLab MCP?

To use AllVoiceLab MCP, you need to obtain an API key from AllVoiceLab, then install and configure the service using uv (Python package manager). You can integrate the service through Claude Desktop or in MCP clients such as Cline.

Key features of AllVoiceLab MCP?

  • Provides multiple core API interfaces, including getting supported voice models, available voices, text-to-speech, and voice conversion functionality.
  • Supports multiple languages, including Chinese, English, Japanese, French, German, and Korean.
  • Supports integration with intelligent assistants compatible with the MCP protocol.
  • Provides advanced voice synthesis parameters such as speech rate adjustment.
  • Offers long text translation capabilities for processing extensive content across supported languages.
  • Features subtitle extraction technology to identify and process text from video content.

Use cases of AllVoiceLab MCP?

  • Converting text to natural and fluent speech.
  • Using different voice models and voices for speech synthesis.
  • Performing voice conversion, transforming one voice into another.
  • Adding natural voice capabilities to intelligent assistants, virtual characters, or applications.
  • Translating long-form content between multiple languages while maintaining context and meaning.
  • Extracting and processing subtitles from video content for translation or accessibility purposes.

FAQ from AllVoiceLab MCP?

  • What is the MCP protocol?

MCP (Model Control Protocol) is a standard used for integrating various services and tools in a unified way. More detailed information can be found in the official MCP documentation.

  • Is there a fee for using the AllVoiceLab API?

Using the AllVoiceLab API may require payment. For specific pricing details, please check the AllVoiceLab official website.

  • How to solve problems in API usage?

You can refer to the official documentation or community forums for troubleshooting tips, or check the log records in the project for more detailed error information.

  • Which languages are supported?

AllVoiceLab MCP supports multiple languages, including Chinese (zh), English (en), Japanese (ja), French (fr), German (de), and Korean (ko).

Server Config

{
  "mcpServers": {
    "AllVoiceLab": {
      "command": "uvx",
      "args": [
        "allvoicelab-mcp"
      ],
      "env": {
        "ALLVOICELAB_API_KEY": "<insert-your-api-key-here>",
        "ALLVOICELAB_API_DOMAIN": "<insert-api-domain-here>",
        "ALLVOICELAB_BASE_PATH": "optional, default is user home directory.This is uesd to store the output files."
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
10 months ago
Author Name
allvoicelab
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Voyei

2 hours ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago