mcpbeat Sign in

Future Video Studio MCP Server

by future Your server? Claim it
answering

Future Video Studio is answering right now. Last checked 13 min ago. 111 installs a week from pypi. It exposes 8 tools. Last commit 11 Jun 2026.

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

Installs per day peak 44 · avg 16 · +23% w/w
a month agotoday
Uptime history 48 days of history · worst day 99%
48 days agonow
100.0%
Uptime 24h
91 of 91 checks
8
Tools
read from the server
276 ms
Response time
average over 24h
111
Installs / week
npm and PyPI

What the code does

We read the source, 22 min ago · tools taken from the live server · rules 3dff92dd89df

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Builds a file path from a variable src/fvs_mcp_server/server.py:1143, [пакет] src/fvs_mcp_server/server.py:1143 
            path = os.path.join(base_dir, filename)

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

run in your terminal
claude mcp add future-video-studio --transport http https://mcp.future.video/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "future-video-studio": {
      "url": "https://mcp.future.video/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.future-video-studio]
url = "https://mcp.future.video/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "future-video-studio": {
      "url": "https://mcp.future.video/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "future-video-studio": {
      "url": "https://mcp.future.video/mcp"
    }
  }
}

Available tools 8

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

fvs
fvs_cancel_render
Cancel a Future Video Studio render job. Provide either `project_id` or the full `cancel_url` returned by fvs_submit_render.
fvs_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.
fvs_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.
fvs_example_render_request
Return a minimal scene render request agents can adapt.
fvs_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`.
fvs_get_render_status
Check a Future Video Studio render job. Provide either `project_id` or the full `status_url` returned by fvs_submit_render.
fvs_open_chatgpt_app
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.
fvs_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.

Endpoints

URLTransportStateLatencyChecked
https://mcp.future.video/mcp streamable-http answering 200 ms 13 min ago

Alternatives to Future Video Studio

same job, measured the same way
Quriov
by quriovai

Create and manage AI image and video generations through Quriov's fixed public MCP tools.

answering
Inblog
by inblog

Create, manage, publish, and analyze Inblog content through AI agents.

answering
OfflineCreator Studio
by offlinecreatorstudio

Create images and videos with OfflineCreator Studio through OAuth or the npm stdio server.

71 installs/wk answering
E2b
by mcparmory

Create and manage secure sandboxes for running AI agent code

238 installs/wk local only
Creative Claw
by creativeclaw

On-brand creative studio for AI agents: images, video, audio, and 3D.

53 tools answering
ReelsFarm
by mateohysa

Create, manage, schedule, and publish short-form user-generated content through AI agents.

answering
SiteGPT
by sitegpt

Manage SiteGPT chatbots and account resources through the SiteGPT API v2.

17 tools answering
FOTOhub Creative AI
by fotohub

Generate images, video, music, voice and 3D through one API. 30 tools, 200+ models.

answering

Future Video Studio — questions

Answers built from our own checks of this server.

What can Future Video Studio do?
It exposes 8 tools, read directly from the server on our last check. Among them: fvs_cancel_render, fvs_create_paid_render_quote, fvs_download_final_video, fvs_example_render_request, fvs_get_paid_render_status, fvs_get_render_status and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Future Video Studio working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 276 ms. The bar chart above shows every period we have measured.
How do I connect Future Video Studio?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Future Video Studio need an API key?
No. Future Video Studio completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Future Video Studio?
It answers our handshake in 276 ms on average, which is faster than 54% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Future Video Studio?
The pypi package future-video-studio-mcp was installed 111 times in the last week. Week over week that is +23%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Future Video Studio open source?
Yes — it is published under the MIT licence, written in Python and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.