Ext Ops Panel
Open dashboard
Comparison

Renderster vs showtime

Renderster is an MCP server published by renderster.com. Marketplaces we read that list it: 1 (Official MCP Registry). showtime is an MCP server published by FavioVazquez. Marketplaces we read that list it: 3 (Official MCP Registry, npm registry (MCP servers), Community GitHub marketplaces). As of our marketplace pass on 2026-11-10. 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
MarketplaceRenderstershowtime
Official MCP Registry Listed
Version: 1.0.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.4.6
Downloads/month (npm): 1 296
Downloads/week (npm): 98
Forks (GitHub): 28
Stars (GitHub): 327
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.4.6
Downloads/month (npm): 1 296
Downloads/week (npm): 98
Forks (GitHub): 28
Stars (GitHub): 327
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

Renderster vs showtime
FactRenderstershowtime
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)0 (worse)327 (better)
Forks (GitHub) (differs)0 (worse)28 (better)
Last release (differs)2026-11-10 (better)2026-10-17 (worse)
Where it runs (differs)Remote server (mcp.renderster.com/mcp)On your machine (@faviovazquez/showtime-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published8, secrets among them: 0
Hooks it runs (differs)Not published1
Parts of the bundle (differs)Not a bundle13
Licence (differs)Not statedMIT
Repository (differs)github.com/wunka-tech/renderster-mcpgithub.com/faviovazquez/showtime
Changes in the last 7 days (differs)20
First seen (differs)2026-10-252026-10-11
Endpoint at the last check (differs)Status out of date: last check 46 h ago returned HTTP 401no remote endpoint we check

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

Renderster

In its own words, on Official MCP Registry:

Long video in, captioned vertical clips out: clip, dub, transcribe and auto edit videos

showtime

In its own words, on Official MCP Registry:

Local video studio for your coding agent: scenes, voice, music and captions, on your machine.

How to run each

Renderster As a remote MCP server

Claude Code
claude mcp add --transport http renderster https://mcp.renderster.com/mcp

showtime As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio showtime -- npx -y @faviovazquez/showtime-mcp

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

Only Renderster has a remote endpoint we 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

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

What it can do: Renderster · What it can do: showtime · 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). Data comes from public marketplace files in GitHub repositories of their authors. 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