Skip to main content
Glama
BACH-AI-Tools

Envato Downloader API1

by BACH-AI-Tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Envato Downloader Api1 MCP Server

English | 简体中文 | 繁體中文

用于访问 Envato Downloader Api1 API 的 MCP 服务器。

🚀 使用 EMCP 平台快速体验

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

快速开始：

  1. 🌐 访问 EMCP 平台

  2. 📝 注册并登录账号

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

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

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

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

EMCP 平台优势：

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

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

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

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

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

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

Related MCP server: Youtube Mp310 MCP Server

简介

这是一个 MCP 服务器，用于访问 Envato Downloader Api1 API。

  • PyPI 包名: bach-envato_downloader_api1

  • 版本: 1.0.0

  • 传输协议: stdio

安装

从 PyPI 安装:

pip install bach-envato_downloader_api1

从源码安装:

pip install -e .

运行

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

# 运行（uvx 会自动安装并运行）
uvx --from bach-envato_downloader_api1 bach_envato_downloader_api1

# 或指定版本
uvx --from bach-envato_downloader_api1@latest bach_envato_downloader_api1

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

python server.py

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

# 安装
pip install bach-envato_downloader_api1

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

配置

API 认证

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

export API_KEY="your_api_key_here"

环境变量

变量名

说明

必需

API_KEY

API 密钥

是

PORT

不适用

否

HOST

不适用

否

在 Cursor 中使用

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

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

在 Claude Desktop 中使用

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

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

可用工具

此服务器提供以下工具:

download_files

test

端点: POST /external-api/envato

参数:

技术栈

  • 传输协议: stdio

  • HTTP 客户端: httpx

许可证

MIT License - 详见 LICENSE 文件。

开发

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

版本: 1.0.0

Available Tools

1 tool
download_filesD

test

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYesExample value: https://elements.envato.com/stamp-in-retro-style-on-paper-mockup-template-92H7DVA

TDQS

D1.4/5.0
Behavior1/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. The single word 'test' reveals nothing about whether this is a read/write operation, what permissions are needed, whether it's destructive, rate limits, or any behavioral traits. This is completely inadequate for a tool that presumably downloads files.

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?

While the description is extremely brief, this is not true conciseness but severe under-specification. A single word 'test' fails to convey necessary information, making it inefficient rather than appropriately sized. Every sentence should earn its place, but here there's essentially no content to evaluate.

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?

Given that this is a tool with 1 parameter, no annotations, and no output schema, the description 'test' is completely inadequate. It doesn't explain what the tool does, how to use it, what it returns, or any behavioral context. For a file download tool, this leaves critical gaps in understanding.

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?

The input schema has 1 parameter with 100% description coverage, providing a clear example URL. The description 'test' adds no semantic value beyond what the schema already documents. According to the rules, when schema_description_coverage is high (>80%), the baseline score is 3 even with no parameter information in the 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?

The description 'test' is a tautology that merely restates the tool name 'download_files' without providing any meaningful information about what the tool does. It fails to specify what resource is being downloaded, from where, or what the outcome is. This is the lowest possible score for purpose clarity.

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?

The description provides no guidance on when to use this tool, what context it applies to, or any prerequisites. There are no sibling tools mentioned, but even without alternatives, the description offers zero usage instructions. This is a complete lack of guidance.

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

C2/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools, as there are no other tools to compare it against. The single tool's purpose is inherently distinct by default.

Naming Consistency5/5

Since there is only one tool, naming consistency is trivially perfect; there are no other tool names to be inconsistent with. The tool name 'download_files' follows a clear verb_noun pattern.

Tool Count2/5

A single tool is generally too few for a server named 'Envato Downloader API1', which suggests a domain involving file downloads from Envato. This likely requires more operations (e.g., list files, check status, manage downloads) to be useful, making the scope feel incomplete and thin.

Completeness2/5

The tool set is severely incomplete for the implied domain. With only a download tool, there are obvious gaps such as listing available files, checking download status, or handling errors, which are essential for a functional downloader API and will likely cause agent failures.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers