Skip to main content
Glama
enesjakozh
kentaro

AivisSpeech MCP Server

by kentaro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

AivisSpeech MCP 服务器

AivisSpeech 的模型上下文协议 (MCP) 服务器实现。该服务器与AivisSpeech引擎配合，提供语音合成接口。通过MCP协议，AivisSpeech的语音合成能力可以轻松被AI助手等应用程序使用。

概述

AivisSpeech MCP 服务器提供以下功能：

  • 符合 MCP 协议的 API 端点

  • 与 AivisSpeech Engine 合作的高质量语音合成

  • 使用 TypeScript 进行类型安全设计

  • 易于配置且高度可扩展的架构

Related MCP server: TTS-MCP

先决条件

  • Node.js 18.x 或更高版本

  • npm 9.x 或更高版本

  • AivisSpeech 引擎（需要单独安装）

安装

# リポジトリをクローン
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"

环境设置

在您的.env文件中，设置以下内容：

# AivisSpeech API Configuration
AIVIS_SPEECH_API_URL=http://localhost:10101  # AivisSpeech EngineのAPIエンドポイント

# Speaker Configuration
AIVIS_SPEECH_SPEAKER_ID=888753760  # デフォルトのスピーカーID

光标 MCP 设置

在.cursor/mcp.json文件中，配置以下内容：

{
  "mcpServers": {
    "AivisSpeech-MCP": {
      "command": "node",
      "args": ["/path/to/aivis-speech-mcp/dist/index.js"]
    }
  }
}

将/path/to/aivis-speech-mcp/dist/index.js替换为您的项目路径。对于 Windows，请转义反斜杠或使用正斜杠。例如： "C:/Users/username/path/to/aivis-speech-mcp/dist/index.js"

如何使用

开发模式

在开发过程中，您可以使用以下命令通过热重载启动服务器：

npm run dev

建造

要构建生产环境，请运行以下命令：

npm run build

生产模式

构建完成后，使用以下命令以生产模式启动服务器：

npm start

测试

要运行测试，请使用以下命令：

npm test

建筑学

AivisSpeech MCP 服务器由以下组件组成：

  • MCP服务：提供符合模型上下文协议的服务器，处理来自客户端的请求。

  • AivisSpeech 服务：与 AivisSpeech 引擎 API 通信并执行语音合成。

API 规范

提供符合 MCP 协议的 API 端点。主要特点包括：

  • 语音合成（从文本生成语音）

  • 获取演讲者信息

  • 音频风格设置

详细API规范请参考AivisSpeech引擎API规范。

与 MCP 协议集成

该服务器实现了模型上下文协议（MCP），可以被AI助手等应用程序无缝使用。有关 MCP 协议的更多信息，请参阅MCP 官方文档。

故障排除

常见问题及解决方案：

  • 无法连接到 AivisSpeech 引擎：检查.env文件中的AIVIS_SPEECH_API_URL是否设置正确

  • 没有声音：检查系统的音频设置并确保选择了正确的音频设备

  • 未找到扬声器 ID ：确保 AivisSpeech 引擎正常运行并检查可用的扬声器 ID。

贡献

请通过我们的 GitHub 问题跟踪器报告错误或功能请求。也欢迎拉取请求。

执照

麻省理工学院

致谢

Available Tools

1 tool
aivis-speech-synthesisD
ParametersJSON Schema
NameRequiredDescriptionDefault
intonation_scaleNoイントネーションのスケール（1.0が標準）
output_sampling_rateNo出力音声のサンプリングレート（Hz）
pitch_scaleNo音高のスケール（1.0が標準）
post_phoneme_lengthNo音声の末尾の無音時間（秒）
pre_phoneme_lengthNo音声の先頭の無音時間（秒）
speaker_idNo音声合成に使用するスピーカーのID
speed_scaleNo話速のスケール（1.0が標準）
style_idNo音声合成に使用するスタイルのID
textYes音声合成するテキスト
volume_scaleNo音量のスケール（1.0が標準）

TDQS

D1/5.0
Behavior1/5

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.

Conciseness1/5

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.

Completeness1/5

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.

Parameters1/5

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.

Purpose1/5

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.

Usage Guidelines1/5

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.

  1. 1 tool updatev1.0.0
    • First observedaivis-speech-synthesis
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

D1.7/5.0

Scored across 1 tool

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count2/5

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.

Completeness1/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • TTS-MCP

    nakamurau1
    A
    license
    Not graded
    quality
    C
    maintenance
    A 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.
    23 npm
    1
    MIT

  • Voicevox MCP Server

    Dosugamea
    A
    license
    B
    quality
    F
    maintenance
    A 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.
    1
    12
    MIT

  • Edge-TTS MCP Server

    yuiseki
    A
    license
    B
    quality
    D
    maintenance
    A 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.
    2
    8
    MIT

Appeared in Searches