Skip to main content

MCP server for creating Future Video Studio renders through the FVS Agent API.

Project description

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:

https://mcp.future.video/mcp

The same server can also run locally over stdio from this Python package.

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.
  • Pay-per-render mode: omit the account key. 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.

Tools

  • fvs_submit_render: submit a render request, optionally with uploaded files
  • 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

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:

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

Pay-per-render mode:

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

Local Install

python -m pip install future-video-studio-mcp
python -m fvs_mcp_server

Example local stdio MCP config:

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

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

Run the HTTP transport locally:

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

Publishing

Build and check the package:

python -m build
python -m twine check dist/*

This package is intended to publish to PyPI as:

future-video-studio-mcp

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

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

Links

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

future_video_studio_mcp-0.1.2.tar.gz (16.2 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

future_video_studio_mcp-0.1.2-py3-none-any.whl (15.4 kB view details)

Uploaded Python 3

File details

Details for the file future_video_studio_mcp-0.1.2.tar.gz.

File metadata

  • Download URL: future_video_studio_mcp-0.1.2.tar.gz
  • Upload date:
  • Size: 16.2 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/6.1.0 CPython/3.13.12

File hashes

Hashes for future_video_studio_mcp-0.1.2.tar.gz
Algorithm Hash digest
SHA256 d78871283db5004c4d9003be6b78d53a4d4a6991e17e8ad2c3fe93ed0f88f3c1
MD5 7f9f1a1ae657cc4f0e3f2bc71af26882
BLAKE2b-256 dcee00e5405a7c14f0cae66bfe429d167ec5d88eff43d70892d80ceefe3e3519

See more details on using hashes here.

Provenance

The following attestation bundles were made for future_video_studio_mcp-0.1.2.tar.gz:

Publisher: publish-pypi.yml on ariadne-coil/fvs-mcp

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file future_video_studio_mcp-0.1.2-py3-none-any.whl.

File metadata

File hashes

Hashes for future_video_studio_mcp-0.1.2-py3-none-any.whl
Algorithm Hash digest
SHA256 c7198e5f5faf3163b16e6e1e74c5f98b3a3ebeef1fe2103f66130bd6cddf18c0
MD5 d7df94220d90470280c31b5410188b1e
BLAKE2b-256 365136a21078fc510abcffb7e5236700a68868bd77b38bff9bc89ffc6c6d51fb

See more details on using hashes here.

Provenance

The following attestation bundles were made for future_video_studio_mcp-0.1.2-py3-none-any.whl:

Publisher: publish-pypi.yml on ariadne-coil/fvs-mcp

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page