OpenVideoGenerator MCP Server vs Future Video Studio
OpenVideoGenerator MCP Server is an MCP server published by zsthimself. Marketplaces we read that list it: 1 (Official MCP Registry). Future Video Studio is an MCP server published by future.video. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-14. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  OpenVideoGenerator MCP Server |   Future Video Studio |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.1.8 Downloads/month (PyPI): 91 Downloads/week (PyPI): 18 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | OpenVideoGenerator MCP Server | Future Video Studio |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (openvideogenerator.com/api/mcp) | Remote server (mcp.future.video/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/zsthimself/open-video-generator-mcp | github.com/ariadne-coil/fvs-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-11-10 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 7 h ago | Responded 3 h ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
OpenVideoGenerator MCP Server
AI video generation MCP server for Kling, MiniMax, Luma & Hunyuan with prompt blueprints.
Future Video Studio
Create and manage cinematic AI video renders through the Future Video Studio Agent API.
How to run each
OpenVideoGenerator MCP Server As a remote MCP server
claude mcp add --transport http open-video-generator-mcp https://openvideogenerator.com/api/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Future Video Studio As a remote MCP server
claude mcp add --transport http future-video-studio https://mcp.future.video/mcp --header "X-FVS-Agent-Key: <YOUR_X_FVS_AGENT_KEY>" --header "X-FVS-Marketplace-Signature: <YOUR_X_FVS_MARKETPLACE_SIGNATURE>"Requires: X-FVS-Agent-Key header, X-FVS-Marketplace-Signature header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: OpenVideoGenerator MCP Server · What it can do: Future Video Studio · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.