Skip to main content
Glama
BACH-AI-Tools

Youtube Mp36 MCP Server

by BACH-AI-Tools
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Youtube Mp36 MCP Server

English | 简体中文 | 繁體中文

用于访问 Youtube Mp36 API 的 MCP 服务器。

🚀 使用 EMCP 平台快速体验

EMCP 是一个强大的 MCP 服务器管理平台，让您无需手动配置即可快速使用各种 MCP 服务器！

快速开始：

  1. 🌐 访问 EMCP 平台

  2. 📝 注册并登录账号

  3. 🎯 进入 MCP 广场，浏览所有可用的 MCP 服务器

  4. 🔍 搜索或找到本服务器（bach-youtube_mp36）

  5. 🎉 点击 "安装 MCP" 按钮

  6. ✅ 完成！即可在您的应用中使用

EMCP 平台优势：

  • ✨ 零配置：无需手动编辑配置文件

  • 🎨 可视化管理：图形界面轻松管理所有 MCP 服务器

  • 🔐 安全可靠：统一管理 API 密钥和认证信息

  • 🚀 一键安装：MCP 广场提供丰富的服务器选择

  • 📊 使用统计：实时查看服务调用情况

立即访问 EMCP 平台 开始您的 MCP 之旅！

Related MCP server: Youtube Mp310 MCP Server

简介

这是一个 MCP 服务器，用于访问 Youtube Mp36 API。

  • PyPI 包名: bach-youtube_mp36

  • 版本: 1.0.0

  • 传输协议: stdio

安装

从 PyPI 安装:

pip install bach-youtube_mp36

从源码安装:

pip install -e .

运行

方式 1: 使用 uvx（推荐，无需安装）

# 运行（uvx 会自动安装并运行）
uvx --from bach-youtube_mp36 bach_youtube_mp36

# 或指定版本
uvx --from bach-youtube_mp36@latest bach_youtube_mp36

方式 2: 直接运行（开发模式）

python server.py

方式 3: 安装后作为命令运行

# 安装
pip install bach-youtube_mp36

# 运行（命令名使用下划线）
bach_youtube_mp36

配置

API 认证

此 API 需要认证。请设置环境变量:

export API_KEY="your_api_key_here"

环境变量

变量名

说明

必需

API_KEY

API 密钥

是

PORT

不适用

否

HOST

不适用

否

在 Cursor 中使用

编辑 Cursor MCP 配置文件 ~/.cursor/mcp.json:

{
  "mcpServers": {
    "bach-youtube_mp36": {
      "command": "uvx",
      "args": ["--from", "bach-youtube_mp36", "bach_youtube_mp36"],
      "env": {
        "API_KEY": "your_api_key_here"
      }
    }
  }
}

在 Claude Desktop 中使用

编辑 Claude Desktop 配置文件 claude_desktop_config.json:

{
  "mcpServers": {
    "bach-youtube_mp36": {
      "command": "uvx",
      "args": ["--from", "bach-youtube_mp36", "bach_youtube_mp36"],
      "env": {
        "API_KEY": "your_api_key_here"
      }
    }
  }
}

可用工具

此服务器提供以下工具:

get_mp3

Convert to MP3 at the default bit rate. Quota cost will apply according to the length of the mp3 file.

端点: GET /dl

参数:

  • id (string) 必需: Quota cost will apply according to the length of the mp3 file. Quota is calculated as follows: if length <= 30 then 1 if 30 < length <= 60 then 2 if 60 < length <= 90 then 4 if 90 < length <= 120 then 5 if 120 < length <= 150 then 6 7 if 150 < length <= 180 then 7 8 if 180 < length <= 210 then 9 if 210 < length <= 240 then 10 (Note: length unit is minute) For trim/cut request, length of the original mp3 file is used for quota. If the trimmed mp3 file served from storage then trimmed length is us

  • cut (number): Cut the mp3 according to the provided sStart and sEnd parameters. The value must be provided as 1. The quota Cost is +1.

  • sStart (string): Starting point for cutting the mp3. Format must be HH:MM:SS

  • sEnd (string): End point for cutting the mp3. Format must be HH:MM:SS

技术栈

  • 传输协议: stdio

  • HTTP 客户端: httpx

许可证

MIT License - 详见 LICENSE 文件。

开发

此服务器由 API-to-MCP 工具生成。

版本: 1.0.0

Available Tools

1 tool
get_mp3B

Convert to MP3 at the default bit rate. Quota cost will apply according to the length of the mp3 file.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesQuota cost will apply according to the length of the mp3 file. Quota is calculated as follows: if length <= 30 then 1 if 30 < length <= 60 then 2 if 60 < length <= 90 then 4 if 90 < length <= 120 then 5 if 120 < length <= 150 then 6 7 if 150 < length <= 180 then 7 8 if 180 < length <= 210 then 9 if 210 < length <= 240 then 10 (Note: length unit is minute) For trim/cut request, length of the original mp3 file is used for quota. If the trimmed mp3 file served from storage then trimmed length is us
cutNoCut the mp3 according to the provided sStart and sEnd parameters. The value must be provided as 1. The quota Cost is +1.0
sStartNoStarting point for cutting the mp3. Format must be HH:MM:SS
sEndNoEnd point for cutting the mp3. Format must be HH:MM:SS

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses quota costs based on file length, which is a key behavioral trait (resource consumption). However, it lacks details on other aspects like error handling, rate limits, authentication needs, or what happens during conversion (e.g., is it destructive to the original?). It adds some value but is incomplete for a mutation tool.

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

Conciseness4/5

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

The description is concise with two sentences that directly address conversion and quota costs. It is front-loaded with the main purpose. However, the second sentence could be more structured, and it slightly repeats quota info from the schema, but overall it's efficient with minimal waste.

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

Completeness3/5

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

Given no annotations, no output schema, and a mutation tool (conversion), the description is moderately complete. It covers purpose and quota costs, but misses details like return values, error conditions, or full behavioral context. It's adequate as a minimum viable description but has clear gaps for a tool with parameters and potential side effects.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description does not add any meaning beyond what the schema provides regarding parameters; it only mentions quota costs generally. Baseline is 3 when schema does the heavy lifting, and the description doesn't compensate with extra insights.

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: 'Convert to MP3 at the default bit rate.' It specifies the action (convert) and resource (to MP3), but lacks differentiation from siblings since none exist, so it can't achieve a perfect score. The description is specific and not tautological.

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 quota costs, which might imply usage considerations, but does not explicitly state when or why to invoke it, nor does it address prerequisites or exclusions. Without siblings, this is less critical, but still a gap.

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. 1 tool update
    • First observedget_mp3
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.3/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined as converting to MP3 at a default bit rate, making it distinct by default.

Naming Consistency5/5

The single tool name 'get_mp3' follows a clear verb_noun pattern (get + mp3), which is consistent and predictable. Since there is only one tool, there is no inconsistency to evaluate.

Tool Count2/5

A single tool is too few for a server named 'Youtube Mp36 MCP Server', which implies a broader scope for YouTube MP3-related operations. This minimal set feels thin and underdeveloped for the apparent domain, limiting functionality to just conversion without other expected features like search, download options, or metadata handling.

Completeness2/5

The tool surface is severely incomplete for a YouTube MP3 server. It only provides conversion to MP3 at a default bit rate, missing obvious operations such as searching for videos, specifying bit rates, handling playlists, or retrieving metadata. This will likely cause agent failures when trying to perform common tasks in this domain.

Maintenance

ActivityInactive
ResponsivenessNo issues

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

Related MCP Servers

Latest Blog Posts

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/BACH-AI-Tools/bachai-youtube-mp36'

If you have feedback or need assistance with the MCP directory API, please join our Discord server