mcp server
Future Video Studio
Create and manage cinematic AI video renders through the Future Video Studio Agent API.
Description as published by the maintainer. Source
- version 0.1.8
- active
active — Registry entry last updated 2026-06-11.
What this server can do
8 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
fvs_cancel_render(cancel_url, project_id)- Cancel a Future Video Studio render job. Provide either `project_id` or the full `cancel_url` returned by fvs_submit_render.
fvs_create_paid_render_quote(request, upload_urls)- Create a no-account Link payment quote for an FVS render. The backend returns HTTP 402 payment details as data: `payment_url`, `status_url`, `claim_token`, `amount_cents`, `currency`, and a raw `www_authenticate` challenge. Pay `payment_url` with Link's MPP flow, then poll with fvs_get_paid_render_status. Local file uploads are not available in paid quote mode; use public HTTPS `upload_urls` when assets are needed. Required: request.
fvs_download_final_video(overwrite, output_path, final_video_url)- Download a completed Future Video Studio final render URL to a local file. Use this only after fvs_get_render_status or fvs_get_paid_render_status returns a final_video_url for a completed render. The tool performs an unauthenticated HTTPS GET to that signed URL and writes the response bytes to output_path on the MCP server's local filesystem. It does not call the FVS Agent API, spend wallet credits, require FVS_AGENT_API_KEY, cancel jobs, or modify remote render state. Side effects and constraints: output_path is a local filesystem path for the MCP server process, parent directories are created, existing files are not replaced unless overwrite is true, and large videos may take minutes to download. The request timeout is 600 seconds. Use a fresh status check to refresh expired signed URLs, and do not pass arbitrary or untrusted URLs. Required: final_video_url, output_path.
fvs_example_render_request- Return a minimal scene render request agents can adapt.
fvs_get_paid_render_status(quote_id, status_url, claim_token)- Check a no-account paid render created with fvs_create_paid_render_quote. Provide the full `status_url` or pass both `quote_id` and `claim_token`.
fvs_get_render_status(project_id, status_url)- Check a Future Video Studio render job. Provide either `project_id` or the full `status_url` returned by fvs_submit_render.
fvs_open_chatgpt_app(quote_id, project_id, status_url, claim_token, final_video_url)- Open the Future Video Studio ChatGPT app widget without creating a render. Use this when the user wants the FVS app panel, wants to paste a status URL, or wants to prepare a render interactively before spending credits.
fvs_submit_render(request, upload_urls, poll_until_complete)- Submit a Future Video Studio render job through the FVS Agent API. Pass the render payload in the required `request` object. For reference assets, pass public HTTPS URLs in `upload_urls`; every `request.assets[].filename` must match one uploaded URL basename or explicit upload URL filename. Credentials come from the connector header, marketplace account mapping, or FVS_AGENT_API_KEY in the MCP server environment. Required: request.
Last successful function declaration observed on . Source: https://mcp.future.video/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://mcp.future.video/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 0.1.8 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-06-11 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-06-11 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 8 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | mcp.future.video | |
| mcp endpoint status | ok | The server listed 8 functions when asked. | as of probe | mcp.future.video |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json