Future Video Studio

Future Video Studio is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.future.video/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

The registry entry declares HTTP headers for the connection: X-FVS-Agent-Key (secret), X-FVS-Billing-Mode, X-FVS-Marketplace-Account, X-FVS-Marketplace-Entitlement, X-FVS-Marketplace-Timestamp and X-FVS-Marketplace-Signature (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set them with the server's URL.

It can also run locally from a Python package published to PyPI: future-video-studio-mcp version 0.1.8. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install — the usual command is uvx future-video-studio-mcp.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "future-video-studio": {
      "command": "uvx",
      "args": [
        "future-video-studio-mcp"
      ]
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect