Ext Ops Panel
Open dashboard
Comparison

constellation vs lovable

constellation is a plugin bundle for AI coding tools published by Jose Andrade. Marketplaces we read that list it: 1 (Community GitHub marketplaces). lovable is a plugin bundle for AI coding tools published by lovablelabs. Marketplaces we read that list it: 3 (Claude Code: claude-plugins-official, Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-14. 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
Marketplaceconstellationlovable
Community marketplace avarajar/constellation Listed
Version: 0.6.0
No figure published
Not marked · First seen
Not listed
Claude Code: claude-plugins-official Not listed Listed
Version: 0.1.0
Forks (GitHub): 6
Stars (GitHub): 6
Not marked · First seen
Official MCP Registry Not listed Listed
Version: 0.1.3
Forks (GitHub): 6
Stars (GitHub): 6
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

constellation vs lovable
Factconstellationlovable
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)No figure on GitHub6
Forks (GitHub) (differs)No figure on GitHub6
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.lovable.dev)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)94
Licence (differs)MITApache-2.0
Repository (differs)github.com/avarajar/constellationgithub.com/lovablelabs/mcp
Changes in the last 7 days22
First seen (differs)2026-10-142026-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

constellation

In its own words, on Community GitHub marketplaces:

Interactive project generator — visual web UI to select your tech stack, then AI-generates a fully functional project

lovable

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

Build, iterate on, deploy, and manage Lovable apps from Claude Code. Bundles the official Lovable MCP server (remote, OAuth 2.1) and adds focused commands for the common build/iterate/database workflows, with credit- and publish-safety prompts.

How to run each

constellation As a Claude Code plugin

Claude Code
/plugin marketplace add avarajar/constellation
/plugin install constellation@constellation

lovable As a Claude Code plugin

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

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

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

What it can do: constellation · What it can do: lovable · Compare two other plugins

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