Skip to main content
Glama

avc-test-js-mcp (Node.js)

npm version Node.js >=18 License: MIT

Video enhancement service based on the MCP protocol, acting as an MCP Client-Server to interact with a FastAPI HTTP Server.

Features

Provides the following MCP Tools:

  • create_task - Create a video enhancement task (supports URL or local file upload)

  • get_task_status - Query task status

  • enhance_video_sync - Synchronously enhance video (blocking wait)

Related MCP server: avc-test-py-mcp

Installation

npm install -g avc-test-js-mcp

Or use yarn/pnpm:

yarn global add avc-test-js-mcp
pnpm add -g avc-test-js-mcp

Install from source

git clone https://github.com/yourusername/avc-test-js-mcp.git
cd js_client
npm install
npm run build

Usage

1. Command Line Startup

Use directly after global installation:

avc-test-js-mcp --base-url https://mcp.luluhero.com --api-key your-api-key

Or use environment variables:

# Windows PowerShell
$env:HTTP_API_BASE_URL="https://mcp.luluhero.com"
$env:HTTP_API_KEY="your-api-key"
avc-test-js-mcp

# Windows CMD
set HTTP_API_BASE_URL=https://mcp.luluhero.com
set HTTP_API_KEY=your-api-key
avc-test-js-mcp

# macOS/Linux
export HTTP_API_BASE_URL=https://mcp.luluhero.com
export HTTP_API_KEY=your-api-key
avc-test-js-mcp

2. Configure in Claude Desktop

Edit the Claude Desktop configuration file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "video-enhancement": {
      "command": "avc-test-js-mcp",
      "args": [
        "--base-url",
        "https://mcp.luluhero.com",
        "--api-key",
        "your-api-key"
      ]
    }
  }
}

3. Use npx (No global installation required)

npx avc-test-js-mcp --base-url https://mcp.luluhero.com --api-key your-api-key

Claude Desktop configuration:

{
  "mcpServers": {
    "video-enhancement": {
      "command": "npx",
      "args": [
        "avc-test-js-mcp",
        "--base-url",
        "https://mcp.luluhero.com",
        "--api-key",
        "your-api-key"
      ]
    }
  }
}

Provided Tools

create_task

Create a video enhancement task (asynchronous).

Parameters:

  • video_source (string, required): Video URL or local file path

  • type (string, optional): Upload type, default "url"

    • Available values: "url" - Web video URL, "local" - Local file path

  • resolution (string, optional): Target resolution, default 720p

    • Available values: 480p, 540p, 720p, 1080p, 2k

Usage Example:

// URL 方式
{
  "video_source": "https://example.com/video.mp4",
  "type": "url",
  "resolution": "1080p"
}

// 本地文件方式
{
  "video_source": "/path/to/local/video.mp4",
  "type": "local",
  "resolution": "1080p"
}

Return Value:

{
  "success": true,
  "task_id": "xxx",
  "status": "wait"
}

get_task_status

Query task status.

Parameters:

  • task_id (string, required): Task ID

Usage Example:

{
  "task_id": "task-123-abc"
}

Return Value:

{
  "success": true,
  "task_id": "xxx",
  "status": "completed",
  "progress": 100,
  "video_url": "https://...",
  "error_message": null,
  "created_at": "2024-01-01T00:00:00Z",
  "updated_at": "2024-01-01T00:01:00Z"
}

enhance_video_sync

Synchronously enhance video (blocking wait for completion).

Parameters:

  • video_source (string, required): Video URL or local file path

  • type (string, optional): Upload type, default "url"

    • Available values: "url" - Web video URL, "local" - Local file path

  • resolution (string, optional): Target resolution, default 720p

  • poll_interval (number, optional): Polling interval (seconds), default 5

  • timeout (number, optional): Timeout (seconds), default 600

Usage Example:

{
  "video_source": "https://example.com/video.mp4",
  "type": "url",
  "resolution": "1080p",
  "poll_interval": 5,
  "timeout": 600
}

Return Value:

{
  "success": true,
  "task_id": "xxx",
  "status": "completed",
  "progress": 100,
  "video_url": "https://..."
}

File Upload Instructions

When type is set to "local", the MCP Server will:

  1. Read the local file

  2. Convert the file to base64 encoding

  3. Upload to the video enhancement service

Limitations:

  • Maximum file size: 100MB

Environment Variables

Variable Name

Description

Default Value

HTTP_API_BASE_URL

FastAPI HTTP Server address

https://mcp.luluhero.com

HTTP_API_KEY

API authentication key

None

Development

# 克隆仓库
git clone https://github.com/yourusername/avc-test-js-mcp.git
cd js_client

# 安装依赖
npm install

# 开发模式(自动编译)
npm run dev

# 构建
npm run build

License

MIT License - See LICENSE file for details

Available Tools

3 tools
create_taskA

创建视频增强任务(异步)

支持两种上传方式:

  1. URL 上传:提供视频 URL

  2. 本地上传:提供本地文件路径,MCP Server 自动读取并转为 base64

参数说明:

  • video_source: 视频 URL 或本地文件路径

  • type: "url" 或 "local"

  • resolution: 目标分辨率

Inputs: video_source (required), type, resolution.

enhance_video_syncB

同步增强视频(阻塞等待完成)

支持两种上传方式:

  1. URL 上传:提供视频 URL

  2. 本地上传:提供本地文件路径,MCP Server 自动读取并转为 base64

参数说明:

  • video_source: 视频 URL 或本地文件路径

  • type: "url" 或 "local"

  • resolution: 目标分辨率

  • poll_interval: 轮询间隔(秒)

  • timeout: 超时时间(秒)

Inputs: video_source (required), type, resolution, poll_interval, +1 more.

get_task_statusA

查询视频增强任务状态

Inputs: task_id (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.7/5.0

    Scored across 3 tools

    Disambiguation1/5

    The tool descriptions are extremely confusing and overlapping. The 'create_task' tool appears to be described twice with different parameter sets (first mentioning 'enhance_video_sync', then mentioning 'poll_interval', 'timeout', and 'get_task_status'), making it unclear if these are separate tools or one poorly described tool. There's no clear distinction between what each tool does, and the descriptions suggest they might all be part of the same functionality.

    Naming Consistency1/5

    Only one tool name 'create_task' is provided, but the description suggests multiple tools or functionalities. The naming is chaotic with no discernible pattern, and the description mixes parameter names with what appear to be additional tool names ('get_task_status'), creating complete inconsistency.

    Tool Count2/5

    The server claims 3 tools but only lists one tool name ('create_task'). The description is so poorly structured that it's impossible to determine what the actual tools are. For a video enhancement server, 3 tools could be appropriate, but the actual implementation appears to be a single tool with confusing documentation.

    Completeness2/5

    For a video enhancement server, we would expect tools for creating tasks, checking status, and retrieving results. The description suggests some of these functionalities exist but they're all muddled together in one tool description. There's no clear separation of operations, making the surface appear severely incomplete despite potentially having the necessary functionality buried in the confusing documentation.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers