Skip to main content
Glama
BACH-AI-Tools

Ytstream Download Youtube Videos MCP Server

by BACH-AI-Tools
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Ytstream Download Youtube Videos MCP Server

English | 简体中文 | 繁體中文

用于访问 Ytstream Download Youtube Videos API 的 MCP 服务器。

🚀 使用 EMCP 平台快速体验

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

快速开始：

  1. 🌐 访问 EMCP 平台

  2. 📝 注册并登录账号

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

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

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

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

EMCP 平台优势：

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

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

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

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

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

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

Related MCP server: BACH YouTube API MCP Server

简介

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

  • PyPI 包名: bach-ytstream_download_youtube_videos

  • 版本: 1.0.0

  • 传输协议: stdio

安装

从 PyPI 安装:

pip install bach-ytstream_download_youtube_videos

从源码安装:

pip install -e .

运行

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

# 运行（uvx 会自动安装并运行）
uvx --from bach-ytstream_download_youtube_videos bach_ytstream_download_youtube_videos

# 或指定版本
uvx --from bach-ytstream_download_youtube_videos@latest bach_ytstream_download_youtube_videos

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

python server.py

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

# 安装
pip install bach-ytstream_download_youtube_videos

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

配置

API 认证

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

export API_KEY="your_api_key_here"

环境变量

变量名

说明

必需

API_KEY

API 密钥

是

PORT

不适用

否

HOST

不适用

否

在 Cursor 中使用

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

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

在 Claude Desktop 中使用

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

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

可用工具

此服务器提供以下工具:

downloadstream

Stream or download info.

端点: GET /dl

参数:

  • id (string) 必需: Youtube Video Id.

  • cgeo (string): Country code in ISO 3166 format of the end user. It is important to provide geo of the end user to get the best speed and direct links. Not providing cgeo may lead to extra quota cost in case of proxied link. If links are used in the server, then cgeo will be the geo of the server.

  • lang (string): Language code for audio results based on availability. Like en, ru, hi, etc

技术栈

  • 传输协议: stdio

  • HTTP 客户端: httpx

许可证

MIT License - 详见 LICENSE 文件。

开发

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

版本: 1.0.0

Available Tools

1 tool
downloadstreamC

Stream or download info.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesYoutube Video Id.
cgeoNoCountry code in ISO 3166 format of the end user. It is important to provide geo of the end user to get the best speed and direct links. Not providing cgeo may lead to extra quota cost in case of proxied link. If links are used in the server, then cgeo will be the geo of the server.
langNoLanguage code for audio results based on availability. Like en, ru, hi, etc

TDQS

C2/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 the full burden of behavioral disclosure. It vaguely mentions 'stream or download' but doesn't clarify if this is a read-only operation, what the output format is, whether it involves data transfer costs, or any rate limits. This leaves significant gaps for a tool that likely handles media streaming/downloading.

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

Conciseness2/5

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

The description is overly concise to the point of being under-specified—'Stream or download info' is a single vague phrase that doesn't earn its place by providing useful context. It lacks structure and fails to front-load critical information.

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 a streaming/download tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'info' is returned, how streaming vs. downloading is determined, or any behavioral traits, leaving the agent with insufficient guidance for proper use.

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 (id, cgeo, lang) thoroughly. The description adds no additional meaning beyond what the schema provides, such as explaining how parameters interact or affect behavior, meeting the baseline for high schema coverage.

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

Purpose2/5

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

The description 'Stream or download info' is vague and tautological—it essentially restates the tool name 'downloadstream' without specifying what resource it operates on. It mentions 'info' but doesn't clarify if this refers to metadata, video content, or something else, failing to provide a clear verb+resource combination.

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?

There are no usage guidelines in the description—it doesn't indicate when to use this tool, any prerequisites, or alternatives. With no sibling tools, this isn't a major issue, but the description offers no contextual guidance for the agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

C2.5/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The tool 'downloadstream' stands alone with a clear purpose, so disambiguation is perfect.

Naming Consistency5/5

A single tool inherently has consistent naming, as there are no other tools to compare it against. The name 'downloadstream' follows a clear verb_noun pattern, and no inconsistencies exist.

Tool Count2/5

A single tool is too few for a server focused on downloading YouTube videos, as this domain typically requires multiple operations (e.g., list videos, get metadata, choose formats, handle errors). One tool feels thin and limits functionality.

Completeness2/5

The tool surface is severely incomplete for downloading YouTube videos. It lacks essential operations such as searching for videos, retrieving metadata, selecting quality options, or managing downloads, which will likely cause agent failures in real-world use.

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-ytstream-download-youtube-videos'

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