Skip to main content
Glama
xiaobenyang-com

edge-tts

by xiaobenyang-com
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

语音合成服务器

一个集成了Microsoft Edge高质量语音合成能力的MCP服务器，支持多语言语音生成、音频合并和云端存储。 An MCP server integrated with Microsoft Edge's high-quality speech synthesis capabilities, supporting multilingual speech generation, audio merging, and cloud storage.## 工具列表 Tool List

本MCP服务封装下列工具，可让模型通过标准化接口调用以下功能。 本MCP服务封装下列工具，可让模型通过标准化接口调用以下功能。

工具 Tool

描述 Description

generate_speech

Generate speech audio from text using Microsoft Edge TTS. Supports multi-role conversations and audio merging.

检查服务 ## Inspector

工具在线测试： https://mcp.xiaobenyang.com/inspector/1777316659830787

Online Tool test https://mcp.xiaobenyang.com/inspector/1777316659830787

Related MCP server: Edge TTS MCP

服务配置 MCP Server Config

如何获取 XBY-APIKEY ？ How to get XBY-APIKEY ?

访问小笨羊科技网站 https://xiaobenyang.com，注册用户即可获得APIKEY Visit XiaoBenYang website https://xiaobenyang.com, register and get the APIKEY.

SSE

{
  "mcpServers": {
    "语音合成服务器": {
      "headers": {
        "XBY-APIKEY": "<YOUR_XBY_APIKEY>"
      },
      "type": "sse",
      "url": "https://mcp.xiaobenyang.com/1777316659830787/sse"
    }
  }
}

STREAMABLE HTTP

{
  "mcpServers": {
    "语音合成服务器": {
      "headers": {
        "XBY-APIKEY": "<YOUR_XBY_APIKEY>"
      },
      "type": "streamable_http",
      "url": "https://mcp.xiaobenyang.com/1777316659830787/mcp"
    }
  }
}

STDIO

{
    "mcpServers": {
        "语音合成服务器": {
          "command": "npx",
          "args": [
            "-y",
            "xiaobenyang-mcp"
          ],
          "env": {
            "XBY_APIKEY": "<YOUR_XBY_APIKEY>",
            "mcpId": "1777316659830787",
          },
          "transport": "stdio"
        }
      }
}

Available Tools

1 tool
generate_speechgenerate_speechC

Generate speech audio from text using Microsoft Edge TTS. Supports multi-role conversations and audio merging.

ParametersJSON Schema
NameRequiredDescriptionDefault
merge_outputYes
itemsYes

TDQS

C2.8/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'multi-role conversations and audio merging,' which adds some context about features, but fails to cover critical aspects like rate limits, authentication needs, output format, or error handling. For a tool with no annotations, this is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is highly concise and front-loaded, consisting of two efficient sentences that directly state the tool's purpose and key features. Every sentence adds value without redundancy, making it easy for an AI agent to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of audio generation, lack of annotations, no output schema, and low schema coverage, the description is incomplete. It omits details on output format, error conditions, performance limits, and parameter usage, leaving significant gaps for an AI agent to operate effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for undocumented parameters. It implies 'items' relate to text inputs and 'merge_output' controls audio merging, but does not explain parameter meanings, formats, or constraints. This leaves key input details ambiguous, failing to adequately supplement the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Generate speech audio from text using Microsoft Edge TTS.' It specifies the action (generate), resource (speech audio), and technology (Microsoft Edge TTS). However, without sibling tools, it cannot demonstrate differentiation from alternatives, preventing a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It mentions 'Supports multi-role conversations and audio merging,' which hints at capabilities but does not specify use cases, prerequisites, or exclusions. This lack of explicit context limits its utility for an AI agent.

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 observedgenerate_speech
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

B3/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's purpose is clearly defined and distinct by default.

Naming Consistency5/5

A single tool inherently has perfect naming consistency. The tool name 'generate_speech' follows a clear verb_noun pattern, and there are no other tools to compare or create inconsistency with.

Tool Count2/5

One tool is too few for most practical purposes, as it severely limits functionality. While it covers the core TTS generation, the server lacks tools for managing voices, configurations, or other related operations, making the scope feel incomplete and thin.

Completeness2/5

The server is severely incomplete for a TTS domain. It only provides speech generation without tools for listing available voices, adjusting speech parameters, or handling audio playback, leaving significant gaps that agents cannot work around effectively.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • 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

  • Edge TTS MCP

    s-n-n
    A
    license
    A
    quality
    D
    maintenance
    A cross-platform MCP server that enables Claude to speak using Microsoft Edge TTS with support for over 300 voices across 50+ languages. It requires no API keys and allows for customization of speech rate, volume, and pitch.
    3
    2
    MIT

  • Edge-TTS MCP Server

    yangwuan55
    F
    license
    Not graded
    quality
    D
    maintenance
    An MCP server that leverages the Microsoft Edge TTS service to provide high-quality text-to-speech capabilities across over 80 languages. It enables users to generate audio files, query available voices, and create subtitle files using natural language commands.
    -

  • Edge TTS MCP

    Hwenyi
    A
    license
    Not graded
    quality
    D
    maintenance
    An MCP server that converts text into lifelike speech using Microsoft Edge's Text-to-Speech service, supporting customizable voice, rate, volume, and pitch.
    4
    MIT