Local file output
Codex can save returned media to a local directory when the user asks for a download.
Codex video download tool
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.
The installer wires a local CLI and MCP server so the video parsing workflow lives inside the same agent session.
Codex can save returned media to a local directory when the user asks for a download.
Codex can return platform, title, author, media URLs, warnings and quota without saving files.
Codex can check the signed-in account's daily parse quota before a batch workflow.
Use this as the first public demo because it proves the product in less than a minute.
fast-download auth login and finish Google OAuth in the browser.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"]
Stated plainly, because a tool that hides its edges is a tool you cannot build on.
| Capability | Status | Notes |
|---|---|---|
| Codex CLI | Supported | Config written to ~/.codex/config.toml |
| Codex IDE extension | Supported | Same config file, same server |
| Install method | One command | curl -fsSL https://fastdown.pro/cli | sh |
| Auth | Google OAuth | Interactive once, then reused headlessly |
| Tools exposed | 3 | download_video, parse_video, quota |
| Sandboxed Codex runs | Needs network | The server calls the Fastdown API over HTTPS |
Skip this section if you only ever want the terminal.
[mcp_servers.fast-download]
command = "fast-download"
args = ["mcp", "--stdio"]
Four constraints that make the tool safe to put inside an automated workflow.
fast-download uninstall --agent codex removes the config block and the binary.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.
Yes. Codex calls download_video with the public share link and receives a local path it can then read, transcribe or move.
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.
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.
What the loop looks like once the MCP server is wired.
download_video once per link.quota and stop early rather than burning through the daily allowance mid-task.