lovable vs io.github.haserisa0810-gif/nanami-products
lovable is a plugin bundle for AI coding tools published by lovablelabs. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Official MCP Registry). io.github.haserisa0810-gif/nanami-products is an MCP server published by haserisa0810-gif. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-05. 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
| Marketplace |  lovable |  io.github.haserisa0810-gif/nanami-products |
|---|---|---|
| Claude Code: claude-plugins-official | Listed Version: 0.1.0 Forks (GitHub): 6 Stars (GitHub): 9 Not marked · First seen |
Not listed |
| Official MCP Registry | Listed Version: 0.1.3 Forks (GitHub): 6 Stars (GitHub): 9 Not marked · First seen |
Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 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
| Fact | lovable | io.github.haserisa0810-gif/nanami-products |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 9 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 6 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.lovable.dev) | Remote server (chart.nanami-astro.com/mcp) |
| Transport (differs) | Streamable HTTP | SSE |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 4 | Not a bundle |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/lovablelabs/mcp | github.com/haserisa0810-gif/nanami-products |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Status out of date: last check 6 days ago returned HTTP 200 | Responded 1 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
lovable
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.
io.github.haserisa0810-gif/nanami-products
Pre-computed astrology YAML via Swiss Ephemeris. Calculation is code, interpretation is AI.
How to run each
lovable As a Claude Code plugin
/plugin install lovable@claude-plugins-officialio.github.haserisa0810-gif/nanami-products As a remote MCP server
claude mcp add --transport sse nanami-products https://chart.nanami-astro.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily 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: lovable · What it can do: io.github.haserisa0810-gif/nanami-products · 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 the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.