MCP VOICEVOX Go

Created By
metapoxa year ago
VOICEVOX MCP Server - Model Context Protocol server for VOICEVOX text-to-speech synthesis
Overview

What is MCP VOICEVOX Go?

MCP VOICEVOX Go is an implementation of a Model Context Protocol (MCP) server that utilizes VOICEVOX for text-to-speech synthesis, allowing users to access VOICEVOX's voice synthesis capabilities from a language model.

How to use MCP VOICEVOX Go?

To use MCP VOICEVOX Go, ensure that VOICEVOX is running locally, clone the repository, and start the server using the provided commands. You can customize server options through command-line arguments or environment variables.

Key features of MCP VOICEVOX Go?

  • Converts text to speech using VOICEVOX.
  • Retrieves a list of available speakers.
  • Customizable server settings through command-line options and environment variables.

Use cases of MCP VOICEVOX Go?

  1. Integrating text-to-speech functionality into applications.
  2. Creating voice responses for chatbots.
  3. Enabling voice synthesis in educational tools.

FAQ from MCP VOICEVOX Go?

  • What are the prerequisites for using MCP VOICEVOX Go?

You need Go 1.21 or higher and a running instance of VOICEVOX.

  • How can I change the default speaker?

You can set the default speaker ID using the --default-speaker option or the MCP_VOICEVOX_DEFAULT_SPEAKER environment variable.

  • Is there a way to run MCP VOICEVOX Go on a different port?

Yes, you can specify a different port using the --port option.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
metapox
Star
0
Language
Go
License
-

Recommend Servers

View All
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)

2 days ago