Ext Ops Panel
Open dashboard
Comparison

hyperframes vs io.github.AceDataCloud/mcp-veo

hyperframes is a plugin bundle for AI coding tools published by heygen-com. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Community GitHub marketplaces). io.github.AceDataCloud/mcp-veo is an MCP server published by AceDataCloud. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
Marketplacehyperframesio.github.AceDataCloud/mcp-veo
Claude Code: claude-plugins-official Listed
Version: 0.8.61
Forks (GitHub): 5 510
Stars (GitHub): 61 563
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2026.10.12.1
Downloads/month (PyPI): 1 639
Downloads/week (PyPI): 750
Forks (GitHub): 1
Stars (GitHub): 3
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

hyperframes vs io.github.AceDataCloud/mcp-veo
Facthyperframesio.github.AceDataCloud/mcp-veo
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)61 563 (better)3 (worse)
Forks (GitHub) (differs)5 510 (better)1 (worse)
Last release (differs)Not published2026-10-12
Where it runs (differs)Installs as a plugin bundleRemote server (veo.mcp.acedata.cloud/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)21Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/heygen-com/hyperframesgithub.com/acedatacloud/veomcp
Changes in the last 7 days (differs)21
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

hyperframes

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

HyperFrames by HeyGen. Write HTML, render video. Compositions, GSAP and runtime adapter animations, captions, voiceovers, audio-reactive visuals, and website-to-video capture for HyperFrames.

io.github.AceDataCloud/mcp-veo

In its own words, on Official MCP Registry:

MCP server for Google Veo AI video generation

How to run each

hyperframes As a Claude Code plugin

Claude Code
/plugin install hyperframes@claude-plugins-official

io.github.AceDataCloud/mcp-veo As a remote MCP server

Claude Code
claude mcp add --transport http mcp-veo https://veo.mcp.acedata.cloud/mcp

Requires: ACEDATACLOUD_API_TOKEN (secret)

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

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

What it can do: hyperframes · What it can do: io.github.AceDataCloud/mcp-veo · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. 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