Ext Ops Panel
Open dashboard
Comparison

future-video-studio vs Kinocut

future-video-studio is a plugin bundle for AI coding tools published by ariadne-coil. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Kinocut is an MCP server published by KyaniteLabs. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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

Where each is published
Marketplacefuture-video-studioKinocut
Claude Code: claude-plugins-community Listed
Version: 6d49005
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed, marked deprecated
Version: 1.16.1
Downloads/month (PyPI): 8 854
Downloads/week (PyPI): 2 058
Forks (GitHub): 47
Stars (GitHub): 226
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

future-video-studio vs Kinocut
Factfuture-video-studioKinocut
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)226 (better)
Forks (GitHub) (differs)0 (worse)47 (better)
Last release (differs)Not published2026-10-27
Where it runs (differs)Installs as a plugin bundleOn your machine (kinocut)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/ariadne-coil/future-video-render-claude-plugingithub.com/kyanitelabs/kinocut
Changes in the last 7 days (differs)04
First seen2026-10-112026-10-11

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

future-video-studio

In its own words, on Claude Code: claude-plugins-community:

Future Video Studio lets Claude create cinematic AI videos through the hosted FVS MCP server. It can turn creative briefs, scripts, shot lists, and public reference assets into finished video renders, then monitor progress and return the final video URL. The plugin supports both FVS account renders through an Agent API key and no-account pay-as-you-go renders through Link payment quotes, so users can either spend existing wallet credits or approve a one-off render payment before generation begins.

Kinocut

In its own words, on Official MCP Registry:

Guardrailed video editing for AI agents: FFmpeg, captions, effects, Hyperframes, and receipts.

How to run each

future-video-studio As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install future-video-studio@claude-community

Kinocut As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio kinocut -- uvx kinocut

Commands built only from what the marketplaces declare; the full set for every client is on each card.

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: future-video-studio · What it can do: Kinocut · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.

Where the data comes from: how the catalog is built