Ext Ops Panel
Open dashboard
Comparison

ElevenLabs vs Future Video Studio

ElevenLabs is an MCP server published by elevenlabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). 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-10-21. 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
MarketplaceElevenLabsFuture Video Studio
Docker MCP Catalog Listed
Version: sha256:ad57886f6a7b
Forks (GitHub): 258
Pulls (Docker Hub): 50 969
Stars (Docker Hub): 7
Stars (GitHub): 1 535
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.8
Downloads/month (PyPI): 91
Downloads/week (PyPI): 37
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

ElevenLabs vs Future Video Studio
FactElevenLabsFuture Video Studio
Marketplaces that list it11
Stars (GitHub) (differs)1 535 (better)0 (worse)
Pulls (Docker Hub) (differs)50 969No figure on Docker Hub
Forks (GitHub) (differs)258 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/elevenlabs)Remote server (mcp.future.video/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)27Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/elevenlabs/elevenlabs-mcpgithub.com/ariadne-coil/fvs-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 4 days 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

ElevenLabs

In its own words, on Docker MCP Catalog:

Official ElevenLabs Model Context Protocol (MCP) server that enables interaction with powerful Text to Speech and audio processing APIs.

Future Video Studio

In its own words, on Official MCP Registry:

Create and manage cinematic AI video renders through the Future Video Studio Agent API.

How to run each

ElevenLabs As a local MCP server: Docker image

Claude Code
claude mcp add --env "ELEVENLABS_API_KEY=<YOUR_ELEVENLABS_API_KEY>" --transport stdio elevenlabs -- docker run -i --rm -e ELEVENLABS_API_KEY mcp/elevenlabs

Requires: ELEVENLABS_API_KEY (secret)

Future Video Studio As a remote MCP server

Claude Code
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.

Only Future Video Studio has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Future Video Studio publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Future Video Studio publish no settings it asks for, so we do not compare settings.

What it can do: ElevenLabs · What it can do: Future Video Studio · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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