Codex video download tool

Install Fastdown from a Codex session.

Fastdown is designed for agent-first setup: paste the install prompt into Codex, authenticate once, then let Codex call MCP tools for public short-video links.

What Codex gets after setup

The installer wires a local CLI and MCP server so the video parsing workflow lives inside the same agent session.

download_video

Local file output

Codex can save returned media to a local directory when the user asks for a download.

parse_video

Structured inspection

Codex can return platform, title, author, media URLs, warnings and quota without saving files.

quota

Usage visibility

Codex can check the signed-in account's daily parse quota before a batch workflow.

Demo script

Use this as the first public demo because it proves the product in less than a minute.

  1. 1Open Codex in a workspace and paste the Fastdown setup prompt.
  2. 2Run fast-download auth login and finish Google OAuth in the browser.
  3. 3Paste a public short-video link and ask Codex to download it locally.

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.

# ~/.codex/config.toml (written by the installer)
[mcp_servers.fast-download]
command = "fast-download"
args = ["mcp", "--stdio"]

Coverage and limits

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

CapabilityStatusNotes
Codex CLISupportedConfig written to ~/.codex/config.toml
Codex IDE extensionSupportedSame config file, same server
Install methodOne commandcurl -fsSL https://fastdown.pro/cli | sh
AuthGoogle OAuthInteractive once, then reused headlessly
Tools exposed3download_video, parse_video, quota
Sandboxed Codex runsNeeds networkThe server calls the Fastdown API over HTTPS

Wire it into a client (optional)

Skip this section if you only ever want the terminal.

[mcp_servers.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

How do I add an MCP server to Codex?

Either paste the Fastdown setup prompt into a Codex session and approve the command, or add a [mcp_servers.fast-download] block to ~/.codex/config.toml manually.

Can Codex download a TikTok video during a task?

Yes. Codex calls download_video with the public share link and receives a local path it can then read, transcribe or move.

What happens if the Codex sandbox has no network?

The parse fails with a network error. The MCP server is a thin client over HTTPS, so the sandbox has to allow outbound requests to fastdown.pro.

Does this replace yt-dlp in a Codex workflow?

Only for the platforms it covers, and only when you want structured output instead of a shell invocation. yt-dlp remains the better answer for arbitrary sites and for bulk channel archiving.

A realistic Codex session

What the loop looks like once the MCP server is wired.

  1. 1You describe the outcome — “Take these three Douyin links and put the videos in ./assets.” Codex decides to call download_video once per link.
  2. 2Codex checks the quota — Before a long batch it can call quota and stop early rather than burning through the daily allowance mid-task.
  3. 3Failures surface as errors — A refused link returns a typed error, so Codex can skip it and continue instead of silently producing an empty file.