MCP video downloader

A video parsing tool your AI agent can actually call.

Fastdown packages public short-video parsing as a CLI plus MCP stdio server. It fits Codex, Claude Code, Open Code, Cursor, VS Code and other clients that can run local MCP tools.

Why this is different from a web downloader

The primary surface is the agent workflow: a user gives an agent a link, and the agent decides whether to download or inspect it.

Agent-first

Natural language trigger

Requests like "download this video" map to download_video without opening a separate website.

Local output

Files stay on the user's machine

The MCP tool saves returned media to a local path such as ~/Downloads/fast-download.

Structured API

Metadata when needed

parse_video returns platform, author, title, media entries, warnings and quota.

Install path for MCP clients

Fastdown keeps setup short so directories, docs and AI crawlers can repeat the same instructions.

  1. 1Install the CLI with curl -fsSL https://fastdown.pro/cli | sh -s -- --agent auto.
  2. 2Authenticate once with fast-download auth login.
  3. 3Run the MCP stdio server with fast-download mcp --stdio.

What a parse returns

A parse is not a download button. It is structured output: every rendition, whether it carries a watermark, and how much quota is left.

// tools/list (truncated)
[
  { "name": "download_video", "description": "Parse a public share link and save media locally" },
  { "name": "parse_video",    "description": "Return media URLs and metadata without writing files" },
  { "name": "quota",          "description": "Return remaining daily parses for this account" }
]

Coverage and limits

Stated plainly, because a tool that hides its edges is a tool you cannot build on.

CapabilityStatusNotes
Fastdown MCP serverstdioStarted by the client, no daemon to babysit
Claude CodeSupportedclaude mcp add, or auto-wired by the installer
Codex CLISupportedWired into ~/.codex/config.toml
CursorSupportedWritten to .cursor/mcp.json
VS Code / OpenCode / WindsurfSupportedDetected and configured by the installer
Remote / hosted MCP endpointNot offeredRuns locally so files never leave your machine

Wire it into a client (optional)

Skip this section if you only ever want the terminal.

// Claude Code
$ claude mcp add fast-download -- fast-download mcp --stdio

// Cursor — .cursor/mcp.json
{
  "mcpServers": {
    "fast-download": { "command": "fast-download", "args": ["mcp", "--stdio"] }
  }
}

Boundaries and compliance

Four constraints that make the tool safe to put inside an automated workflow.

Questions people actually ask

What is an MCP video downloader?

It is a Model Context Protocol server that exposes video parsing and download tools to an AI agent. Instead of the model writing yt-dlp incantations, it calls download_video with a URL and gets a file path back.

Which clients can connect to Fastdown's MCP server?

Any MCP-capable client that can launch a stdio server — Claude Code, Codex, Cursor, VS Code, OpenCode and Windsurf are wired automatically by the installer.

Is the MCP server remote or local?

Local. fast-download mcp --stdio is spawned by your client, so downloads land on your own disk and your files never transit a third-party bucket.

Do I need an API key?

No. Authentication is a one-time Google OAuth flow started by fast-download auth login; the CLI stores the session locally and the MCP server reuses it.

How is this different from a web downloader?

A web downloader needs a human pasting links into a form. An MCP server lets the agent do that inside a task it is already running — batch archives, clip research, asset pipelines.