Skip to content
External endpointresponds

Future Video Studio

Create and manage cinematic AI video renders through the Future Video Studio Agent API.

Endpoint URL
https://mcp.future.video/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:03 AM UTC
Check
MCP initialize · 8s limit
Latency
208 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
video.future/future-video-studio

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
future-video-studio
Version
0.1.8
Capability keys
experimental, prompts, resources, tools
Tool names
fvs_open_chatgpt_app, fvs_submit_render, fvs_create_paid_render_quote, fvs_get_render_status, fvs_get_paid_render_status, fvs_cancel_render, fvs_download_final_video, fvs_example_render_request
Instructions excerpt

Create videos through the Future Video Studio Agent API. In ChatGPT, this MCP server also exposes a Future Video Studio app widget for submitting, paying for, polling, and opening renders directly inside the conversation. Use fvs_submit_render for account API-key projects, fvs_create_paid_render_quote for no-account Link payment quotes, fvs_get_render_status or fvs_get_paid_render_status to poll, fvs_cancel_render to stop account-owned runs, and fvs_download_final_video to save a finished signed final_video_url. Prefer FVS_AGENT_API_KEY and FVS_AGENT_BASE_URL from the MCP server environment when the user has an FVS account. Agent API keys are owned by normal FVS user accounts and use the same pricing, wallet, and saved pipeline defaults as the web app. Marketplace-linked calls map a signed marketplace account to an FVS Agent API key. Paid quotes use the same credit estimate and return a claim token so the result can be retrieved without an FVS account.

Reported Aug 17, 2026, 05:03 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 402ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 629ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 119ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 208ms