AivisSpeech MCP Server
Enables configuration of the server through environment variables, allowing customization of API endpoints and speaker settings
Used for cloning the repository and managing the source code
Hosts the repository and provides issue tracking for bug reports and feature requests
Runtime environment required to run the MCP server (version 18.x or higher)
Package manager used for installing dependencies and running scripts (version 9.x or higher)
Provides type-safe design for the server implementation
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@AivisSpeech MCP Serversynthesize 'Welcome to our meeting' with speaker ID 888753760"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
AivisSpeech MCP Server
This is an implementation of the Model Context Protocol (MCP) server for AivisSpeech. This server works with the AivisSpeech Engine to provide an interface for speech synthesis. Through the MCP protocol, it becomes easy to use AivisSpeech's speech synthesis function from applications such as AI assistants.
overview
AivisSpeech MCP Server provides the following features:
MCP protocol compliant API endpoints
High-quality voice synthesis in cooperation with AivisSpeech Engine
Type-safe design with TypeScript
Easy to configure and highly scalable architecture
Related MCP server: TTS-MCP
Prerequisites
Node.js 18.x or higher
npm 9.x or higher
AivisSpeech Engine (requires separate installation)
install
# リポジトリをクローン
git clone https://github.com/kentaro/aivis-speech-mcp.git
cd aivis-speech-mcp
# 依存関係のインストール
npm install
# ビルド
npm run build
# 環境変数の設定
cp .env.sample .env
# .envファイルを編集して、必要な設定を行ってください
# Cursor MCPの設定
cp .cursor/mcp.json.sample .cursor/mcp.json
# mcp.jsonファイル内の"/path/to/aivis-speech-mcp/dist/index.js"を
# 実際のプロジェクトパスに書き換えてください
# 例: "C:/Users/username/path/to/aivis-speech-mcp/dist/index.js"Environment settings
In your .env file, set the following:
# AivisSpeech API Configuration
AIVIS_SPEECH_API_URL=http://localhost:10101 # AivisSpeech EngineのAPIエンドポイント
# Speaker Configuration
AIVIS_SPEECH_SPEAKER_ID=888753760 # デフォルトのスピーカーIDCursor MCP Settings
In .cursor/mcp.json file, configure the following:
{
"mcpServers": {
"AivisSpeech-MCP": {
"command": "node",
"args": ["/path/to/aivis-speech-mcp/dist/index.js"]
}
}
}Replace /path/to/aivis-speech-mcp/dist/index.js with the path to your project. For Windows, escape the backslashes or use forward slashes. For example: "C:/Users/username/path/to/aivis-speech-mcp/dist/index.js"
How to use
Development Mode
During development you can start the server with hot reloading with the following command:
npm run devBuild
To build for production run the following command:
npm run buildProduction Mode
After building, start the server in production mode with the following command:
npm starttest
To run the tests use the following command:
npm testarchitecture
AivisSpeech MCP Server consists of the following components:
MCP Service : Provides a server that complies with the Model Context Protocol and processes requests from clients.
AivisSpeech Service : Communicates with the AivisSpeech Engine API and performs speech synthesis.
API Specifications
We provide API endpoints that comply with the MCP protocol. The main features are as follows:
Speech synthesis (generating speech from text)
Get speaker information
Audio style settings
For detailed API specifications, please refer to AivisSpeech Engine API Specification .
Integration with MCP protocol
This server implements the Model Context Protocol (MCP) and can be used seamlessly with applications such as AI assistants. For more information about the MCP protocol, see the official MCP documentation .
troubleshooting
Common issues and solutions:
Can't connect to AivisSpeech Engine : Check if
AIVIS_SPEECH_API_URLin.envfile is set correctlyNo sound : Check your system's audio settings and make sure the correct audio device is selected
Speaker ID not found : Make sure AivisSpeech Engine is running properly and check for available speaker IDs.
contribution
Please report bugs and feature requests via our GitHub issue tracker. Pull requests are also welcome.
license
Acknowledgements
Aivis Speech Engine Team
Developer of Model Context Protocol
Available Tools
1 toolaivis-speech-synthesisD
| Name | Required | Description | Default |
|---|---|---|---|
| intonation_scale | No | イントネーションのスケール(1.0が標準) | |
| output_sampling_rate | No | 出力音声のサンプリングレート(Hz) | |
| pitch_scale | No | 音高のスケール(1.0が標準) | |
| post_phoneme_length | No | 音声の末尾の無音時間(秒) | |
| pre_phoneme_length | No | 音声の先頭の無音時間(秒) | |
| speaker_id | No | 音声合成に使用するスピーカーのID | |
| speed_scale | No | 話速のスケール(1.0が標準) | |
| style_id | No | 音声合成に使用するスタイルのID | |
| text | Yes | 音声合成するテキスト | |
| volume_scale | No | 音量のスケール(1.0が標準) |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
v1.0.0- First observed
aivis-speech-synthesis
TDQS
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'aivis-speech-synthesis' stands alone with a distinct purpose, so agents cannot misselect among multiple options.
A single tool inherently has consistent naming, as there are no other tools to compare it against. The name 'aivis-speech-synthesis' follows a clear pattern of domain-specific naming, and no inconsistencies can arise from a set of one.
A single tool for a speech synthesis server is too few for typical use cases, as it lacks essential operations like configuration, status checks, or batch processing. This minimal scope limits functionality and suggests an incomplete or overly simplistic implementation for the domain.
The tool set is severely incomplete for a speech synthesis domain, offering only synthesis without any supporting operations like listing voices, adjusting parameters, checking synthesis status, or handling errors. This creates significant gaps that will likely cause agent failures in real-world scenarios.
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
MCP server exposing the AceDataCloud Fish Audio API (text-to-speech with voice conditioning)
A Model Context Protocol server for Wix AI tools
MCP server for Text-to-Speech
Related MCP Servers
- AlicenseBqualityDmaintenanceA Model Context Protocol server that provides text-to-speech capabilities using the Kokoro TTS model, offering multiple voice options and customizable speech parameters.4251MIT
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol server that integrates high-quality text-to-speech capabilities with Claude Desktop and other MCP-compatible clients, supporting multiple voice options and audio formats.171MIT
- AlicenseBqualityFmaintenanceA server that enables Claude 3.7 and other AI agents to access VOICEVOX-compatible speech synthesis engines (AivisSpeech, VOICEVOX, COEIROINK) through the Model Context Protocol.112MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server that provides text-to-speech functionality for AI agents using Microsoft Edge's text-to-speech technology, supporting multiple voices, languages, and voice customization.28MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/kentaro/aivis-speech-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server