Integration
Video Download MCP for Codex
Codex reads MCP servers from its config file. The stdio package is the most portable option because it works in every Codex build; the remote HTTP form is shorter when your build supports it.
stdio config
[mcp_servers.videodownload]
command = "npx"
args = ["-y", "@videodownload/mcp"]
env = { VIDEODOWNLOAD_API_KEY = "vd_your_key" }Add to ~/.codex/config.toml. The process proxies calls to the hosted API.
remote config
[mcp_servers.videodownload]
url = "https://videodownloadmcp.com/mcp"
http_headers = { Authorization = "Bearer vd_your_key" }Use this only if your Codex version supports remote MCP servers.
Steps
- 01Create a vd_ key.
- 02Add one of the config blocks to ~/.codex/config.toml.
- 03Restart Codex and ask it to list the available MCP tools.
- 04Ask for a resolve on a public URL, then a download.
Limits that still apply
- The stdio package requires Node 20 or newer.
- Both forms call the same six tools and charge the same credits.
FAQ
Does Codex need ffmpeg?+
No. The hosted worker runs ffmpeg for merges and MP3 conversion.
Why did the stdio process exit immediately?+
VIDEODOWNLOAD_API_KEY was not set in the server env block. Codex launches the process with only the env you declare.