EasyDown for AI agents

Video Downloader MCP Server

Connect Claude Code, Cursor, MCP Inspector, or another Streamable HTTP client to one authenticated tool for public media links across 11 supported platforms.

Live Streamable HTTP endpointhttps://api.easydown.org/mcp

Connect the MCP server

Use the same private EasyDown API token for REST and MCP. Keep the token in your client configuration and never place it in public browser code.

{
  "mcpServers": {
    "easydown": {
      "url": "https://api.easydown.org/mcp",
      "headers": {
        "Authorization": "Bearer ed_live_xxx"
      }
    }
  }
}

Replace ed_live_xxx with an API token created in your EasyDown account.

Platform downloader MCP pages

Every platform page documents the exact public URL formats, media behavior, example request, and known limits for that source.

One tool, one response shape

The server exposes only parse_media_url. It detects the platform from the URL and preserves every media candidate returned by the existing EasyDown parser.

Input

parse_media_url({
  "url": "https://www.youtube.com/watch?v=..."
})

Structured output

{
  "status": 200,
  "data": { "images": [], "videos": [], "audios": [] },
  "billing": { "creditsCharged": 1, "creditsRemaining": 99 }
}

Success-only credits

A successful call with at least one image, video, or audio URL costs 1 credit. Unsupported URLs, upstream failures, authentication errors, and empty media results do not charge credits.

Public single-post media

The MCP server is designed for supported public single posts. Profiles, search pages, feeds, collections, private content, deleted content, and unsupported live pages remain outside the product scope.

MCP server FAQ

What does the EasyDown MCP server return?

parse_media_url returns the existing EasyDown media schema: platform, title, thumbnail, duration, images, videos, audios, message, and billing data. Media candidate arrays are not truncated by the MCP layer.

How do I authenticate the video downloader MCP server?

Create an ed_live API token in the EasyDown dashboard and send it as Authorization: Bearer ed_live_xxx on every Streamable HTTP request.

Does connecting or listing MCP tools consume credits?

No. Initialization and tools/list do not charge credits. Only a successful parse_media_url result with downloadable media costs 1 credit.

Does EasyDown store downloaded files?

No. The MCP server returns source media URLs and metadata. Those URLs may expire or require source-specific request headers, cookies, or regional access.