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