Future Video Studio
Server Details
Create and manage cinematic AI video renders through the Future Video Studio Agent API.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- ariadne-coil/fvs-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.2/5 across 8 of 8 tools scored. Lowest: 3.5/5.
Each tool has a clearly distinct purpose: cancel, submit, status (two variants), download, quote, example, and app launcher. No overlap or ambiguity.
All tools use a consistent verb_noun pattern with the 'fvs_' prefix, e.g., fvs_cancel_render, fvs_submit_render, fvs_get_render_status.
8 tools are appropriate for a video rendering service, covering essential operations without being overwhelming or too few.
The tool surface covers the full render lifecycle: submission, status polling (both regular and paid), cancellation, download, quote creation, and an example request. No obvious gaps.
Available Tools
8 toolsfvs_cancel_renderCancel renderDestructiveInspect
Cancel a Future Video Studio render job.
Provide either `project_id` or the full `cancel_url` returned by
fvs_submit_render.
| Name | Required | Description | Default |
|---|---|---|---|
| cancel_url | No | ||
| project_id | No |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
fvs_create_paid_render_quoteCreate paid render quoteInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| request | Yes | Required render request object used for the paid quote. Include name. project_mode must be one of scene, music, or custom. Use assets[].purpose for asset intent. Usually include screenplay, instructions, shot_count, duration, and resolution. | |
| upload_urls | No | Optional public HTTPS reference asset URLs. Each object can include url and filename; filename should match request.assets[].filename. |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
fvs_download_final_videoDownload final videoDestructiveInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| overwrite | No | Set true only when replacing an existing output_path is intended. Defaults to false to avoid accidental local file overwrites. | |
| output_path | Yes | Local filesystem path where the MCP server should write the video, for example C:/Users/me/Videos/fvs-result.mp4 or /tmp/fvs-result.mp4. Parent directories are created. Existing files are refused unless overwrite is true. | |
| final_video_url | Yes | HTTPS signed final_video_url returned by a completed fvs_get_render_status or fvs_get_paid_render_status response. Use a fresh status check if the signed URL has expired. |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
fvs_example_render_requestExample render requestRead-onlyIdempotentInspect
Return a minimal scene render request agents can adapt.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
fvs_get_paid_render_statusGet paid render statusRead-onlyIdempotentInspect
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`.
| Name | Required | Description | Default |
|---|---|---|---|
| quote_id | No | ||
| status_url | No | ||
| claim_token | No |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
fvs_get_render_statusGet render statusRead-onlyIdempotentInspect
Check a Future Video Studio render job.
Provide either `project_id` or the full `status_url` returned by
fvs_submit_render.
| Name | Required | Description | Default |
|---|---|---|---|
| project_id | No | ||
| status_url | No |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
fvs_open_chatgpt_appOpen Future Video StudioRead-onlyIdempotentInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| quote_id | No | ||
| project_id | No | ||
| status_url | No | ||
| claim_token | No | ||
| final_video_url | No |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
fvs_submit_renderSubmit renderDestructiveInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| request | Yes | Required render request object. Include name. project_mode must be one of scene, music, or custom. Use assets[].purpose for asset intent. Usually include screenplay, instructions, shot_count, duration, and resolution. | |
| upload_urls | No | Optional public HTTPS reference asset URLs. Each object can include url and filename; filename should match request.assets[].filename. | |
| poll_until_complete | No |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!