Future Video Studio MCP server

• Registry namevideo.future/future-video-studioverified in the MCP registry

The registry name sits under future.video. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-21
• Tools8
• Server calls itselffuture-video-studio
• Server version0.1.8
• Protocol version2025-06-18

On 2026-10-21 the server answered initialize and tools/list without a sign-in. First answer in 192 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 6 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 6 so far
• Use22 PyPI downloads a week
• Answeredmeasuring6 of the 7 daily checks it takes to print a share
• Median first answer171 ms
• Space in an agent's context≈ 3,283 tokensthe definitions of all its tools (8), which an agent carries on every turn
• Tool definitionsA · 90 of 100
• Typed results8 of 8 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 5 of 8

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• fvs_open_chatgpt_app

  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

  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…

• fvs_create_paid_render_quote

  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…

• fvs_get_render_status

  Check a Future Video Studio render job. Provide either `project_id` or the full `status_url` returned by fvs_submit_render.

• fvs_get_paid_render_status

  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_cancel_render

  Cancel a Future Video Studio render job. Provide either `project_id` or the full `cancel_url` returned by fvs_submit_render.

• fvs_download_final_video

  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…

• fvs_example_render_request

  Return a minimal scene render request agents can adapt.