Ext Ops Panel
Open dashboard
Comparison

NoaCG Broadcast Graphics and Playout vs HyperCodeMotion MCP

NoaCG Broadcast Graphics and Playout is a plugin bundle for AI coding tools published by NoaCG Studio. Marketplaces we read that list it: 1 (Community GitHub marketplaces). HyperCodeMotion MCP is an MCP server published by jasp402. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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
MarketplaceNoaCG Broadcast Graphics and PlayoutHyperCodeMotion MCP
Community marketplace noacg/noacg-studio Listed
Version: 0.12.3
Forks (GitHub): 2
Stars (GitHub): 8
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.8.0
Forks (GitHub): 0
Stars (GitHub): 1
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

NoaCG Broadcast Graphics and Playout vs HyperCodeMotion MCP
FactNoaCG Broadcast Graphics and PlayoutHyperCodeMotion MCP
Marketplaces that list it11
Stars (GitHub) (differs)8 (better)1 (worse)
Forks (GitHub) (differs)2 (better)0 (worse)
Last release (differs)2026-10-18 (worse)2026-10-21 (better)
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.hypercodemotion.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/noacg/noacg-studiogithub.com/jasp402/hypercodemotion-mcp
Changes in the last 7 days (differs)39
First seen2026-10-142026-10-14
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 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

NoaCG Broadcast Graphics and Playout

In its own words, on Community GitHub marketplaces:

Make broadcast graphics for NoaCG Studio and play them out: lower thirds, scoreboards, tickers, bugs, countdowns and full-screen graphics, run live from NoaCG Playout to CasparCG, OBS or vMix, or exported for SPX, H2R or any OGraf renderer. Adds the /noacg:graphic skill, and runs nothing until a graphic is being made.

HyperCodeMotion MCP

In its own words, on Official MCP Registry:

Validate AI-made motion graphics and package them as editable HyperCodeMotion projects.

How to run each

NoaCG Broadcast Graphics and Playout As a Claude Code plugin

Claude Code
/plugin marketplace add noacg/noacg-studio
/plugin install noacg@noacg-studio

HyperCodeMotion MCP As a remote MCP server

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

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

Only HyperCodeMotion MCP has a remote endpoint we check. How we check endpoints

Tools each declares

Neither the marketplaces of NoaCG Broadcast Graphics and Playout nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

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

What it can do: NoaCG Broadcast Graphics and Playout · What it can do: HyperCodeMotion MCP · Compare two other plugins

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