Skip to main content
Glama
BACH-AI-Tools

Youtube Mp310 MCP Server

by BACH-AI-Tools
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Youtube Mp310 MCP Server

English | 简体中文 | 繁體中文

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

🚀 使用 EMCP 平台快速体验

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

快速开始：

  1. 🌐 访问 EMCP 平台

  2. 📝 注册并登录账号

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

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

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

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

EMCP 平台优势：

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

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

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

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

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

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

Related MCP server: Youtube Mp36 MCP Server

简介

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

  • PyPI 包名: bach-youtube_mp310

  • 版本: 1.0.0

  • 传输协议: stdio

安装

从 PyPI 安装:

pip install bach-youtube_mp310

从源码安装:

pip install -e .

运行

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

# 运行（uvx 会自动安装并运行）
uvx --from bach-youtube_mp310 bach_youtube_mp310

# 或指定版本
uvx --from bach-youtube_mp310@latest bach_youtube_mp310

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

python server.py

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

# 安装
pip install bach-youtube_mp310

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

配置

API 认证

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

export API_KEY="your_api_key_here"

环境变量

变量名

说明

必需

API_KEY

API 密钥

是

PORT

不适用

否

HOST

不适用

否

在 Cursor 中使用

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

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

在 Claude Desktop 中使用

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

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

可用工具

此服务器提供以下工具:

download

Download mp3.

端点: GET /download/mp3

参数:

技术栈

  • 传输协议: stdio

  • HTTP 客户端: httpx

许可证

MIT License - 详见 LICENSE 文件。

开发

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

版本: 1.0.0

Available Tools

1 tool
downloadC

Download mp3.

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYesExample value: https://www.youtube.com/watch?v=phd1U2JIfUA

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. 'Download mp3' implies a read operation that retrieves data, but it doesn't disclose behavioral traits such as authentication needs, rate limits, file size limits, or what happens on failure. This is a significant gap for a tool with no annotation coverage.

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 extremely concise at two words, front-loaded with the essential action and resource. There is zero waste, making it efficient for quick understanding.

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 no annotations, no output schema, and a single parameter with full schema coverage, the description is incomplete. It fails to provide necessary context for a download operation, such as return format, error handling, or usage constraints, leaving significant gaps for an AI agent.

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%, with the parameter 'url' documented in the schema as a string with an example. The description adds no additional meaning beyond the schema, such as URL format requirements or supported sources, so it meets the baseline of 3 when the schema does the heavy lifting.

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

Purpose3/5

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

The description 'Download mp3' specifies the action (download) and resource type (mp3), which is clear but vague about scope and source. It doesn't differentiate from siblings since none exist, but lacks specificity about what exactly is being downloaded (e.g., from where, under what conditions).

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?

No guidance is provided on when to use this tool versus alternatives, prerequisites, or constraints. The description simply states what it does without context about appropriate scenarios or limitations.

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 observeddownload
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

C2.9/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is singular and clear.

Naming Consistency5/5

A single tool inherently has perfect naming consistency, as there are no other tools to compare it against for patterns or deviations.

Tool Count2/5

One tool is too few for a server named 'Youtube Mp310 MCP Server', which suggests functionality like searching, listing, or managing downloads beyond a single download action. This minimal set severely limits agent capabilities.

Completeness1/5

The tool surface is severely incomplete; it only provides download functionality without any supporting operations such as search, list, or metadata retrieval, which are essential for a YouTube MP3 domain.

Maintenance

ActivityInactive
ResponsivenessSyncing

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-mp310'

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