Ext Ops Panel
Open dashboard
Comparison

Ssemble AI Clipping vs Vyexa — video link to short clips

Ssemble AI Clipping is an MCP server published by ssemble.com. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). Vyexa — video link to short clips is an MCP server published by vyexa.net. 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
MarketplaceSsemble AI ClippingVyexa — video link to short clips
Official MCP Registry Listed
Version: 1.1.14
Downloads/month (npm): 1 870
Downloads/week (npm): 382
Forks (GitHub): 2
Stars (GitHub): 7
Not marked · First seen
Listed
Version: 1.0.0
No figure published
Not marked · First seen
npm registry (MCP servers) Listed
Version: 1.1.14
Downloads/month (npm): 1 870
Downloads/week (npm): 382
Forks (GitHub): 2
Stars (GitHub): 7
Not marked · First seen
Not listed

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

Ssemble AI Clipping vs Vyexa — video link to short clips
FactSsemble AI ClippingVyexa — video link to short clips
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)7No figure on GitHub
Forks (GitHub) (differs)2No figure on GitHub
Last release (differs)2026-10-27Not published
Where it runs (differs)Remote server or your machineRemote server (vyexa.net/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/ssembleinc/ssemble-mcp-serverNot stated
Changes in the last 7 days (differs)60
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 25 h agoNot responding since 2026-10-28

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

Ssemble AI Clipping

In its own words, on Official MCP Registry:

Create AI-powered short-form video clips from YouTube videos. Supports webhook callbacks.

Vyexa — video link to short clips

In its own words, on Official MCP Registry:

Turn a video link into vertical short clips with subtitles: create jobs, poll, get downloads.

How to run each

Ssemble AI Clipping As a remote MCP server

Claude Code
claude mcp add --transport http ssemble-ai-clipping https://mcp.ssemble.com/mcp

Requires: SSEMBLE_API_KEY (secret)

Vyexa — video link to short clips As a remote MCP server

Claude Code
claude mcp add --transport http clips https://vyexa.net/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Only the endpoint of Ssemble AI Clipping responded at the last daily check. How we check endpoints

Tools each declares

Neither the marketplaces of Vyexa — video link to short clips nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

The marketplaces of Vyexa — video link to short clips publish no settings it asks for, so we do not compare settings.

What it can do: Ssemble AI Clipping · What it can do: Vyexa — video link to short clips · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). 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