Future Video Studio MCP server
online · 100% uptimevideo.future/future-video-studio·v0.1.8Create and manage cinematic AI video renders through the Future Video Studio Agent API.
0 stars
Reviews
Write oneNobody has reviewed Future Video Studio yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Future Video Studio tools (8, 3 write)
write = sends, deletes, buys or postsfvs_cancel_renderwrite actionFreeCancel a Future Video Studio render job. Provide either `project_id` or the full `cancel_url` returned by fvs_submit_render.
fvs_create_paid_render_quotewrite actionFreeCreate 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.
fvs_download_final_videoFreeDownload 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.
fvs_example_render_requestFreeReturn a minimal scene render request agents can adapt.
fvs_get_paid_render_statusFreeCheck 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_statusFreeCheck a Future Video Studio render job. Provide either `project_id` or the full `status_url` returned by fvs_submit_render.
fvs_open_chatgpt_appFreeOpen 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_renderwrite actionFreeSubmit 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.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan10 source files scanned25/25
- Live reliabilityremote reachable in 568ms20/20
- Tool poisoning8 tool descriptions checked15/15
- Auth qualityAPI key sent as a header8/15
- Maintenancelast push 108 days ago8/15
- Maintainer identitynamespace and repository owner differ; website matches verified namespace5/10
How Future Video Studio compares
Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 81/100
- higher than 63% of 4,460 AI and agents servers
- Tools
- 8
- the typical AI and agents server has 6
- Tools that change things
- 38%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote AI and agents server answers 100%
- Response time
- 203 ms
- faster than 65% of 2,331 AI and agents servers
What its tools let an agent do: 5 read · 3 change
Install Future Video Studio in Claude Code, Cursor or VS Code
claude mcp add --transport http future-video-studio https://mcp.future.video/mcp
What the publisher says
From the Future Video Studio repository's README, as published. We do not edit it. Read it on GitHub
Future Video Studio MCP
<!-- mcp-name: video.future/future-video-studio -->
Future Video Studio MCP lets agents create, monitor, cancel, and download cinematic AI video renders through the Future Video Studio Agent API.
The hosted MCP server is available at:
https://mcp.future.video/mcpThe same server can also run locally over stdio from this Python package.
The hosted service also serves the ChatGPT Apps domain verification endpoint at https://mcp.future.video/.well-known/openai-apps-challenge. Set OPENAIAPPSCHALLENGE_RESPONSE only if the submission dashboard requires an exact challenge body.
ChatGPT App
The hosted MCP server is also ready to connect as a ChatGPT App in developer mode:
Connector URL: https://mcp.future.video/mcp
App manifest: https://mcp.future.video/chatgpt-app.json
Widget URI: ui://future-video-studio/render-console-v1.htmlThe app exposes a small render console inside ChatGPT. It can prepare a render, submit account-wallet jobs, create no-account Link pay-per-render quotes, poll status, show payment links, and open the finished video when FVS returns a signed finalvideourl.
ChatGPT connector setup:
X-FVS-Billing-Mode: pay-per-render.
- Account mode: add X-FVS-Agent-Key as a secret connector header.
- Pay-per-render mode: leave X-FVS-Agent-Key unset, or set
the account-linking gateway.
- Marketplace-linked mode: use the signed X-FVS-Marketplace-* headers from
In ChatGPT, enable developer mode, create a connector, and use https://mcp.future.video/mcp as the connector URL. The tool metadata links the render tools to the FVS widget using the MCP Apps ui.resourceUri field and the ChatGPT openai/outputTemplate compatibility field.
A2A / Gemini Enterprise Preview
The hosted service also exposes a first A2A-compatible wrapper for the Google Cloud Marketplace / Gemini Enterprise Track 3 path:
https://mcp.future.video/.well-known/agent-card.json
https://mcp.future.video/message:send
https://mcp.future.video/tasks/{task_id}
https://mcp.future.video/tasks/{task_id}:cancelThe A2A layer uses the same X-FVS-Agent-Key account credential as the MCP server, marketplace-linked account headers, or paid quote mode. A message:send request can include either plain text brief parts or a structured fvsrenderrequest data part. Account and marketplace submissions create an FVS Agent API render and return an A2A task whose id is the FVS projectid. Paid quote submissions return HTTP 402 with an A2A task whose id is the quoteid; pay the returned Link/Stripe MPP paymenturl, then poll /tasks/{quoteid}?claim_token=....
The Agent Card advertises the Official MCP Registry name, video.future/future-video-studio, so enterprise agents can see both the A2A delegation surface and the hosted MCP tool surface.
Billing Paths
the owning Future Video Studio account wallet under the same credit model and saved pipeline defaults as the web app.
- Account mode: provide X-FVS-Agent-Key or FVSAGENTAPI_KEY. Renders charge
marketplace customer. Production deployments should also set X-FVS-Marketplace-Entitlement, X-FVS-Marketplace-Timestamp, and X-FVS-Marketplace-Signature from the account-linking gateway. The MCP server maps the marketplace account to a stored FVS Agent API key and charges the linked wallet.
- Marketplace-linked mode: provide X-FVS-Marketplace-Account for a linked
X-FVS-Billing-Mode: pay-per-render. The server returns a Link/Stripe MPP payment quote, then exposes a claim-token status URL so the agent can retrieve the result.
- Pay-per-render mode: omit account credentials or set
Agents should get explicit user approval before submitting wallet-backed account renders.
Security Configuration
Marketplace account mapping is configured with environment variables on the MCP deployment:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Future Video Studio: common questions
- Is Future Video Studio MCP server safe?
- Mostly: it is graded B (81/100). Read the Future Video Studio safety report
- How do I install Future Video Studio?
- It runs remotely at mcp.future.video. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Future Video Studio need an API key?
- Yes. The registry entry asks for
X-FVS-Agent-Key,X-FVS-Marketplace-Signature. - Is Future Video Studio maintained?
- The last commit was 146 days ago (2026-06-11). The latest release is v0.1.8.
- Is Future Video Studio up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- What can I use instead of Future Video Studio?
- Servers from other publishers that do the same job: Guaardvark MCP server, Claude Real Video MCP server and Agent-Native Assets MCP server.
- How does Future Video Studio compare with other AI and agents MCP servers?
- safety score 81/100 (higher than 63% of 4,460 AI and agents servers); tools 8 (the typical AI and agents server has 6); tools that change things 38% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Future Video Studio
Same job from other publishers: the closest match first, then the best rated.
GuaardvarkLocal AI studio on your GPU: images, video, music, voice, RAG. Needs the Guaardvark app installed.not reviewedEstablishedB- Claude Real VideoLet any LLM watch a video locally — and search everything it has ever watched.not reviewedEstablishedA
- Agent-Native AssetsDigital asset manager - upload, organize, search, and generate on-brand images and videosnot reviewedEstablishedA
- Watch SkillWatch video and live sessions, keep timestamped evidence, and verify an agent's own work.not reviewedEstablishedB
- WaveSpeedRun any model on the live WaveSpeed catalog: image, video, audio, 3D.not reviewedEstablishedA