Ext Ops Panel
Open dashboard
Comparison

nano-banana vs app.lightgen/lightgen

nano-banana is a plugin bundle for AI coding tools published by Ibrahim-3d. Marketplaces we read that list it: 1 (Community GitHub marketplaces). app.lightgen/lightgen is an MCP server published by lightgen.app. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. 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
Marketplacenano-bananaapp.lightgen/lightgen
Community marketplace ibrahim-3d/orchestrator-supaconductor Listed
Version: 2.1.0
Forks (GitHub): 7
Stars (GitHub): 14
Not marked · First seen
Not listed
Community marketplace ibrahim-3d/nano-banana-claude-plugin Removed on 2026-10-29
Version: 2.1.0
Forks (GitHub): 6
Stars (GitHub): 15
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
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

nano-banana vs app.lightgen/lightgen
Factnano-bananaapp.lightgen/lightgen
Marketplaces that list it11
Stars (GitHub) (differs)14No figure on GitHub
Forks (GitHub) (differs)7No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (lightgen.app/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)5Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/ibrahim-3d/nano-banana-claude-pluginNot stated
Changes in the last 7 days00
First seen (differs)2026-10-212026-10-11
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: no HTTP response at the last check 37 h 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

nano-banana

In its own words, on Community GitHub marketplaces:

AI image generation & editing for Claude Code powered by Google Gemini 3.1 API. Text-to-image, inpainting, style transfer, 4K upscaling, search grounding, and multi-reference composition.

app.lightgen/lightgen

In its own words, on Official MCP Registry:

Generate and edit images and create short videos inside Claude. Prepaid credits, no subscription.

How to run each

nano-banana As a Claude Code plugin

Claude Code
/plugin marketplace add ibrahim-3d/orchestrator-supaconductor
/plugin install nano-banana@ibrahim-plugins

app.lightgen/lightgen As a remote MCP server

Claude Code
claude mcp add --transport http lightgen https://lightgen.app/mcp

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

Only app.lightgen/lightgen 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: nano-banana · What it can do: app.lightgen/lightgen · 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