Ext Ops Panel
Open dashboard
Comparison

heimdall vs FFmpeg API

heimdall is a plugin bundle for AI coding tools published by pranavtotla. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). FFmpeg API is an MCP server published by ffmpeg-api.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
MarketplaceheimdallFFmpeg API
Claude Code: claude-plugins-community Listed
Version: 0.3.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
No figure published
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

heimdall vs FFmpeg API
FactheimdallFFmpeg API
Marketplaces that list it11
Stars (GitHub) (differs)1No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.ffmpeg-api.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)1Not published
Parts of the bundle (differs)7Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/pranavtotla/heimdallNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 days ago, requires a key

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

heimdall

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

Analyze video files: especially bug report screen recordings, directly in Claude Code. Extracts frames via ffmpeg, transcribes audio via whisper-cpp, and produces structured reports with steps-to-reproduce, error messages, and timestamps. All heavy work runs in a subagent so your main context stays clean.

FFmpeg API

In its own words, on Official MCP Registry:

Run FFmpeg and FFprobe in the cloud: convert, compress, trim and analyze video and audio.

How to run each

heimdall As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install heimdall@claude-community

FFmpeg API As a remote MCP server

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

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

Only FFmpeg API 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

Neither one's marketplaces publish the settings it asks for.

What it can do: heimdall · What it can do: FFmpeg API · 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