@lovable.dev/mcp-js vs Homespun
@lovable.dev/mcp-js is an MCP server published by @lovable.dev. Marketplaces we read that list it: 1 (npm registry (MCP servers)). Homespun is an MCP server published by homespun.dev. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-09. 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 |  Homespun | |
|---|---|---|
| npm registry (MCP servers) | Listed Version: 3.4.0 Downloads/month (npm): 1 432 879 Downloads/week (npm): 546 524 Not marked · First seen |
Listed Version: 1.6.99 Downloads/month (npm): 2 442 Downloads/week (npm): 453 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
| Official MCP Registry | Not listed | Listed Version: 1.6.98 Downloads/month (npm): 2 442 Downloads/week (npm): 453 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
| Fact | @lovable.dev/mcp-js | Homespun |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 1 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | 2026-10-30 (better) | 2026-10-20 (worse) |
| Where it runs (differs) | On your machine (@lovable.dev/mcp-js) | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 4, secrets among them: 2 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/lovablelabs/lovable | github.com/homespunapps/homespun |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 31 h ago returned HTTP 406 |
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.dev/mcp-js
Author MCP servers for Lovable apps. Declare tools with defineTool, register them in defineMcp, and a framework adapter (TanStack or Supabase Edge Functions) emits the route(s) at build time.
Homespun
Deploy a multi-user web app from your agent: hosting, auth, database, and permissions.
How to run each
@lovable.dev/mcp-js
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Homespun As a remote MCP server
claude mcp add --transport http homespun https://homespun.dev/mcpRequires: HOMESPUN_API_KEY (secret), HOMESPUN_REGISTER_SECRET (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Homespun has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of @lovable.dev/mcp-js nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
The marketplaces of @lovable.dev/mcp-js publish no settings it asks for, so we do not compare settings.
What it can do: @lovable.dev/mcp-js · What it can do: Homespun · Compare two other plugins
Package data comes from the public npm registry (registry.npmjs.org). 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.