Create and manage cinematic AI video renders through the Future Video Studio Agent API.
Use this profile to copy client config, check auth requirements, review tools and resources, and compare related MCP servers before adding it to an AI client.
https://mcp.future.video/mcpuvx future-video-studio-mcpHeaders: X-FVS-Agent-Key
Add this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"video-future-future-video-studio": {
"command": "uvx",
"args": [
"future-video-studio-mcp"
]
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
Paste an API key, bearer token, or session value from the provider. It is used once to list inventory and discarded after the request.
Optional Future Video Studio Agent API key from Settings > Agent API Access. Omit for Link paid quote mode.
Future Video Studio is an MCP server for Create and manage cinematic AI video renders through the Future Video Studio Agent API.. It supports STDIO, HTTP transport.
Use the generated config in Install. This server runs with uvx future-video-studio-mcp; add any required environment variables before starting your client.
Choose the Claude Desktop tab in Install, copy the config, and add it to Claude Desktop's MCP server settings. Endpoint: https://mcp.future.video/mcp.
Choose the Claude Code tab in Install, copy the config, and add it to Claude Code's MCP server settings. Endpoint: https://mcp.future.video/mcp.
Choose the Codex tab in Install, copy the config, and add it to Codex's MCP server settings. Endpoint: https://mcp.future.video/mcp.
Choose the Cursor or VS Code tab in Install, copy the config, and add it to Cursor or VS Code's MCP server settings. Endpoint: https://mcp.future.video/mcp.
Future Video Studio uses STDIO, HTTP transport. Endpoint: https://mcp.future.video/mcp.
Future Video Studio inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
Future Video Studio does not advertise a verified auth requirement. If discovery fails, it may still need provider login, an API key, a bearer token, or a session header.
| Package | Registry | Version | Inputs |
|---|---|---|---|
future-video-studio-mcpstdio | pypi | 0.1.2 | None advertised |