Future Video Studio

video.futurePublished by future.videoOfficial publisherv0.1.8Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableMedia & DesignAI & ML

Overview

AI-generated overview

Future Video Studio MCP lets an assistant submit, monitor, cancel and download cinematic AI video renders through the FVS Agent API.

What you can do
  • Submit render jobs with a request payload and optional public HTTPS reference assets
  • Create no-account Link payment quotes and poll paid renders with a claim token
  • Check render status by project ID or status URL, and cancel jobs
  • Download a completed render from its signed URL to a local file
  • Open the ChatGPT app widget and fetch an example render request
When to use it
Use it when you want an assistant to produce AI-generated cinematic video from a brief, track or cancel those renders, and save the finished file locally, either on a paid FVS account or per-render payment.
Requirements
Runs as a hosted remote endpoint or as a local Python package over stdio. Account mode needs an FVS Agent API key, sent as the X-FVS-Agent-Key header or the FVS_AGENT_API_KEY environment variable. Marketplace mode needs the X-FVS-Marketplace-* headers. Pay-per-render mode needs no key. Network access to the FVS service and to signed download URLs.
Before you install
Renders spend real money: account mode charges the FVS wallet credits, and pay-per-render mode requires paying a Link/Stripe quote. The README advises getting explicit user approval before wallet-backed renders. The agent key and marketplace signature are secrets. The download tool writes files to the server's filesystem and can overwrite an existing file when overwrite is true; only pass signed URLs returned by a completed render.

Installation

In SourceWeft

  1. Open Future Video Studio in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/video.future%2Ffuture-video-studio/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "future-video-studio": {
      "type": "http",
      "url": "https://mcp.future.video/mcp"
    }
  }
}

README

Future Video Studio MCP

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:

text
https://mcp.future.video/mcp

The 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 OPENAI_APPS_CHALLENGE_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:

text
Connector URL: https://mcp.future.video/mcpApp manifest:  https://mcp.future.video/chatgpt-app.jsonWidget URI:    ui://future-video-studio/render-console-v1.html

The 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 final_video_url.

ChatGPT connector setup:

  • Account mode: add X-FVS-Agent-Key as a secret connector header.
  • Pay-per-render mode: leave X-FVS-Agent-Key unset, or set X-FVS-Billing-Mode: pay-per-render.
  • Marketplace-linked mode: use the signed X-FVS-Marketplace-* headers from the account-linking gateway.

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:

text
https://mcp.future.video/.well-known/agent-card.jsonhttps://mcp.future.video/message:sendhttps://mcp.future.video/tasks/{task_id}https://mcp.future.video/tasks/{task_id}:cancel

The 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 fvs_render_request data part. Account and marketplace submissions create an FVS Agent API render and return an A2A task whose id is the FVS project_id. Paid quote submissions return HTTP 402 with an A2A task whose id is the quote_id; pay the returned Link/Stripe MPP payment_url, then poll /tasks/{quote_id}?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

  • Account mode: provide X-FVS-Agent-Key or FVS_AGENT_API_KEY. Renders charge the owning Future Video Studio account wallet under the same credit model and saved pipeline defaults as the web app.
  • Marketplace-linked mode: provide X-FVS-Marketplace-Account for a linked 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.
  • Pay-per-render mode: omit account credentials or set 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.

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:

powershell
$env:FVS_MARKETPLACE_MODE = "optional"$env:FVS_MARKETPLACE_SHARED_SECRET = "replace-with-random-secret"$env:FVS_MARKETPLACE_REQUIRE_SIGNATURE = "true"$env:FVS_MARKETPLACE_ACCOUNT_KEYS_JSON = '{"acct_google_123":{"api_key":"fvs_live_replace_me","entitlement_id":"ent_123","plan":"starter","status":"active"}}'

The marketplace signature is HMAC-SHA256 over:

text
{unix_timestamp}.{marketplace_account_id}.{marketplace_entitlement_id}

Send it as X-FVS-Marketplace-Signature: sha256=<hex>. The default timestamp window is 300 seconds and can be adjusted with FVS_MARKETPLACE_SIGNATURE_MAX_SKEW_SECONDS.

For Cloud Run production deploys, pass FVS_MARKETPLACE_SHARED_SECRET_SECRET and FVS_MARKETPLACE_ACCOUNT_KEYS_JSON_SECRET to scripts/deploy_mcp_cloud.ps1 so the HMAC secret and account-key mapping come from Secret Manager instead of plain environment variables.

Tools

  • fvs_submit_render: submit a render request, optionally with public asset URLs
  • fvs_create_paid_render_quote: create a no-account Link payment quote
  • fvs_get_render_status: check a render by project_id or status_url
  • fvs_get_paid_render_status: check a paid render by status_url or quote_id plus claim_token
  • fvs_cancel_render: cancel a render by project_id or cancel_url
  • fvs_download_final_video: save a completed render from its signed URL
  • fvs_example_render_request: return an example scene render payload
  • fvs_open_chatgpt_app: open the ChatGPT app widget without creating a render

Downloading Final Renders

Use fvs_download_final_video only after fvs_get_render_status or fvs_get_paid_render_status returns a final_video_url for a completed render. If a signed URL has expired, call the relevant status tool again to refresh it.

The download tool:

  • performs an unauthenticated HTTPS GET to the signed final_video_url
  • writes the video bytes to output_path on the MCP server's local filesystem
  • creates missing parent directories
  • refuses to replace an existing file unless overwrite is true
  • does not require FVS_AGENT_API_KEY
  • does not spend wallet credits, create renders, cancel jobs, or modify remote state
  • may take minutes for large videos and uses a 600 second request timeout

Parameters:

  • final_video_url: an absolute HTTPS signed URL returned by a completed render status response. Do not pass arbitrary or untrusted URLs.
  • output_path: a local path visible to the MCP server process, such as C:/Users/me/Videos/fvs-result.mp4 or /tmp/fvs-result.mp4.
  • overwrite: defaults to false; set it to true only when replacing the destination file is intended.

Remote MCP Config

Account mode:

json
{  "mcpServers": {    "future-video-studio": {      "url": "https://mcp.future.video/mcp",      "headers": {        "X-FVS-Agent-Key": "fvs_live_replace_me"      }    }  }}

Pay-per-render mode:

json
{  "mcpServers": {    "future-video-studio": {      "url": "https://mcp.future.video/mcp"    }  }}

Marketplace-linked mode:

json
{  "mcpServers": {    "future-video-studio": {      "url": "https://mcp.future.video/mcp",      "headers": {        "X-FVS-Billing-Mode": "marketplace-linked-account",        "X-FVS-Marketplace-Account": "acct_google_123",        "X-FVS-Marketplace-Entitlement": "ent_123",        "X-FVS-Marketplace-Timestamp": "<unix_timestamp>",        "X-FVS-Marketplace-Signature": "sha256=<hmac>"      }    }  }}

Local Install

powershell
python -m pip install future-video-studio-mcppython -m fvs_mcp_server

Example local stdio MCP config:

json
{  "mcpServers": {    "future-video-studio": {      "command": "python",      "args": ["-m", "fvs_mcp_server"],      "env": {        "FVS_AGENT_API_KEY": "fvs_live_replace_me",        "FVS_AGENT_BASE_URL": "https://app.future.video"      }    }  }}

FVS_AGENT_API_KEY is optional. Leave it unset to use paid quote mode. FVS_AGENT_BASE_URL defaults to https://app.future.video.

Local Development

powershell
python -m pip install -e ".[dev]"python -m pytestpython -m fvs_mcp_server

Run the HTTP transport locally:

powershell
$env:FVS_MCP_TRANSPORT = "streamable-http"python -m fvs_mcp_server

Publishing

Build and check the package:

powershell
python -m buildpython -m twine check dist/*

This package is intended to publish to PyPI as:

text
future-video-studio-mcp

The MCP Registry package verification marker is the hidden comment near the top of this README:

html
<!-- mcp-name: video.future/future-video-studio -->

Links

Source: README.md at commit 673eff4

Tools

8

fvs_open_chatgpt_app

Open Future Video Studio

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.

Parametersquote_idproject_idstatus_urlclaim_tokenfinal_video_url

fvs_submit_render

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 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.

Parametersrequestrequiredupload_urlspoll_until_complete

fvs_create_paid_render_quote

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 `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.

Parametersrequestrequiredupload_urls

fvs_get_render_status

Get render status

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

Parametersproject_idstatus_url

fvs_get_paid_render_status

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`.

Parametersquote_idstatus_urlclaim_token

fvs_cancel_render

Cancel render

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

Parameterscancel_urlproject_id

fvs_download_final_video

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 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.

Parametersoverwriteoutput_pathrequiredfinal_video_urlrequired

fvs_example_render_request

Example render request

Return a minimal scene render request agents can adapt.

Takes no parameters.

Version history

1
  1. v0.1.8LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Future integrations

FutureSense

Published by GitHub account Sams3595

FutureSense exposes the FutureSense business platform's invoicing, accounting, payroll, CRM, booking, email and content tools to an AI assistant via one API…

Streamable HTTPWeb executableAuth
Productivity & WorkflowCredential requiredOct 24, 2026

FutureSearch MCP Server

Published by GitHub account futuresearch

Local MCP server that lets an assistant forecast future outcomes, compare decision options, and run web research agents through the FutureSearch service.

STDIODesktop only
Web Search & ScrapingNot validated yetOct 25, 2026