Future Video Studio

video.future由 future.video 發布官方發布者v0.1.8更新於 Oct 24, 2026

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

已驗證Streamable HTTP可網頁執行媒體與設計AI 與機器學習

概覽

AI 產生的概覽

Future Video Studio MCP 讓助理透過 FVS Agent API 提交、監控、取消並下載電影級 AI 影片算圖工作。

可以做什麼
  • 提交算圖工作，可附上公開 HTTPS 參考素材
  • 建立免帳號的 Link 付款報價，並以領取權杖查詢付費算圖
  • 依專案 ID 或狀態 URL 查詢算圖狀態，並取消工作
  • 將已完成算圖的簽章連結下載為本機檔案
  • 開啟 ChatGPT 應用面板，並取得範例算圖請求
適用情境
當希望助理依創意簡述產出電影級 AI 影片、追蹤或取消這些算圖工作，並把成品存到本機時使用；可採 FVS 帳戶計費或單次付費。
執行需求
可作為遠端託管端點使用，也可透過 stdio 執行本機 Python 套件。帳戶模式需要 FVS Agent API 金鑰，透過 X-FVS-Agent-Key 標頭或 FVS_AGENT_API_KEY 環境變數提供；市集模式需要 X-FVS-Marketplace-* 系列標頭；單次付費模式不需金鑰。需要連線至 FVS 服務及簽章下載連結的網路。
安裝前請注意
算圖會產生實際費用：帳戶模式扣抵 FVS 錢包額度，單次付費模式需支付 Link/Stripe 報價。README 建議在提交錢包扣款算圖前取得使用者明確同意。Agent 金鑰與市集簽章屬機密資訊。下載工具會寫入伺服器檔案系統，overwrite 為 true 時可覆寫既有檔案；只應傳入已完成算圖回傳的簽章連結。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Future Video Studio，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/video.future%2Ffuture-video-studio/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "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

來源：README.md，提交 673eff4

工具

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.

輸入參數quote_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.

輸入參數request必填upload_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.

輸入參數request必填upload_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.

輸入參數project_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`.

輸入參數quote_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.

輸入參數cancel_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.

輸入參數overwriteoutput_path必填final_video_url必填

fvs_example_render_request

Example render request

Return a minimal scene render request agents can adapt.

無需輸入參數。

版本歷史

1
  1. v0.1.8最新Sep 16, 2026

評分

已滿足適用檢查項的 100%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

其他 Future 整合

FutureSense

由 GitHub 帳號 Sams3595 發布

FutureSense 讓 AI 助理透過單一 API 金鑰操作 FutureSense 商業平台的開票、會計、薪資、CRM、預約、郵件與內容工具。

Streamable HTTP可網頁執行驗證方式
效率與工作流需要憑證Oct 24, 2026

FutureSearch MCP Server

由 GitHub 帳號 futuresearch 發布

本機 MCP 伺服器，讓助理透過 FutureSearch 服務預測未來結果、比較決策選項，並執行網路研究代理。

STDIO僅桌面
網頁搜尋與抓取尚未驗證Oct 25, 2026